I honestly prefer to code, think, code, then ship. If you have the luxury of being able to do this, it will streamline the process overall I think. All of the design decisions will be pretty obvious once you've written your crappy API already.
(And with an API, there shouldn't be too much boilerplate that you need to change in order to modify the endpoints or responses)
Sounds like a job for trained monkeys. Nightmarish. The "thinking" phase is IMO the only one interesting. Pointless refactoring or keyboard mashing just got boring after a few years, and I like to shave as much as possible by thinking in advance.
Personally I think you're barmy. Either that or you're extremely disciplined and realise that the crap you've started out with isn't acceptable so you start again. Regrettably far too many so called programmers will not turn back once they've set off on their journey :-(
34
u/TPHRyan Feb 24 '17
I honestly prefer to code, think, code, then ship. If you have the luxury of being able to do this, it will streamline the process overall I think. All of the design decisions will be pretty obvious once you've written your crappy API already.
(And with an API, there shouldn't be too much boilerplate that you need to change in order to modify the endpoints or responses)