Downloaded 158 times
Uploaded byDylan Wilbanks
Making the Web Fireproof: A Building Code for Websites
The document discusses the need for a 'building code' for the web to address various types of technical debt, including design and accessibility issues. It emphasizes the importance of planning, prototyping, and adopting best practices in web development to enhance security and usability. The author argues that without such standards, issues will persist and compromise the web's efficiency and effectiveness.
![Number_Guessing_Game_Dsbsbssbzboc[1].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/numberguessinggamedoc1-251206215042-a076fc05-thumbnail.jpg?width=640&height=640&fit=bounds)
Making the Web Fireproof: A Building Code for Websites
- 1. Making the WebFireproof: A Building Code for Websites Dylan Wilbanks MinneWebCon 2015 Web: dylanwilbanks.com Twitter: @dylanw
- 2. One caveat: I can’tpromise great insight.
- 3.
- 6.
- 9.
- 10.
- 12.
- 13. But is itfireproof? http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
- 19.
- 20.
- 22.
- 24. Clear rules onwhat goes into a new building
- 25.
- 26.
- 27. Clear rules onwhen to retrofit or replace
- 29.
- 31. We need abuilding code for the web.
- 32.
- 33.
- 34. “Building codes wouldnever work for building code.” https://www.flickr.com/photos/tambako/14065508649/
- 35.
- 37.
- 38.
- 39.
- 40.
- 41. https://www.flickr.com/photos/christinyca/15875497176/ “The built environmentmust be planned in advance!”
- 42. “Web development is notpre-planned!”
- 43. “Web development is notpre-planned!” (Usually)
- 45.
- 47. Every website, everyproduct, every codebase is littered with Doors to Nowhere. (Yes, even yours.)
- 49.
- 50.
- 51.
- 52.
- 53. Kinds of debt •Tech debt • Design debt • Accessibility debt • I18N debt • Security debt • DevOps debt
- 54. Tech debt • Codeupgrades • Refactoring • “Temporary” hacks • TODO • Not staying up to date
- 55.
- 56.
- 58. Design debt • Usabilitycompromised by lack of testing or cut scope • Sub-optimal user flows • Unfinished features • Mobile Last, Mobile Not, What’s Mobile? • “Experience rot” • “Patch and paint” UX solutions instead of “replacing the wall”
- 60. Accessibility debt • Doesn’twork with screen reader • ARIA hooks not used or set up properly • Accessibility never tested, never a priority • “Yes, but are they the 80% case?”
- 62. –Developer, (company redacted) “Sixyears ago I was asked how long it’d take for me to internationalize our code base. I said two weeks. But we didn’t have time. Now, it would take months of work — with multiple developers.”
- 63. You will nevernot have debt.
- 64.
- 65. What’s on firetoday? http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
- 66. The Hierarchy ofNeeds
- 67. The Hierarchy ofNeeds Shipping working code
- 68. The Hierarchy ofNeeds Fixing bugs in working code Shipping working code
- 69. The Hierarchy ofNeeds New features Fixing bugs in working code Shipping working code
- 70. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working code
- 71. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working code
- 72. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working codeMONEY
- 73. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working code MOAR MONEY! MONEY
- 74. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working code MAKE IT RAAAAAAAAIN MOAR MONEY! MONEY
- 75. The Hierarchy ofNeeds Technical debt New features Fixing bugs in working code Shipping working code No Money, Many Problems MAKE IT RAAAAAAAAIN MOAR MONEY! MONEY
- 76.
- 77. Worst of all,it’s not just your debt.
- 78. Worst of all,it’s not just your debt.
- 79. To sum up… •Poor architecture kills velocity and sales • We always have to keep up with change in market, device, user • Not planning for internationalization is costly • Security mistakes cost us money (and face) • Bad accessibility costs us face (and money) • You take on the debt of everyone else’s code you use
- 82. We need abuilding code for the web.
- 84. Not web standards, webpractice.
- 86. What would itlook like? • Design first, prototype second • Best practices for security, accessibility, internationalization • Have a rigorous plan for refactoring and paying down tech debt • “Build to last, build to destroy”
- 87. So why aren’twe doing it?
- 90. There’s no suchthing as a local fire on the Internet.
- 91.
- 92. Who should doit? Yeah, I don’t know either.
- 93.
- 94.
- 95. What can youdo?
- 96. 1. Plan, plan,plan.
- 98.
- 101.
- 102. Defining the damnthing saves us headaches every time.
- 103.
- 104.
- 107. StoryCore • Bootstrap forapplications • Sets the nuts and bolts pieces in place for a basic web application • Import stories into your bug tracker of choice • Build in key user experience requirements • Accessibility and security acceptance criteria
- 108.
- 109.
- 110.
- 111.
- 112. 4. Embrace impermanence throughprototyping.
- 115.
- 117.
- 118.
- 119. 5. Demand betterframeworks, not more frameworks
- 120.
- 123. We must holdframeworks makers accountable.
- 124.
- 125.
- 126.
- 127.
- 128. Building codes donot save us from bad design.
- 130. With a code,you can choose the right doors to nowhere
- 133. Thank you. Dylan Wilbanks Web:dylanwilbanks.com Twitter: @dylanw And other fine social media networks