← sources

Advice from devs who unexpectedly found themselves working with really bad legacy code?

source: reddit (reddit:cscareerquestions)published 2026-10-26 23:29ingested 2026-10-27 02:36

retained text

I'm a dev with 6 years of experience. I left my old company and joined a new company for family and mental health reasons. I really miss my old company and its modern tech stack, the good engineering practices, the team oriented and positive culture, and integration and units tests...

This new company has an older tech stack which I knew coming in. But naively, I was not prepared for the legacy code I would encounter. I can only speak to the team I'm on now, but the engineering practices are bad as well. Just to mention a few things: There are no tests, little to no code reviews, and there are no naming conventions and bloated methods (40k+ lines).

I plan to read Michael Feathers' "Working Effectively with Legacy Code" and keep at it. But I'm curious, are there other experienced devs who have experienced this? Do you have any advice or recommendations? Did it hurt your confidence as an engineer or do you think you eventually grew into a stronger engineer from this experience? Did the codebase get better and how long did it take?

document fetched 2026-10-27 00:24 · canonical https://reddit.com/r/cscareerquestions/comments/1xgcpqe/advice_from_devs_who_unexpectedly_found