[OpenDrapery]

I can tell that you are an architect from they way that you like to use the terms "right" and "wrong".

There is no right and wrong. There are only opinions and stylistic preference. There are solutions that are better and there are ones that are worse. But when you black box it and look at it from the outside, it either works or it doesn't.

[jib]

This is patently not true. :)

Everything is a spectrum, but there are also clear parts of the spectrum that contains death, and clear parts of the spectrum that are better than the others.

Works is not an acceptable standard. Imagine if we built bridges with the criteria that “well I crossed the river on it, so it works”. What tonnage can it support, how many years can it stay viable, does it fail gracefully if we drive something heavier than intended over it, what amount of wind can it take... none of those things are captured by “it works”.

Similarly for code. If your answer is “well something changed, so we need to refactor” or “well that wasn’t in the requirements so we can’t do that” then your solution didn’t work in the first place, because works implies scalability, extensibility, reliability etc.

Those are not style or opinion. Making anything “work” in the now is trivial. Building things that are not fragile to change and time is engineering.