Dublin Web Summit 2012: Stop Solving Problems you Don't Yet Have

My presentation for the Dublin Web Summit 2012.

Transcript

1. Stop solving problems you don’t yet have. Dublin Web Summit 2012
2. a History Lesson
3. <script type="text/javascript"> <!-- function MM_reloadPage(init) { if (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) { document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }} else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload(); } MM_reloadPage(true); //--> </script>
5. Things used by people who understand the problems they solve are also used by those who do not understand those problems, or even if there is a problem.
6. This is an amazing time to be a web developer.
9. Frustration
10. The web is a work in progress. Your job? To deal with it.
11. Making things better with code
13. You now have two problems
15. Problem: no media query support in IE8 and below.
17. Problem: lack of support for styling HTML5 semantic elements in older browsers.
18. Problem: lack of support for certain CSS3 Selectors in older browsers.
19. 1. What is the problem? My process 2. What are my constraints? 3. Is not supporting this feature an option? 4. What current solutions exist? 5. Use a polyfill or roll my own?
20. Why not just use a boilerplate?
22. Stop solving problems you don’t yet have
23. If you don’t know what it is doing. Why is it there?
24. Do you know what is safe to delete?
25. There’s no silver bullet to making a slow site fast. You must take a holistic approach. High performance runs the entire way through from the hardware it’s hosted on, through the app that builds the pages, to the server software that delivers the pages and the front end code that displays them in a browser. Drew McLellan - http://allinthehead.com/retro/361/how-to-make-your-website-fast
27. Polyfills should not be a black box
28. Teach problem solving before polyfilling.
30. “Perch is removing my paragraphs”
31. We need to teach: HTML, CSS, JavaScript
32. We need to teach: Problem Solving skills
34. If we train people to just copy and paste, we stop them growing, learning and contributing.
35. Make sure you know why you are using a solution and what your other options are.
36. Know and test for what happens if JavaScript doesn’t load.
37. When teaching or writing tutorials for others explain problems before handing out the solution. Explain why as well as how.
38. Thank you. @rachelandrew http://rachelandrew.co.uk http://edgeofmyseat.com http://grabaperch.com Image credits - Flickr users: artbystevejohnson, atoach, dominicspics, imagesbywestfall, koalazymonkey, pinksherbert, whatcouldgowrong, colemama