←back to thread

873 points belter | 1 comments | | HN request time: 0.215s | source
Show context
donatj ◴[] No.42948747[source]
> Most programming should be done long before a single line of code is written

This is the only point I strongly disagree with. I have been doing this for twenty years now and every time we've gone into something with a STRONG plan for how it's going to be built, it's ended up an inflexible nightmare when we inevitably end up having to work around things that were not considered in the design phase.

The plan always ends up bumping into unforeseen realities, and you end up with sunk cost around the planning so instead of pivoting you keep on suboptimal course.

You can spend months planning the smallest feature and there will always be something you did not consider.

Rapid prototyping in my experience is the way. Throw something together that works, see how it can be improved, don't be afraid to throw the entire thing out.

replies(3): >>42948976 #>>42949171 #>>42949782 #
1. bluGill ◴[] No.42949782[source]
There needs to be a balance of course, but eventually you will have code/interfaces that are too painful to change because of all the users. The more core code is the more painful it will be to change and so the more a well thought out strong design is needed. The less core the code is, the less strong the design needs to be - but often the code code will force some design on you.

Of course there will always be something you didn't consider.