The biggest and most costly mistakes in my career weren't hidden in a line of code or a misconfigured network. In fact, my most expensive lessons came from the indirect consequences of saying "yes" to a task or taking on a responsibility. As a system architect, one of the most important things I wish I had learned earlier was this: you can't do everything, and trying to do so can cause more damage than even the greatest technical debt.
For twenty years, while navigating between systems and networks, I've encountered many complex problems. From PostgreSQL WAL bloat to AI-driven production planning algorithms in a manufacturing ERP, I've delved deep into technical stacks. However, during this process, I realized that the way people communicate, their expectations, and their boundaries are just as critical as the technology itself.
The Cost of Saying 'Yes' to Everything
Over the years, I found myself on many projects. Especially while developing an ERP for a manufacturing company, saying "yes, we can do it" with every new request became almost a reflex. These decisions, made in the name of customer satisfaction, flexibility, and rapid adaptation, might have seemed to work in the short term, but in the long run, they insidiously eroded the project's core architecture and the team's energy.
