“If Tetris has taught me anything, it’s that errors pile up and accomplishments disappear” is a common quote and it seems we’re living this to its full extend as web developers. We fail to celebrate the successes we have and the tools that are at our disposal but we’re never short of finding reasons why things don’t work. We also tend to pile on technology on technology to solve problems that may actually not exist and thus clog up the web. In this talk Chris Heilmann wants to remind us what we achieved and how we should celebrate it and how we should stop trying to solve problems that are simply beyond our control.
10. conservativeinnovative
controlling trusting
The right, conservative piece…
Progressive enhancement is the way to build
working solutions. You build on static HTML
generated from a backend and you will never break
the user experience.
11. conservativeinnovative
controlling trusting
The right, conservative piece…
You have no right to block any user.
The web is independent of device and ability. It is
our job to make sure people can use our products.
We do that by relying on standards.
26. conservativeinnovative
controlling trusting
The innovation piece…
The concept of starting with a text editor and static
files is outdated. We have so much more benefits
from using a proper toolchain. If that’s too hard for
you, then you’re not a web developer.
27. conservativeinnovative
controlling trusting
The innovation piece…
Web standards like CSS, JavaScript and HTML are
conversion targets. Sass, CoffeeScript, Elm,
Markdown and Jade gives us more reliable control
right now, not when browsers catch up.
31. conservativeinnovative
controlling trusting
The innovative blocker…
CSS is broken. The DOM is broken. We have the
technologies in our evergreen browsers to fix all
that reliably as we have insight into what’s
happening and can optimise it.
35. conservativeinnovative
The difference is responsibility and support.
controlling trusting
End users can cater the
interface to their needs,
products run everywhere.
High responsibility, high
demand on the end
user’s environment.
37. Who has the final say how
an interface looks and
what it is used for?
38. conservativeinnovative
Users over authors over implementors over
specifiers over theoretical purity…
controlling trusting
https://www.w3.org/TR/html-design-principles/
39. If our users are the end goal, findings and best
practices should go both ways.
conservativeinnovative
controlling trusting
50. ▪ Manifests
▪ Service Workers
How much of a great
opportunity are
Progressive Web Apps?
51. ▪ In-browser tooling
▪ Hackable editors written in
web technologies.
▪ Toolchains to produce what
we need when it makes sense!
How amazing are our
developer tools?
52. ▪ Browser makers are available
for feedback and information.
▪ We have collaboration tools
by the truckload
▪ We have more events than I
can count with published
videos
How easy is it for us to
stay up-to-date?
56. It is not OK for them to
become landfill of the web.
57. Our job right now is to
create interfaces that are
simple, human and fun
to use…
58. There is no such thing as a perfect user - think inclusive.
https://www.microsoft.com/en-us/Design/inclusive
It isn’t about allowing access but about avoiding barriers.
59. Users over authors over implementors over
specifiers over theoretical purity…
https://www.w3.org/TR/html-design-principles/
60. We have come a
long way.
We made the world
much smaller and
more connected.
61. Things are looking up.
I can’t wait to see what all
of you - together - will
come up with next.
62. Let’s storyboard the next
web.
Use Codepen, JSBin, all the
fiddles out there.
Give feedback on
standards and browser
features
63. Let’s stop fussing over
minor details, and show
more love to the web,
love to the craft and much
more respect for another.
64. You don’t owe the world
perfection.
But you have a voice that
should be heard and your
input matters.
Get creative – no creativity
is a waste.