making the web fireproof: a building code for websites
Post on 15-Jul-2015
4.316 Views
Preview:
TRANSCRIPT
Making the Web Fireproof: A Building Code for Websites
Dylan Wilbanks MinneWebCon 2015
Web: dylanwilbanks.com Twitter: @dylanw
https://www.flickr.com/photos/valkrye131/3240437070/
http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
But is it fireproof?http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
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/
http://council.seattle.gov/2013/02/11/new-funds-for-preservation/
http://www.districtenergy.org/blog/wp-content/uploads/2013/10/Seattle-SouthLakeUnionAerial_big.jpg
http://upload.wikimedia.org/wikipedia/commons/a/a3/New_and_Old_Bay_Bridge_(8859593785).jpg
“Building codes would never work for building code.”
https://www.flickr.com/photos/tambako/14065508649/
https://www.flickr.com/photos/christinyca/15875497176/
“The built environment must be planned in advance!”
http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
Let’s talk debt.http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
http://commons.wikimedia.org/wiki/File:Ward_Cunningham_at_Wikimania_2006.jpg
Ward Cunningham
Kinds of debt• Tech debt
• Design debt
• Accessibility debt
• I18N debt
• Security debt
• DevOps debt
Design debt• Usability compromised 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”
Accessibility debt
• Doesn’t work with screen reader
• ARIA hooks not used or set up properly
• Accessibility never tested, never a priority
• “Yes, but are they the 80% case?”
–Developer, (company redacted)
“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 have time. Now, it would take
months of work — with multiple developers.”
http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
What’s on fire today?http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working codeMONEY
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
MOAR MONEY!
MONEY
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
MAKE IT RAAAAAAAAIN
MOAR MONEY!
MONEY
The Hierarchy of Needs
Technical debt
New features
Fixing bugs in working code
Shipping working code
No Money, Many Problems
MAKE IT RAAAAAAAAIN
MOAR MONEY!
MONEY
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
What would it look 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”
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
http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
But… fireproof?http://upload.wikimedia.org/wikipedia/commons/3/32/Fire-Forest.jpg
top related