[mattmanser]

I've been doing this a long times and I've never had to do that and have delivered multiple successful products used by millions of users. Some of which were used for years after we stopped doing any sort of even maintaining with no bugs, problems or crashes.

There are only a few software architecture patterns because there's only a few ways to solve code architecture problems.

If you're getting your initial design so wrong that you have to start again from scratch midway through, that shows a lack of experience, not insight.

You wouldn't know this, but I'm also a bit of an expert at refactoring, having saved several projects which had built up so much technical debt the original contractors ran away. I've regularly rewritten 1,000s if not 10,000s of line into 100s of lines of code.

So it's especially galling to be told not only that somehow all code problems are unique (they almost never are), but my code is building technical debt (it's not, I solve that stuff).

Most problems are solved, and you should be using other people's solutions to solve the problems you face.