On Fireproof, Future-Proof,
Failure-Proof Things.
Dylan Wilbanks
OpenWebCamp VI, July 2014
!
Web: dylanwilbanks.com
Twitte...
Two huge caveats.
1. I have (almost) no answers.
2. I have (almost) no takeaways.
Philadelphia.
https://www.flickr.com/photos/lschreur/101326235/
https://www.flickr.com/photos/ericsbinaryworld/130500981/
Fireproof?
http://www.sonofthesouth.net/leefoundation/civil-war/1865/february/philadelphia-fire.htm
What about the web?
“Building codes would never
work for building code.”
“It’s different!”
“The built environment
is planned!”
https://www.flickr.com/photos/structures-nyc-photos/5595474378/
“Development is not
pre-planned!”
“What’s on fire today?”
The Hierarchy of Startup Code Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
The Hierarchy of Startup Code Needs
No Money, Many Problems
MAKE IT RAAAAAAAAIN
MOAR MONEY!
MONEY
Let’s talk debt.
http://commons.wikimedia.org/wiki/File:Ward_Cunningham_at_Wikimania_2006.jpg
–Developer, Apptio
“Six years ago I was asked how long it’d
take for me to internationalize our code
base. I said two week...
Kinds of debt
• Technical debt
• Design debt
• Accessibility debt
• I18N debt
• Security debt
• DevOps debt
Tech debt
• Code upgrades
• Refactoring
• “Temporary” hacks
• TODO
• Not staying up to date
Design debt
• Poor usability
• Sub-optimal user flows
• Mobile Last, Mobile Not, What’s Mobile?
• “Experience rot”
• “Patch...
Accessibility debt
• Doesn’t work with screen reader
• ARIA hooks not used for AJAX-based sites
• Accessibility never test...
You will never not
have debt.
Resources vs. Revenue
But…
• Poor architecture kills velocity and sales
• We always have to keep up with change in
market, device, user
• Not pl...
What do we do?
We need a building
code for the web.
Clear rules:
Retrofit, replace, new construction
http://upload.wikimedia.org/wikipedia/commons/a/a3/New_and_Old_Bay_Bridge_(8859593785).jpg
http://www.districtenergy.org/blog/wp-content/uploads/2013/10/Seattle-SouthLakeUnionAerial_big.jpg
Standard sizes,
standard practice.
https://www.flickr.com/photos/duiceburger/3312213574/
http://idighardware.com/2010/01/survey-q3-how-can-you-tell-a-fire-door-from-a-regular-door/
Beyond web standards,
beyond frameworks,
it’s practice.
What can we do?
My little part for UX
StoryCore
2014 Home Edition Live* 365! (pre-alpha preview)
StoryCore
• Bootstrap for applications
• Sets the nuts and bolts pieces in place for a
basic web application
• Import stor...
Available… soonish.
What are you going
to do?
Kinds of debt
• Tech debt
• Design debt
• Accessibility debt
• I18N debt
• Security debt
• DevOps debt
Thank you.
Dylan Wilbanks
Web: dylanwilbanks.com
Twitter: @dylanw
And other fine social media networks
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
Upcoming SlideShare
Loading in...5
×

Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.

895

Published on

The moment we start creating a website, we’re setting ourselves up for failure later. Bad code creates middle of the night fire drills. Lack of thinking about accessibility gets our employer sued. Not thinking ahead on mobile generates rework.

We accept this as the normal course of business — but is there any way we could prevent (or lower) this cost? Is there anything we can learn from the building codes that dictate how our built environment is constructed?

A quick tour of how we got where we are with the web, and perhaps some valuable takeaway points.

Published in: Internet
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
895
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.

  1. 1. On Fireproof, Future-Proof, Failure-Proof Things. Dylan Wilbanks OpenWebCamp VI, July 2014 ! Web: dylanwilbanks.com Twitter: @dylanw
  2. 2. Two huge caveats.
  3. 3. 1. I have (almost) no answers. 2. I have (almost) no takeaways.
  4. 4. Philadelphia.
  5. 5. https://www.flickr.com/photos/lschreur/101326235/
  6. 6. https://www.flickr.com/photos/ericsbinaryworld/130500981/
  7. 7. Fireproof?
  8. 8. http://www.sonofthesouth.net/leefoundation/civil-war/1865/february/philadelphia-fire.htm
  9. 9. What about the web?
  10. 10. “Building codes would never work for building code.”
  11. 11. “It’s different!”
  12. 12. “The built environment is planned!”
  13. 13. https://www.flickr.com/photos/structures-nyc-photos/5595474378/
  14. 14. “Development is not pre-planned!”
  15. 15. “What’s on fire today?”
  16. 16. The Hierarchy of Startup Code Needs Technical debt New features Fixing bugs in working code Shipping working code
  17. 17. The Hierarchy of Startup Code Needs No Money, Many Problems MAKE IT RAAAAAAAAIN MOAR MONEY! MONEY
  18. 18. Let’s talk debt.
  19. 19. http://commons.wikimedia.org/wiki/File:Ward_Cunningham_at_Wikimania_2006.jpg
  20. 20. –Developer, Apptio “Six years ago 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.”
  21. 21. Kinds of debt • Technical debt • Design debt • Accessibility debt • I18N debt • Security debt • DevOps debt
  22. 22. Tech debt • Code upgrades • Refactoring • “Temporary” hacks • TODO • Not staying up to date
  23. 23. Design debt • Poor usability • Sub-optimal user flows • Mobile Last, Mobile Not, What’s Mobile? • “Experience rot” • “Patch and paint” UX solutions instead of “replacing the wall”
  24. 24. Accessibility debt • Doesn’t work with screen reader • ARIA hooks not used for AJAX-based sites • Accessibility never tested, never a priority • “Yes, but are they the 80% case?”
  25. 25. You will never not have debt.
  26. 26. Resources vs. Revenue
  27. 27. But… • Poor architecture kills 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)
  28. 28. What do we do?
  29. 29. We need a building code for the web.
  30. 30. Clear rules: Retrofit, replace, new construction
  31. 31. http://upload.wikimedia.org/wikipedia/commons/a/a3/New_and_Old_Bay_Bridge_(8859593785).jpg
  32. 32. http://www.districtenergy.org/blog/wp-content/uploads/2013/10/Seattle-SouthLakeUnionAerial_big.jpg
  33. 33. Standard sizes, standard practice.
  34. 34. https://www.flickr.com/photos/duiceburger/3312213574/
  35. 35. http://idighardware.com/2010/01/survey-q3-how-can-you-tell-a-fire-door-from-a-regular-door/
  36. 36. Beyond web standards, beyond frameworks, it’s practice.
  37. 37. What can we do?
  38. 38. My little part for UX
  39. 39. StoryCore 2014 Home Edition Live* 365! (pre-alpha preview)
  40. 40. StoryCore • Bootstrap for applications • 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
  41. 41. Available… soonish.
  42. 42. What are you going to do?
  43. 43. Kinds of debt • Tech debt • Design debt • Accessibility debt • I18N debt • Security debt • DevOps debt
  44. 44. Thank you. Dylan Wilbanks Web: dylanwilbanks.com Twitter: @dylanw And other fine social media networks
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×