> is how you get hundreds of poorly written spaghetti code
So what you are saying is that the IoC / Decorator approach is the way to avoid spaghetti code? That's an interesting assertion.
> You are setting yourself up for some bad tech debt in the future
You mean like being saddled with a product that depends on a large framework that fewer and fewer people want to deal with?
The way to avoid tech debt is to retain plasticity, keep more options open and not paint yourself into a corner where your choice of framework dictates how you structure entire systems.
And, of course, to hire people based on talent and ability rather than a line on their CV that promises experience with a given framework.
So what you are saying is that the IoC / Decorator approach is the way to avoid spaghetti code? That's an interesting assertion.
> You are setting yourself up for some bad tech debt in the future
You mean like being saddled with a product that depends on a large framework that fewer and fewer people want to deal with?
The way to avoid tech debt is to retain plasticity, keep more options open and not paint yourself into a corner where your choice of framework dictates how you structure entire systems.
And, of course, to hire people based on talent and ability rather than a line on their CV that promises experience with a given framework.