It comes down to cuture and how people you work with think and perform when building software. Experienced developers will know that spending time not writing

It comes down to cuture and how people you work with think and perform when building software. Experienced developers will know that spending time not writing code is where you really solve the challenges at hand. It's not about patterns or arc' style, that is merely a tool to reach the goal. It's about experience and knowing when step back and iterate, and take the time needed to solve something. I often spent months breaking a problem down, and in that period of time I often realize that I was on the wrong foot from the beginning. So I iterate once again, slowly building confidence in a better solution. And in those months of tinkering I don't write production code that problem. Quality work takes time to do, it's a oneway street that thing.