RCS??? Is it really that hard?
-
I had a meeting today, with some "software developers". I use that term loosely, because they probably don't classify themselves as software folks, but > 80% of their time is in software development and/or debug. As of today they don't use any sort of or very minor version control. I thought it was going to be a slam dunk in getting them to implement some sort of revision control tool, but they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
-
I had a meeting today, with some "software developers". I use that term loosely, because they probably don't classify themselves as software folks, but > 80% of their time is in software development and/or debug. As of today they don't use any sort of or very minor version control. I thought it was going to be a slam dunk in getting them to implement some sort of revision control tool, but they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
-
I had a meeting today, with some "software developers". I use that term loosely, because they probably don't classify themselves as software folks, but > 80% of their time is in software development and/or debug. As of today they don't use any sort of or very minor version control. I thought it was going to be a slam dunk in getting them to implement some sort of revision control tool, but they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
rbuchana wrote:
they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
I said the same thing when i first ran into it. It doesn't help that most of the client software sucks. Why would you want to periodically break your workflow unless you're getting something really huge in return? Of course, you are (or can be at least). Find out how they work, what problems they've had, how they coordinate changes. Then tell 'em a story that sounds real, describing how Source Control Will Save Them.
----
...the wind blows over it and it is gone, and its place remembers it no more...
-
rbuchana wrote:
they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
I said the same thing when i first ran into it. It doesn't help that most of the client software sucks. Why would you want to periodically break your workflow unless you're getting something really huge in return? Of course, you are (or can be at least). Find out how they work, what problems they've had, how they coordinate changes. Then tell 'em a story that sounds real, describing how Source Control Will Save Them.
----
...the wind blows over it and it is gone, and its place remembers it no more...
-
I think I did all that, but maybe not good enough. Oddly enough I recommended TortoiseSVN.
-
I had a meeting today, with some "software developers". I use that term loosely, because they probably don't classify themselves as software folks, but > 80% of their time is in software development and/or debug. As of today they don't use any sort of or very minor version control. I thought it was going to be a slam dunk in getting them to implement some sort of revision control tool, but they basically told me... Why would we need that? and We don't want the extra overhead of checking in and out. I'm really feeling dumbfounded.
So they're coders rather than software engineers. It's an uphill struggle.