A twenty-year-old backend with no framework underneath it is still the one in production

The backend is unframeworked — built up directly over roughly two decades rather than on top of a maintained framework that would have carried it through version upgrades and security patches along the way. On the front end, the engineering conventions still list largely superseded frameworks as acceptable choices alongside current ones, and treat a modern, type-safe language as optional rather than the standard it's become at most software companies built in the last several years. Both are the kind of detail that shows up in a job posting or a contributor guide long before it shows up in the product.

An unframeworked backend built over two decades accumulates its own bespoke patterns that only the people who wrote them fully understand — there's no framework's own documentation or community to fall back on when someone new joins the team. Combined with front-end tooling that hasn't standardized on current practice, the practical cost is slower onboarding for new engineers, higher risk in every change because there's less structure catching mistakes, and a widening gap against how a comparable product would be built today.