19 Years of Spring Mistakes: What Every Framework Maintainer Should Know

Spring's annotation model made MVC hugely popular but introduced a steep learning curve for extension and debugging. The functional alternative, while less adopted, produced fewer bugs and was easier to maintain. The tradeoff between ease of use and extensibility is a recurring theme.

HTTP client APIs evolved from a monolithic RestTemplate to a guided state-machine design. The lesson: explicit APIs that steer users reduce errors. The URI encoding dilemma shows that "clever" behavior breaks for edge cases; offering both encoded and unencoded options is safer.

The HTTP method enum mistake took five years to fix, only possible because a forced recompilation allowed breaking changes. This illustrates the change event horizon: foundational frameworks cannot easily correct errors, so design decisions have decades-long consequences.

Poutsma's closing principles—empathy, humility, restraint—are not soft skills. They shape API design, bug report handling, and feature selection. "When in doubt, leave it out" is a concrete rule that prevents future technical debt.