Timeline for KPI's for Programmers
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 19, 2013 at 0:36 | history | edited | gnat | CC BY-SA 3.0 |
quote from book that opens with the picture
|
| Jan 7, 2011 at 17:48 | comment | added | Jeremy | It's too bad that a lot of the time "going back" never happens. | |
| Jan 6, 2011 at 6:27 | comment | added | Homde | It's ok IMO to do ugly hacks to go quickly forward, on the condition that you continually go back and refactor them as appropriate, 3 steps forward, 1 step backward :) | |
| Jan 6, 2011 at 6:19 | comment | added | Bobby Tables | +1. We had a discussion along these lines at my work a couple of years ago: the more comments in the code along the lines of "this is a horrible hack that I have to do because of X", the more productive that developer is. It generally means that they're working on real stuff which integrates with other stuff and often forces them into not being able to do things nicely. Hmmm, it's a bit of a you-had-to-be-there now that I think of it. But basically if you had no frustrations that led to such comments in your code on that team, it meant you weren't doing much (or didn't recognise the badness). | |
| Jan 6, 2011 at 6:10 | history | answered | Homde | CC BY-SA 2.5 |