Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Feeling this now. I'm at a company doing client work for a client that has a huge codebase previously all developed/maintained by us. It's legacy, and it does have some rough edges, but the code was cleaner than 95% of codebases I've seen, it was stable, it worked really well, and it was consistent and feature-rich. They hired a new team that doesn't understand (or care to understand) any of the existing code so it's all being reimplemented as hacky ad-hoc microservices and React apps. They can't replace it all at once so an API layer has been awkwardly wedged into the existing legacy codebase, creating problems in pretty much all of the core data models. That layer was "completed" a year ago and I'm still finding places where it completely breaks basic features of the existing apps. The new apps are usually not well-specced or scheduled so they are MVP at best and often contain some really silly bugs that break their API server and thus bring down all of the new and old apps.