10 years ago, I thought I could solve any problem with any tool handed to me. I suppose my definition of "solve" has since changed. Simply solutioning for any single customer request is certainly not solving anything. That’s because there will be subsequent requests, the product owner or business goals will change, the scale will change, and there is no crystal ball that properly forecasts the future. Solving for a single request without thinking about scalability means you, the developer will create technical debt from day one, a year down the road the team will begin to hit a wall and the refactoring tickets will start to come in. It doesn’t have to go that way. There is another path that allows for improvements in velocity and scale with very little accumulation of technical debt. Instead of refactoring code, refactor your approach to development and you will, in very little time, build simple, scalable systems that outperform. You may even find yourself in situations where future requests are already inherently solved by the simplicity of the design.
Learn More