Without questioning the usefulness and effectiveness of frameworks, I was thinking that choosing a framework for implementation, especially in small teams (the ones I write about), requires constantly measuring the framework against your actual scale. And not being afraid to adapt it, remove what’s unnecessary, and test it in practice.
This one post is equivalent to an MBA in itself! mind-blowing! take a bow Torsten
Excellent article. Thank you so much!
Without questioning the usefulness and effectiveness of frameworks, I was thinking that choosing a framework for implementation, especially in small teams (the ones I write about), requires constantly measuring the framework against your actual scale. And not being afraid to adapt it, remove what’s unnecessary, and test it in practice.
thank you , super celar and helpful
What a solid guide. It's great to have a comprehensive list of frameworks and all the examples illustrating the points.
Very interesting statement.
I can confess that, when I read the title of this post, I was understanding that you refer to frameworks like Spring, Django or things like this.
After reading the post, I find that you refer to t patterns and rules to solve problems.
I'm 💯 agree that the usage of known patterns is the way to go and one of the best skills an engineer must drive.
Thanks for sharing!