I feel when designing software there's generally two approaches to implementing features: "we'll take care of it" vs "someone else will have to take care of it". If a program takes care of too little it'll feel boilerplaty (or useless). Too much and it'll feel restrictive.
-
Show this thread
-
Generally when deciding to implement features I like to ask: "is this something thats useful to have opinions about?" If the answer is "sometimes", then ask: "can we provide a default, but also a way to configure it?" If the answer is "always yes", then config can distract.
1 reply 1 retweet 4 likesShow this thread -
It feels so often software is created through anti-design. Out of fear of making a wrong decision we don't choose between options, but instead opt to add both. It feels neutral, it feels safe. But it lacks deliberation. If "design" is making choices, then this is the opposite.
1 reply 2 retweets 11 likesShow this thread
Anyway, I've been working on some fun libraries recently and have been thinking a lot about design! Very happy with the resulting work, and excited for it to be released ^^
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.