10 principles for effective front-end development, the text version
I saw some inspiring slides from Harry Roberts this morning and thought I'd share it in text form for those who like to scan.
The simplest option is usually the best.
faster and cheaper to implement
easier to understand, inherit, maintain, and debug
less likely to fail or break
lessens amount of cognitive overhead when working at scale
Reduce the amount of moving parts.
get rid of as much as you can
every moving part is a potential point of failure
you’re inviting the chance for something to go wrong
reduce both features and code
code is a means to an end
understand the business cost and value of your work
don’t waste other peoples’ money
Care less, care appropriately.
no one cares about your code more than you do
balance the needs of everyone
there’s a much bigger picture to look at
Pragmatism trumps perfection.
“good enough” today is better than “perfect” tomorrow
measure features by their business value
your job isn’t just to reproduce designs anymore
do not put yourself in a bubble
get involved with everyone else’s issues
do what’s right for the product
Do not design systems around edge cases.
don’t let the minority lead the majority
build for the most common scenario first
solve edge cases separately
Do not make decisions based on anecdotal evidence.
anecdotes are not representative
anecdotes are isolated incidents
Don’t build it until you’ve been asked for it.
you’ve caused yourself work, and cost the business money
no spec, so how do we know it’s right? how do we test it?
could end up influencing the rest of the project
now you have to maintain something that no one ever wanted
solve each problem as you encounter it
Expect and accommodate change.
always keep adaptable, flexible, and nimble
everything is subject to change
yousharknotpass
jimmyeatworldofficial
tangentwithtanner
theartofmadeline
amandla
titsay
romaincrisis