Skip to content

Comment on Ask HN: Senior engineers, how do you deal with poorly written software?

Comments

"Poorly" (in quotes because it's a relative term) written codebases are the best:

- tons of opportunities to improve things!

- fixing bugs is like being Sherlock Holmes. I enjoy that

- and the best is: if you need to deliver something that has a deadline and you couldn't make it, you can always blame the "poorly" written codebase

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.