3 ms·
I also found myself getting stuck and over-engineering. Now, I try to take a phased approach to development: 1. Make it work. 2. Make it good (visually or oth
by Aqua_Geek 14y ago
I also found myself getting stuck and over-engineering. Now, I try to take a phased approach to development:
1. Make it work.
2. Make it good (visually or otherwise).
3. Make it fast.
- arethuza 14y agohttp://c2.com/cgi/wiki?MakeItWorkMakeItRightMakeItFast http://c2.com/cgi/wiki?MakeItWorkMakeItRightMakeItFast
- slantyyz 14y agoThe saying Firmitas, Utilitas, Venustas comes to mind.
- chmike 14y agoThis good. But how do you handle it when designing a protocol and a data encoding ? You can't iterate.
- wpietri 14y agoAll good design comes from iteration. You can certainly do with protocols and encodings. Look at the very first published swing at HTTP, for example: http://www.w3.org/History/19921103-hypertext/hypertext/WWW/Protocols/HTTP.html http://www.w3.org/History/19921103-hypertext/hypertext/WWW/P... From today's modern perspective, it's laughable. And that was just the first public bit. Surely he iterated some on his own before putting that out.
- betadj 14y agoMake it fast only when you have to! I've seen too many projects focus on performance before traffic comes, most of time traffic never comes.