![MERCI! Christian Heilmann http://wait-till-i.com http://icant.co.uk/ http://pluglondon.org [email_address] http:// slideshare.net/cheilmann](https://image.slidesharecdn.com/successful-teams-follow-standards-1195202309989789-2/85/Successful-Teams-follow-Standards-78-320.jpg)
Uploaded byChristian Heilmann
Successful Teams follow Standards
The document emphasizes the importance of following web development standards and practices to improve product consistency, maintainability, and adaptability to changing technologies. It highlights that adherence to W3C recommendations facilitates better collaboration among teams, reduces errors, and enhances quality control. The author advocates for a collaborative culture in web development, where teams work together effectively, regardless of individual expertise or location.
More Related Content
Similar to Successful Teams follow Standards
Successful Teams follow Standards
- 1. Successful Teams follow standards Christian Heilmann Paris Web 2007 November 2007, Paris
- 2. The great thingabout web development is that browsers rock.
- 3. All you needis to put some HTML together, and let the browser do its stuff.
- 4. <HTML> <DIV style=“width:300px;background:gray”> Section Header<BR><BR> Section Body<BR><BR> Section Footer<BR><BR> </div> </HTML>
- 5.
- 6. Done. Nothing toworry about.
- 7. An attitude thatsupports a whole market segment: Web Development
- 8. However, not allweb developers subscribe to it.
- 9. A small, butconstantly growing group tends to disagree.
- 10.
- 11. They want tomove ahead.
- 12. They do thatby relying on a secret weapon.
- 13. Following agreed standardsand practices.
- 14. This takes timeand effort.
- 15. It also takesdedication and stamina.
- 16. Especially when itcomes to following the W3C recommendations.
- 17. … as browsersdo not really care.
- 18. Small wins aregreat
- 19. Does this meanthat following standards means unnecessary overhead?
- 20. Are we agileenough?
- 21.
- 22. First of all,browsers are forgiving, but not in the same manner.
- 23. This is notthat much of a problem, if you are not too fussed about the display being perfect.
- 24. However, some peopledo. With good reason.
- 25. We work withanother department that cares a lot.
- 26.
- 27. We also workwith another department that does not care as much.
- 28.
- 29. However, everybody isa designer. (or thinks so)
- 30. How to achieveconsistency?
- 31. By not lettingbrowsers do guesswork but telling them what is what.
- 32. <!DOCTYPE HTML PUBLIC"-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html dir="ltr" lang="en" > <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Page Demo</title> </head> <body> <div id="intro"> <div class="hd">Section Header</div> <div class="bd">Page Section Body</div> <div class="ft">Page Section Footer</div> </div> </body> </html>
- 33. How can youimprove the product turnaround time?
- 34. Allowing for workin parallel.
- 35. You can achievethis by separating work streams and use the right technologies for the right job.
- 36. sep·a·ra·tion HTML =structure “ what is what” CSS = look and feel “ how should it be displayed” JS/Flash = behaviour “ how should it react”
- 37. The main driverof successful web products?
- 38. The ability tochange and adapt to market demands.
- 39. Your web productis never finished. The media moves too fast for that.
- 40. The web isevolving and moving away from the web we know now.
- 41. New platforms, newbrowsers, new technologies are always around the corner.
- 42.
- 43. Nazb… Naba… that bunny thing.
- 44.
- 45. Businesses who don’tunderstand that need to watch out.
- 46. The way tosupport upcoming technologies and platforms in a predictable manner is?
- 47.
- 48. What is astandard?
- 49. A standard isan agreement of various groups or individuals to solve a problem in a consistent manner.
- 50. An example -The Screw
- 51. To be usedwith a screwdriver
- 52.
- 53.
- 54. We do thesame to web sites.
- 55. The W3C recommendationsare the screwdriver for browsers and assistive technology.
- 56. WYSIWYG or “let’ssee if it works on my browser” aren’t.
- 57. Following a standardmeans: Predictable results Validation as a quality control Safe re-use of code and ideas Consistency (which leads to easy bug-fixing)
- 58. Validation is thestart of a quality control process, not the end of it!
- 59. You can createperfectly valid and at the same time terribly bad code.
- 60. You cannot validatesemantics automatically.
- 61. Following W3C recommendationsis also the start for your own code standards.
- 62. Defining a standardis hard work.
- 63. The benefits howeverare great. Flexible allocations (every product is built the same) Standard QA practices Modular Development via re-use of code from other products. A lot less maintenance work
- 64. Following a standardmakes us ready for change.
- 65. <!DOCTYPE HTML PUBLIC"-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html dir="ltr" lang="en" > <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <title>Page Demo</title> <link rel="stylesheet" type="text/css" href="http://yui.yahooapis.com/2.3.1/build/reset-fonts-grids/reset-fonts-grids.css"> <link rel="stylesheet" type="text/css" href="http://yui.yahooapis.com/2.3.1/build/container/assets/container.css"> <link rel="stylesheet" type="text/css" href="http://yui.yahooapis.com/2.3.1/build/container/assets/skins/sam/container.css"> </head> <body class="yui-skin-sam"> <div id="intro"> <div class="hd">Section Header</div> <div class="bd">Section Body</div> <div class="ft">Section Footer</div> </div> <script type="text/javascript" src="http://yui.yahooapis.com/2.3.1/build/yahoo-dom-event/yahoo-dom-event.js"></script> <script type="text/javascript" src="http://yui.yahooapis.com/2.3.1/build/dragdrop/dragdrop-min.js"></script> <script type="text/javascript" src="http://yui.yahooapis.com/2.3.1/build/container/container-min.js"></script> <script> var demopanel = new YAHOO.widget.Panel('intro',{close:true,visible:true,modal:true,draggable:true}); demopanel.render(); </script> </body> </html>
- 66.
- 67. Following a standardmakes us an example for others.
- 68. Imagine starting ina company that has an agreed way of working.
- 69. People can work,can get sick or go on vacation.
- 70. There is nodowntime or long hand-over periods.
- 71. You don’t workfor yourself but for everybody else and the person to replace you.
- 72. You can workacross the globe, taking advantage of time differences.
- 73.
- 74.
- 75. Lightning Talks: 5Minutes presentation 5 minutes demo 5 minutes discussion Every Thursday 11.45 – 12.00
- 76.
- 77. No more badsurprises. No more heroes. Let’s work together.
- 78. MERCI! Christian Heilmannhttp://wait-till-i.com http://icant.co.uk/ http://pluglondon.org [email_address] http:// slideshare.net/cheilmann