←back to thread

873 points belter | 1 comments | | HN request time: 0.225s | 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. nicce ◴[] No.42949171[source]
I would say it depends on your domain expertise and the expertise of the chosen programming language. Of course, for very large projects with multiple unknown integrations this is not the case.

But if you are an expert in both of domain and the technology itself, you can well design it before starting the coding, because you already know the technical issues you are likely facing.

At least I have personally managed to design some projects and implement them without any design changes. But I also read countless blog posts about the limitations of these programming languages every day.