News for hackers. Stuff that matters.
Re:You're not a senior engineer until you've worked on a leg... by indymike on Monday February 17, 2025 @01:54PM (#43082107)
> Haven’t you also often made a moat between yourself and doing literally anything else more interesting at the company

Nope, assuming that code works and handles UTF8 (sorry, but there is a point where it is too far gone to save). You’ve made yourself essential. You know the business better. You are strategic. And often, you become the one person who knows the legacy code base. And you will quickly find yourself a part of super important decisions. You’ll be called out regularly for fixing things that have gone unfixed for years. You’ll also drive value by helping the company avoid spending vast amounts of money re-implementing functioning code. On top of that, new product is often a mix of new and old, so you’ll quickly find yourself in the middle of new product teams.

Re:You're not a senior engineer until you've worked on a leg... by le-mark on Monday February 17, 2025 @07:46PM (#43084790)
These insights are essential for playing the long game; it may sound distasteful for people early in their careers. That’s fine, but when you’re running out the clock to retirement, can’t go wrong.
Re:You're not a senior engineer until you've worked on a leg... by kijin on Tuesday February 18, 2025 @12:33AM (#43086393)
It's not just about job security.

Even at a young age, some people find it super fascinating to work with old stuff and study the traces of people long gone.

If you're that kind of person, digging into an old assembly codebase is going to be so much more fun than learning some newfangled web framework.