3 ms·
There's a difference between moving fast and doing sloppy work. IMO, this post is a recipe for mediocre design (at best). Don't confuse movement for work - when
by nbashaw 16y ago
There's a difference between moving fast and doing sloppy work. IMO, this post is a recipe for mediocre design (at best). Don't confuse movement for work - when you approach a design with the a rushed attitude it slows you down in the long run, because you have to clean up your mistakes and possibly start over again when you realize that your first attempt just didn't work at all.
I'm not so much arguing with the specific suggestions in the post as I am the general approach and worldview. There are some useful ideas in there, but they're weakened by being presented in "recepie" format. Sometimes they make sense, sometimes they don't. It depends on the context. Better to learn principles than methods. It's quicker in the long run.
- minouye 16y agoThere is definitely a balance between speed and quality. The author here is advocating methods that will enable a single founder to push out an MVP as quickly as possible (while still maintaining some degree of aesthetic appeal). The recipe is absolutely useful in the same way that purchasing a template is useful. As long as it doesn't get in the way of your functionality, you can ship and start iterating with real users.
- DennisP 16y agoThe article is aimed at programmers without design skills. If you can teach them to create great designs instead of just half-way decent ones, write something up!
- nbashaw 16y agoGood challenge! I think I'll take you up on it. That's a good Sunday project.