We're good. Thanks.
Tom Malia T <http://www.ttdsinc.com> &T Data Solutions L.L.C. _____ From: Stephen Connolly [mailto:[email protected]] Sent: Tuesday, June 29, 2010 10:17 AM To: Tom Malia Cc: Andy Levy; [email protected] Subject: Re: What would be the best way to create "working repositories"? On 29 June 2010 14:39, Tom Malia <[email protected]> wrote: Completely understood and agreed. As I said, I was setting the stage, not dictating the absolute. I understood and agreed with Stephen's core points. I didn't find the approach to communicating those points particular efficient. Only one comment was tongue-in-cheek and it even had a smiley All the rest were IMHO direct and too the point. Applogies if my brevity causes offence -Stephen My goal with the "over taxed" developers is explicitly to reduce that load. I am not necessarily "over taxed" and if necessary I'm looking for ways that I can take on as much of the burden of learning and possibly doing the processes necessary and only have to push as little as possible of that burden to the developers. Tom Malia T&T Data Solutions L.L.C. -----Original Message----- From: Andy Levy [mailto:[email protected]] Sent: Tuesday, June 29, 2010 9:24 AM To: Tom Malia Cc: Stephen Connolly; [email protected] Subject: Re: What would be the best way to create "working repositories"? On Tue, Jun 29, 2010 at 09:16, Tom Malia <[email protected]> wrote: > Stephen, > > > > I appreciate you taking the time to reply. I know many of your comments are > tongue-in-cheek and I don't take them too personally. However, I don't find > them terribly helpful either. I wont waste anymore bandwidth here on that > aspect of your reply. > > > > I have no idea what GIT is. If it's another product that I would have to > dedicate more resources to learning myself and training the already over > taxed developers then I don't think it's a great idea for my situation. A 5-second Google search will inform you as to what git is. Stephen makes a valid point, though - if you & your developers are so "overtaxed" that proper source control is too much to handle (this includes your developers not understanding Subversion beyond what you've described), then you have worse problems than the one you've asked for help with here. In the end, I think you'll find you spend more time, money & effort doing it wrong than you will in training & staffing appropriately to do it right. Or, to paraphrase a sign seen around my office: If don't have time to do it right, when will you have time to do it twice?
