News for hackers. Stuff that matters.
Re:The Carrying-Cost of Code: Taking Lean Seriously by sunir on Wednesday May 18, 2011 @09:25AM (#2560050)
One of my favorite interview questions for software developers is "how many lines of code have you deleted in one day?"

The question helps assess their maturity. It throws some people who think software is about adding continuously. Senior people know what I mean usually.

No code has no bugs. And no-code has no bugs.

Re:The Carrying-Cost of Code: Taking Lean Seriously by patrickyeon on Wednesday May 18, 2011 @10:16AM (#2560204)
It's a story we've probably all heard many times before, but I give you a story from the old Apple days: -2000 lines of code http://www.folklore.org/StoryView.py?story=Negative_2000_Lin...
Re:The Carrying-Cost of Code: Taking Lean Seriously by arethuza on Wednesday May 18, 2011 @10:26AM (#2560230)
People often talk about technical debt, but arguably what projects need is an entire balance sheet of assets and liabilities. I don't mean this literally, but just having the idea of debt doesn't quite sum up the possible state of a project in the same way that a balance sheet sums up the financial state of a company.
Re:The Carrying-Cost of Code: Taking Lean Seriously by thwarted on Wednesday May 18, 2011 @10:32AM (#2560253)
Technical debt can be roughly calculated from the number of open tickets that say something should be revisited and the number of times TODO and FIXME appear in the source code. Of course, if you don't ticket things that need to be revisited or write those comments, you have incalculable technical debt, which is even worse.