Steve Balmer on KLOCs
Ali Gajani0 HN recommenders · 2016–2026
11K views · commentary · evergreen · Uploaded 2014-11-27
A one-minute clip of Steve Ballmer explaining IBM's obsession with counting thousands of lines of code (KLOCs) as a measure of programmers. He explains why that metric is useless.
Linked whenever lines of code or developer productivity metrics are debated.
1:00:43Jim Simons (full length interview) - Numberphile
Numberphile2
14:34Steve Jobs Stanford Commencement Speech 2005
JoshuaG
1:03:55🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
32:56Bret Victor The Future of Programming
Joey Reid
1:07:26Alan Kay - Normal Considered Harmful
powerfuloutlet
53:31Growing a Language, by Guy Steele
Bill Pugh
1:01:40A Philosophy of Software Design | John Ousterhout | Talks at Google
Talks at Google
1:18:21"Uncle" Bob Martin - "The Future of Programming"
Paul Stringer's Mobile Tech
5 comments from Hacker News
> he didn't feel like they wrote enough lines of code. Say what you want about Steve Balmer but he had the right attitude towards that [VIDEO] As to the rest, I get the feeling that a lot of players in the market that now need software have the exact same tales being told about them. It is going to be a wonderment to me if I will be about to get through a day in 10 years without a IoT failure.
Steve Ballmer on "KLOCs" [1]. Not saying you're taking that extreme but LOC value is certainly debatable... [1]: [VIDEO]
Triumph of the Nerds: The Rise of Accidental Empires is his and is pretty good. I must admit that the part with Steve Balmer talking about KLOCs is funny and true [VIDEO]
Former Microsoft CEO Steve Ballmer on useless performance metrics[1][2]: >> In IBM there's a religion in software that says you have to count K-LOCs, and a K-LOC is a thousand line of code. How big a project is it? Oh, it's sort of a 10K-LOC project. This is a 20K-LOCer. And this is 5OK-LOCs. And IBM wanted to sort of make it the religion about how we got paid. How much money we made off OS 2, how much they did. How many K-LOCs did you do? And we kept trying to convince them - hey, if we have - a developer's got a good idea and he can get something done in 4K-LOCs instead of 20K-LOCs, should we make less money? Because he's made something smaller and faster, less KLOC. K-LOCs, K-LOCs, that's the methodology. Ugh anyway, that always makes my back just crinkle up at the thought of the whole thing. [1] [LINK] [2] [VIDEO]
If so, it hasn't always been that way. Steve Ballmer on IBM and KLoC's: [VIDEO] (I think it is from "Triumph of the Nerds" (1996), but I can't find the time code)