12
How I stopped worrying and learned to love Eric Eggert, @yatil Fronteers 2012 Jam, 03.10.2012 DEFAULTS I am Eric Eggert and I’m not talking about accessibility today. I'm talking about defaults and how they help to improve the workflow.

How I stopped worrying and learned to love with defaults – with Notes

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: How I stopped worrying and learned to love with defaults – with Notes

How I stopped worrying and learned to love

Eric Eggert, @yatil

Fronteers 2012 Jam, 03.10.2012

DEFAULTS

I am Eric Eggert and I’m not talking about accessibility today. I'm talking about defaults and how they help to improve the workflow.

Page 2: How I stopped worrying and learned to love with defaults – with Notes

WTF are

DEFAULTS

I think about defaults as decisions that I made befor a decision is even necessary. Compare it to my iPhone 5 purchase, once I ordered it, the itch to go into a store and buy one reduced.

Page 3: How I stopped worrying and learned to love with defaults – with Notes

Design principles

For oneself, there are three states of rules: first, there are general design principles, second, there are conventions, e.g. In teams, and third there are defaults. They are very personal stuff.

Page 4: How I stopped worrying and learned to love with defaults – with Notes

Design principles

Conventions

For oneself, there are three states of rules: first, there are general design principles, second, there are conventions, e.g. In teams, and third there are defaults. They are very personal stuff.

Page 5: How I stopped worrying and learned to love with defaults – with Notes

Design principles

Conventions

Defaults

For oneself, there are three states of rules: first, there are general design principles, second, there are conventions, e.g. In teams, and third there are defaults. They are very personal stuff.

Page 6: How I stopped worrying and learned to love with defaults – with Notes

In case of conflict, consider users over authors over

implementors over specifiers over theoretical purity.

That's an example of an Design Principle by the w3c: the html5 spec says (read it) yet, in practice…

Page 7: How I stopped worrying and learned to love with defaults – with Notes

In case of conflict, consider implementors.

…we got this! (Read it)

So there are all those technologies around us, we shall use…

Page 8: How I stopped worrying and learned to love with defaults – with Notes

Grunt

Adobe EdgeVanillaJS

Boilerplate Wireframes

Photoshop MockupsPersonas

PubSubHububWordpress

Drupal

ContaoCSS Filters

Flash

Bootstrap

Boilerplate

Moodboards

NodeGIT

CVS

SVN

…WTF? I mean, that's a lot of stuff, that you’d need to learn. And most of this may not even be applicable to what you do anyways. So I'd like that you stick to your choices more often, it will improve how effective you are and may just produce good results.

Page 9: How I stopped worrying and learned to love with defaults – with Notes

Consider Apple. You may hate or love them, but they use that principle and sticked to some default. The 30 pin connector lasted for a long time, and now, it's time to replace it with the shiny *lightning* connector.

Page 10: How I stopped worrying and learned to love with defaults – with Notes

As you can see, it really is tiny, which was a requirement that Apple couldn't see until the iPhone5. Times changed and needs changed, so Apple changed its dock connector.

Page 11: How I stopped worrying and learned to love with defaults – with Notes

• Consider your choices carefully

• Stick to your decision, don't be a sissy

• Change as soon as you have to, but as late as you can

Just want to give you three points on your way before I leave:

Page 12: How I stopped worrying and learned to love with defaults – with Notes

THX!@yatil

yatil.net