Productivity in programming of C++ programmers

[N4M]

Dear,
May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day, what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?
Thanks for your guidance.
NguyenMai

P/S: Similar post has been sent to comp.lang.c++.m oderated (probably
takes longer time)

[Phlip]

N4M wrote:

May I ask how productivity of a(C++) programmer can be measured?
Do you want to rate individuals, or improve user productivity early and
often?

If the former, either run tests, or ask team members to vote on who, besides
themselves, helps the team the most.
If it is measured by number of code lines per day,
A line of code is _spent_, not gained.

To measure a team's productivity, every Monday select a few features of
highest business value. Spend the week implementing them, while writing unit
tests. Don't allow any code that does not support the current and new
features to remain in the codebase. Do not count lines, or reward based on
any ramp in line count. It should curve over (y^2 = x), not up.

On Friday, count the number of features implemented, burn a new version of
the program onto a CD, and pretend to deliver it.

Because this code is bug-free, and contains high-priority features, your
business managers have the option to deploy it to users. Whether they do or
not, the version should demonstrate the ability to boost user productivity.

The team's "velocity" is their number of features per week. Improve this
number by programming in small groups, not alone in individual offices, by
continuously integrating, and by passing all the tests between the fewest
possible edits, say 10 at the most.
what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?

Tests have shown an order of magnitude improvement between intermediate and
guru level. Credit those authors with the experience to rarely get stuck,
but Bjarne shouldn't be revered if he didn't invent a language that others
could benefit from.

The best way to keep a team fast is to allow its gurus' influences to spread
rapidly. Keeping them alone and watching them shred is irrelevant to team
progress. And some folks are faster in some domains than others.

--
Phlip
http://industrialxp.org/community/bi...UserInterfaces

[Peter van Merkerk]

N4M wrote:

Dear,
May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day, what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?

Lines of code is the worst metric to measure a programmers productivity.
It stimulates wrong behavior; you don't want programmers to maximize the
number of lines of code to accomplish a certain task.

--
Peter van Merkerk
peter.van.merke rk(at)dse.nl

[Phlip]

Peter van Merkerk wrote:

Lines of code is the worst metric to measure a programmers productivity.
It stimulates wrong behavior; you don't want programmers to maximize the
number of lines of code to accomplish a certain task.

One Peter Merel put it like this; "If you reward by lines of code,
programmers will automate code generation..."

--
Phlip
http://industrialxp.org/community/bi...UserInterfaces

[osmium]

N4M <dn******@yahoo .com> wrote in message
news:6e******** *************** ***@posting.goo gle.com...

Dear,
May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day, what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?
Thanks for your guidance.

I don't like wading around in philosophical swamps, but anyway ....

Note that the desired end result of programming is performing some function
thought to be useful, not lines of code. The better programmers may produce
less lines of code for the same end result. And the smallest program of all
may be the "worst" since it may be unmaintainable by ordinary mortals. And
on and on ...

So you have chosen a bad metric. And furthermore, some things can't be
measured, which does not diminish the *desire* to measure. I am fascinated
by what makes a woman beautiful, unfortunately I think I will go to the
grave no smarter on that issue than I am right now.

I can think of two ways to quantify, more or less, this issue. The opinion
of peers, or some kind of contest. Example:

Write an equivalent to Pretty Good Privacy. But some of the entrants will
have more prior knowledge than others, so several contests would ne needed.

[Gernot Frisch]

> May I ask how productivity of a(C++) programmer can be measured?

Assume a time it might take for a certain task, then set a deadline at
half of that time. You will have to give time to finish the problem
(that's the other half of the esimated time).
Then pay your programmer for the time worked, or pay per project (and
you will get buggy crap)

Honestly, I don't think there's any way of measuring our work. You can
only trust or don't. And if you think someeone's too slow (in
comparison to others in your office) ask him/her about it.

-Gernot

[Thomas Matthews]

N4M wrote:

Dear,
May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day, what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?
Thanks for your guidance.
NguyenMai

P/S: Similar post has been sent to comp.lang.c++.m oderated (probably
takes longer time)

Productivity must be measured along with other attributes.

I could crank out lousy code all day and be productive.

I could spend a day optimizing the code for speed or space when
optimization is not necessary.

I could spend a day reviewing other people's code. Yet I have
no quantitative or tanglible data for a metric. I know I've
helped in the overall productivity, but alas, it isn't measured
until the end.

I could spend my time writing quality code, yet not be very
"productive ". I can spend my time writing robust code without
generating any data for the metrics.

Somethings in programming are more important than being
measurably productive.

--
Thomas Matthews
Software Rebel.

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.l earn.c-c++ faq:
http://www.comeaucomputing.com/learn/faq/
Other sites:
http://www.josuttis.com -- C++ STL Library book

[Gary Labowitz]

"Thomas Matthews" <Th************ *************** *@sbcglobal.net > wrote in
message news:kG******** *******@newssvr 16.news.prodigy .com...

N4M wrote:

Dear,
May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day, what are the
estimated productivity of a programmer at beginer, intermediate (Me),
advance, master, guru,and sifu (B.Stroustrup, H.Sutter, S. Meyer)?
Thanks for your guidance.
NguyenMai

<<snip>> Somethings in programming are more important than being
measurably productive.

Yes. At IBM, many years ago, there was an attempt to measure programming.
They counted lines of code, percentage of comments, hours spent on
compilation, overtime put in, etc. Nothing made any sense. [When they
measured comments, claiming a good program would have 75%, there were
statements like
"LR reg7,reg9 load register 9 into register 7"]
The result? No answer. However, our team had exactly one bug reported in the
first year our code was release in the wild. Some groups had hundreds and
hundreds. Who was more productive? [I might add we delivered one week early,
which was the only time it ever happened!]

End result: the guys that were on good personal terms with their managers
got awards and raises. I think final salary is the measurement you are
looking for.
--
Gary

[Steven T. Hatton]

Thomas Matthews wrote:

Productivity must be measured along with other attributes.

I could crank out lousy code all day and be productive.

I could spend a day optimizing the code for speed or space when
optimization is not necessary.

I could spend a day reviewing other people's code. Yet I have
no quantitative or tanglible data for a metric. I know I've
helped in the overall productivity, but alas, it isn't measured
until the end.

I could spend my time writing quality code, yet not be very
"productive ". I can spend my time writing robust code without
generating any data for the metrics.

Somethings in programming are more important than being
measurably productive.

I've discovered that more often than not, my third attempt at the same
problem results in far less code than the first. IOW, the better my code
gets, the less of it there is.
--
STH
Hatton's Law: "There is only One inviolable Law"
KDevelop: http://www.kdevelop.org SuSE: http://www.suse.com
Mozilla: http://www.mozilla.org

[Pete Becker]

N4M wrote:

May I ask how productivity of a(C++) programmer can be measured?
If it is measured by number of code lines per day,

By that measure, my productivity is often negative. I consider those to
be very good days.

--

Pete Becker
Dinkumware, Ltd. (http://www.dinkumware.com)