A developer's job is to find the simplest solution to a problem. But being simple is actually harder than it sounds.
So why are you over-engineering everything ?
Let me introduce you to Toto.
Toto just finished a great training program. He learned architecture, good practices, microservices, DevOps with Kubernetes, Jenkins, the whole thing. Now Toto has to build an app for a client probably under 1,000 users.
But Toto builds a microservice for every feature. Multiple databases. A massive CI/CD pipeline. He thinks he is doing the right thing. But he is not. He does not need any of that.
Six months later.
Bug in production. 2am. Toto's mega-architecture is down. He has to debug alone across 12 microservices and his mind keeps saying if only I had kept it simpler. If only I had built an architecture that matched my actual needs.
The message is simple.
Use the architecture and tools you actually need. A solid monolith, Docker, and GitHub Actions will handle 90% of real projects. Microservices are not a sign of skill knowing when NOT to use them is.
Don't fall into this trap. I almost did. Maybe you will too.
This story is fictional. But you probably know a Toto.
Top comments (0)