Alexey Zinger wrote:
At the risk of sounding like an aging hippie, which I am not, you can't put a measure on creativity that way, man, and software engineering is a largely creative endeavor, man. Even when we talk about support of existing software, one's job rarely involves doing the exact same thing twice -- you have to think, make decisions, and execute. Only the latter part can be measured in some number. How do you express the quality of an individual's or a team's thinking and decision making? I think there is only one way short of staying close to them and personally involved in what they do -- with objective results. Is their output selling? Is it causing problems down the road? Are customers happy? Etc.
I can't but agree. After all, are we paid for delivering working software or LoC? Productivity should be measured in function of gained money in the middle and long term.

--
Fabrizio Giudici - Java Architect, Project Manager
Tidalwave s.a.s. - "We make Java work. Everywhere."
java.net/blog/fabriziogiudici - www.tidalwave.it/people
[email protected]
--
You received this message because you are subscribed to the Google Groups "The Java 
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to