How fast are you supposed to write code?
Pages: 12
Hi, nice work,
making games for competition in a limited time frame would be too stressful for me, I prefer to light a cig and take a break while working, hopefully catching some insights :)
800 lines in 10h is close to 1 line per minute, sounds like a good average.
Since lines could be removed in addition to being written, I think both removed and written lines should count as "work", as long as one doesn't write lines only to remove them..
making games for competition in a limited time frame would be too stressful for me, I prefer to light a cig and take a break while working, hopefully catching some insights :)
800 lines in 10h is close to 1 line per minute, sounds like a good average.
Since lines could be removed in addition to being written, I think both removed and written lines should count as "work", as long as one doesn't write lines only to remove them..
As a former programmer and programming manager, I was never focused on lines of coded (LOC) written. Programmers were given an assignment to write a program that did x, add enhancement y, or fix a bug in program z. It was the programmer's responsibility to come back to the manager with an estimate of how long it would take to do x, y, or z. Programmers were generally measured against their estimates.
It was of course possible to game the estimate. One could say it would take twice as long as it should, but that's the managers job to know what are reasonable estimates for x, y and z. If an employee constantly finished an assignment in half his estimate, it would become clear quickly he was sandbagging his estimates. The bigger problem was employees that would take twice as long as their estimate.
Again as a manager, it would become clear rather quickly who did poor jobs of estimating.
On a personal note, I'm currently volunteering with a non-profit organization. What I'm working on is involving several new technologies that I'm not familiar with, so trying to estimate the time required for various tasks is quite challenging.
It was of course possible to game the estimate. One could say it would take twice as long as it should, but that's the managers job to know what are reasonable estimates for x, y and z. If an employee constantly finished an assignment in half his estimate, it would become clear quickly he was sandbagging his estimates. The bigger problem was employees that would take twice as long as their estimate.
Again as a manager, it would become clear rather quickly who did poor jobs of estimating.
On a personal note, I'm currently volunteering with a non-profit organization. What I'm working on is involving several new technologies that I'm not familiar with, so trying to estimate the time required for various tasks is quite challenging.
Thanks for all replies. Just for information, and because I am too curious, what is this non-profit organization @AbstractionAnon ?
| I don't wish to make it public. |
Not a problem. I understand your will to keep you garden secret. I do too ++
Last edited on
Topic archived. No new replies allowed.
Pages: 12