Open Web Camp 2014: On Fireproof, Future-Proof, Failure-Proof Things.
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.
“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
• 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)
2014 Home Edition Live* 365! (pre-alpha preview)
• 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