Timeline for Standards for how developers work on their own workstations
Current License: CC BY-SA 2.5
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2011 at 19:16 | comment | added | user1249 | @Murph, then enforce a rule of "commit often - in a branch" and push to central at least daily. | |
| Jan 11, 2011 at 17:27 | comment | added | Murph | There's a logical inconsistency in there - "you don't know what your developer is doing" vs "you have to delegate" which means you know what he's doing but possibly not how - which in turn is why you need to get at the code... (yes, communication may help to sort this out but if you trust your devs to solve a problem and its a smallish problem - for a given dev - then "go fix this, bye!" may be as much management as is needed). | |
| Jan 11, 2011 at 17:19 | comment | added | user1249 | @Jon, in that case consider his unfinished work lost, assign it to another programmer, and then start pondering on why this happened in the first place. | |
| Jan 11, 2011 at 17:08 | comment | added | Jon Hopkins | I did specifically say in the question to assume that the person can't be contacted. | |
| Jan 11, 2011 at 17:06 | history | answered | user1249 | CC BY-SA 2.5 |