4 ms·
A company's codebase is a liability, not an asset Why not just throw it away, then?
by iainmerrick 6y ago
A company's codebase is a liability, not an asset
Why not just throw it away, then?
- codebje 6y agoIf you can, you should. If you can't, it's (IMO) because you're stuck with the burden of having to write and maintain that code. If it's an asset, why not just write more?
- Eikon 6y ago> If it's an asset, why not just write more? Companies do write more.
- deleted 6y ago[deleted]
- goodside 6y agoIt’s a liability in the sense that a rusty drain pipe covered in duct tape is a liability. You think of it as the source of your problems, but throwing it away would be worse.
- robertlagrant 6y ago> It’s a liability in the sense that a rusty drain pipe covered in duct tape is a liability. You think of it as the source of your problems, but throwing it away would be worse. So in your analogy, what's the software equivalent of replacing the drain pipe?