http://tatiyants.com/devops-is-ruining-my-craft/
First time I disagree with an article from ThoughtWorks.
Monoliths are not a bad design, not at all. The solution to all the problems you raised has been created more than 20 years ago, it is called object oriented programming.
You expediate this solution with statements such as "while this... In practice we see...". And I think this is unfair because the only reason most messy monoliths are messes is because most of the developers DO NOT KNOW Object-Oriented Programming.
If their learned OOP the same way you ask them to learn micro-services, things would be different.
People list OOP on their CV but are not able to model a OOP domain model. I've interviewed many people and most of them had no clue. They only know about textbook situations, and can't leverage OOP in a real world project.
I developped a very complex system, with many modules and dependencies. When I left the company, I wrote up a documentation and insisted to have people ask me questions. I ended it up with 1 question. 1 question for a complex ERP System. People picked it up in 2-3 days, adding features and maintaining it. It was a walk in the park. And it was a monolith.
First time I disagree with an article from ThoughtWorks.
Monoliths are not a bad design, not at all. The solution to all the problems you raised has been created more than 20 years ago, it is called object oriented programming.
You expediate this solution with statements such as "while this... In practice we see...". And I think this is unfair because the only reason most messy monoliths are messes is because most of the developers DO NOT KNOW Object-Oriented Programming.
If their learned OOP the same way you ask them to learn micro-services, things would be different.
People list OOP on their CV but are not able to model a OOP domain model. I've interviewed many people and most of them had no clue. They only know about textbook situations, and can't leverage OOP in a real world project.
I developped a very complex system, with many modules and dependencies. When I left the company, I wrote up a documentation and insisted to have people ask me questions. I ended it up with 1 question. 1 question for a complex ERP System. People picked it up in 2-3 days, adding features and maintaining it. It was a walk in the park. And it was a monolith.
Comments
Post a Comment