4 ms·
Absolutely. I delay coding for as long as humanly possible. Mostly because I hate having to re-do work. So I'll usually spec out my schema, sitemaps, full mocku
by MalcolmDiggs 12y ago
Absolutely. I delay coding for as long as humanly possible. Mostly because I hate having to re-do work. So I'll usually spec out my schema, sitemaps, full mockups of everything, etc. Then I write my tests, and finally my code dead last.
The point for me is to make all the creative decisions (and to do all the creative waffling and do-overs) very early on in the process, on the whiteboard instead of in the IDE (because it's faster to change functionality during the mockup stage than it is to rip out your code). Once I start coding everything should be spec'd in detail.
- panjaro 12y agoThumbs Up ! I prefer the same but in the office I work in, they focus in getting the product to client as soon as possible and it's just getting tough for developers (ones who care about good practice). However, company is just getting lot of clients and earning very well. It got me thinking whether I'm not being quick to develop.....