Download to read offline
Uploaded byDylan Wilbanks
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
The document discusses the various types of debt in web development, including technical, design, accessibility, internationalization (i18n), security, and devops debt. It emphasizes the importance of planning and establishing a 'building code' for the web to manage these debts effectively, as unaddressed debt can hinder velocity, sales, and overall functionality. The author proposes a structured approach for applications through a project called Storycore, aimed at setting essential requirements for user experience, accessibility, and security.
More Related Content
![[Access U 2010] HTML5 & Accessibility](https://cdn.slidesharecdn.com/ss_thumbnails/accessuhtml5andaccessibilityv2-100511152310-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![Designing with Empathy [Reasons to be Creative 2013]](https://cdn.slidesharecdn.com/ss_thumbnails/designingwithempathyreasonstobecreative-130903035840-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
- 1. On Fireproof, Future-Proof, Failure-ProofThings. Dylan Wilbanks OpenWebCamp VI, July 2014 ! Web: dylanwilbanks.com Twitter: @dylanw
- 2.
- 3. 1. I have(almost) no answers. 2. I have (almost) no takeaways.
- 4.
- 5.
- 6.
- 10.
- 11.
- 15. What about theweb?
- 16. “Building codes wouldnever work for building code.”
- 17.
- 18. “The built environment isplanned!”
- 19.
- 20.
- 23. “What’s on firetoday?”
- 24. The Hierarchy ofStartup Code Needs Technical debt New features Fixing bugs in working code Shipping working code
- 25. The Hierarchy ofStartup Code Needs No Money, Many Problems MAKE IT RAAAAAAAAIN MOAR MONEY! MONEY
- 26.
- 27.
- 28. –Developer, Apptio “Six yearsago I was asked how long it’d take for me to internationalize our code base. I said two weeks. But we didn’t do it. Now, it would take months of work — with multiple developers.”
- 29. Kinds of debt •Technical debt • Design debt • Accessibility debt • I18N debt • Security debt • DevOps debt
- 30. Tech debt • Codeupgrades • Refactoring • “Temporary” hacks • TODO • Not staying up to date
- 31. Design debt • Poorusability • Sub-optimal user flows • Mobile Last, Mobile Not, What’s Mobile? • “Experience rot” • “Patch and paint” UX solutions instead of “replacing the wall”
- 32. Accessibility debt • Doesn’twork with screen reader • ARIA hooks not used for AJAX-based sites • Accessibility never tested, never a priority • “Yes, but are they the 80% case?”
- 34. You will nevernot have debt.
- 35.
- 37. But… • Poor architecturekills velocity and sales • We always have to keep up with change in market, device, user • Not planning for I18N is costly • Bad security mistakes cost us money (and face) • Bad accessibility costs us face (and money)
- 39. What do wedo?
- 40. We need abuilding code for the web.
- 41. Clear rules: Retrofit, replace,new construction
- 43.
- 44.
- 45.
- 46.
- 48.
- 50. Beyond web standards, beyondframeworks, it’s practice.
- 52. What can wedo?
- 53. My little partfor UX
- 54. StoryCore 2014 Home EditionLive* 365! (pre-alpha preview)
- 57. 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
- 58.
- 59. What are yougoing to do?
- 60. Kinds of debt •Tech debt • Design debt • Accessibility debt • I18N debt • Security debt • DevOps debt
- 64. Thank you. Dylan Wilbanks Web:dylanwilbanks.com Twitter: @dylanw And other fine social media networks