Hacker News new | ask | show | jobs
by pm 3385 days ago
What's the legacy codebase, if I may ask (unless it identifies the company too much)?
1 comments

Some of it is so obsolete and unique it would probably identify the company :) . The rest is slightly less old, MS webforms.

The webforms stuff isn't much better because the code quality is the worst I've ever seen. Adding features and fixing bugs is a stochastic process because you never know what will break.

Usually fixing a bug will expose an old fix that was done improperly for the original even older bug, forcing you to undo multiple levels of hacks to implement your own. It's nightmarish

Patches all the way down, it seems. I've had to deal with similar codebases. I try to fix what I can, but it always seems to be a neverending process.

Legacy codebases suck, but it doesn't stop newer codebases from sucking just as much. I've learnt that the hard way.

Yes. The codebase is best described as a giant pile of hacks.

It's the culture more than the tech that causes this to happen. Every time I offer to refactor I'm told to fix it the fastest way and that's how we've been doing it for 10+years.

Every time I offer to refactor I'm told to fix it the fastest way and that's how we've been doing it for 10+years.

Ok, as someone with a strong dislike for modern js I still feel sorry about this.

Sounds like it's time to get out then. I don't know how hard that would be as you said you moved cross-country, so you could be anywhere (in the US I'm guessing). Remote work is always handy.