> move glacially slow). Software productivity studies say a developer can
write around 10k lines of code a year (I tend to use 10k lines/year as
sustainable long term, 20k lines/year as approaching long term burnout, and
30k+ lines/year as very serious burnout territory only possible for short
periods),
I have heard about 20 SLOC/hour being the realistic developer’s productivity as
a long-term (months) average - in a short burnout period, the developer can
surely write more then 20 SLOC/hour.
Assuming 41 hours/week and 47 weeks per year with 1 month vacation (really it
is smaller then 47 due to national holidays) - and we will have much larger
estimation then 10.000 SLOC per year.
Dunno whether these are debugged SLOCs or just typed/buildable ones.
I’m not a big fan of these “trying-to-be-scientific” approach to project
management which start from SLOC measurement - the reasons is a) they do not
have any “science”-like approach to support, issues fixing and even debugging,
all “science” is about code typing only and b) they de-facto motivate the
team/company towards absolutely wrong goals like hitting the deadlines at the
cost of code quality - but the number of 20 SLOC/hour coming from this
“science” seems to be realistic.
So, about 2 weeks to write an 2000 lines-of-code rather-well-commented driver.
Dunno what MS’s people will respond to this.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com