News for hackers. Stuff that matters.
Re:Ask HN: Working with a monolithic codebase by pjc50 on Monday January 11, 2016 @12:38PM (#10881817)
It's kind of like conventional depreciating capital assets like buildings. A building requires maintenance, utilities, taxes, repairs and so on. If your building is too large for your needs, the costs can become a debilitating albatross round the neck of the business. There have been plenty of European aristocracy bankrupted by having a house that was too big.

In programming terms, it's very tempting to say, "this room is untidy, I'm going to build a new one." It's certainly more fun than tidying your room. But this is how you get sprawl and bloat.

Re:Ask HN: Working with a monolithic codebase by RivieraKid on Monday January 11, 2016 @01:13PM (#10882022)
Well, you can simply give up ownership rights on the code. If code was indeed a liablity, it would be profitable to transfer ownership to (for example) me.
Re:Ask HN: Working with a monolithic codebase by Someone on Monday January 11, 2016 @01:23PM (#10882096)
You can give away your castle with a license indicating that nobody can keep you out, too, but that doesn't guarantee that it will be maintained so that you can keep using it, either.