Timeline for Standards for how developers work on their own workstations
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 11, 2011 at 16:08 | comment | added | David Thornley | @Dan Ray: One person's organized workspace is another person's mess. The developer might have no problems with managing the multiple copies; perhaps they're named something he can remember. Different people work in different ways, and forcing everybody to work the same risks lower morale and productivity in general to make it somewhat easier to cope with a rare contingency. | |
| Jan 11, 2011 at 15:04 | comment | added | Dan Ray | @Jon - The other thing is (and this isn't obviously a cure-all) but you could at least use gitx or whatever to at least get a quick view of what's IN the changes between the branches. Much easier than trying to manually diff multiple working directories. | |
| Jan 11, 2011 at 14:06 | comment | added | Dan Ray | @Jon - I guess that's true. Maybe there's just no recovering from somebody really committed to making a mess. | |
| Jan 11, 2011 at 13:44 | comment | added | Jon Hopkins | @Dan - But some of those branches are dead ends - proofs of concept, things with assorted debug code in that you don't want merged in, older versions. The fact you have merge functionality doesn't help when you don't know what you should be merging. | |
| Jan 11, 2011 at 13:38 | comment | added | Dan Ray | @Jon -- I guess the point is, his diverse branches would be in something that would have merging functionality built into it, rather than just scattered directories of diverging files. Plus, getting him up and going on the DVCS would have been a training opportunity. | |
| Jan 11, 2011 at 13:37 | comment | added | Murph | Don't assume its the tools - its also appreciation of how best to make use of the tools that can be lacking. What's obvious to some needs to be shown to others. The anti-pattern of lots copies of the source tree is one I've seen a few times. Yes, DVCS can help - but in this context we'd still have an issue with identifying the right branch and - if we want to go further - with making those Work In Progress branches available. @Jon the local DVCS should automagically push to that user's "backup" of their repository. At the very least if moves the problem off their box. | |
| Jan 11, 2011 at 13:34 | comment | added | Jon Hopkins | How would that help? The question would still exist, we'd just be talking about which branch within his local DVCS repository rather than which workspace. | |
| Jan 11, 2011 at 13:14 | history | answered | Dan Ray | CC BY-SA 2.5 |