by gamebit07 on 12/14/13, 10:41 AM with 4 comments
There are several tools as rescuetime, harvestapp etc. that tell you how much time you wasted/utilized doing what, but then if your code editor is open they say the time was productive.
Your code editor being the main window, is by no means a measure of the productivity. Couple of parameters that I have thought are -
1. No. of lines of code that you write.
2. No. of features that you have implemented.
3. No. of bugs that you have solved.
4. And the list can go on.
But each of the above are pretty subjective terms, and are not a good measure.
Just curious how people measure their software development efficiency.
Thanks for reading it.
by crazygringo on 12/18/13, 7:39 PM
Writing code, except for the most boring kind of boilerplate, is inherently a creative process, and neither "final functionality" or "final quality" have good metrics, let alone metrics that translate into man-hours, lines of code, or similar.
All you can really do is get a "feel" for someone who seems to be underperforming, performing at par, or is really a star player. It's just intuition. Which is really a terrible thing to have to base evaluation on, but it's really all we've got.
This is probably why group evaluations, like "planning poker" for estimates of task difficulty, and having the whole group evaluate each of its members (for promotions, raises, etc.), can be popular -- it's still all intuition, but a kind of "consensus" intuition performed by people who ought to know best, can be better than a single person's.
by greenlakejake on 12/26/13, 11:17 PM
-2000 Lines Of Code
http://www.folklore.org/StoryView.py?project=Macintosh&story...
by mherrmann on 12/14/13, 8:09 PM
by js7 on 12/27/13, 1:32 AM