3 ms·
First make it work, then make it correct, then document it, then make it efficient, then make it pretty. Rarely all stages are reached, but in open source proj
by ASalazarMX 9y ago
First make it work, then make it correct, then document it, then make it efficient, then make it pretty.
Rarely all stages are reached, but in open source projects, anyone can cook their favorite dish for this dinner.
- briandear 9y agoThe problem with that is that “pretty” is implying simple visual beauty. It diminishes what design really is: the way something works not simply how it looks. “Pretty” should be integral to “make it work.” If your design is good, it’s more self-documenting, so pretty early in the process means less work documenting — it also reveals more of the essence of what exactly you are building which then helps drive the decisions on what to build next. Design shouldn’t be an afterthought, it should be THE thought.
- ASalazarMX 9y agoI disagree. If you make something, THE thought is that it fulfills its function correctly. I wouldn't pursue an excellent UX if the inner workings are buggy.