My most expensive career mistake wasn't a line of code or a misconfigured server; it was a "yes." Throughout my twenty years of experience in system architecture and operations, I've made countless technical decisions, often succeeding, sometimes making mistakes. However, some decisions cost not just time or money, but also shape our perspective and future.
In this post, I'll share the "yes" decision that cost me the most as an engineer, and the lessons learned from it, not as dry technical details, but as a lived story. My aim is to highlight not just technical correctness, but also the critical role of emotional intelligence and strategic thinking in engineering.
That 'Yes' Moment: A Turning Point
It all began with a project to modernize the ERP system for a large manufacturing firm. The existing system was a tangled mess accumulated over years, severely hindering operational efficiency. Instead of implementing a new system, we decided to improve the current one. This improvement essentially meant a massive rewrite. Proposals were received, projects were drawn up, and budgets were prepared. It was at that precise moment that I said "yes" to the team who said, "We can fix the existing system while it's running, instead of building from scratch."
