 |
 |
|
|
| Source Safe | | (And Why Your Source Control Server Is Like The Bronx In 1985) | | 01 July 2008 | | Okay... okay... so we use Source Safe! We know - it is ugly, unreliable, and so old that it probably has a few Elvis "78"s in the loft. But what we have to say applies to ANY Source Code Control [SCC] system, so quit giggling and listen up!
Having been essentially the ONLY user of our main SCC system over the past few years, we've got things pretty-much the way we like them - stuff is organised in nice directory structures; and even within a project, stuff is divided into "Forms", "Controls", "Components" etc.
So when we noticed that a new colleague had allowed Visual Studio to "double-directory" his project (/MyProject /MyProject /Source Code) we were horrified; and asked him to fix it before hid did ANYTHING else.
Why? Are we obsessive compulsive? Authoritarian? Perhaps we just took more than we thought we did from our years in the army cadets!
No! But we do believe in Broken Windows Theory!
Your SCC control system, you see, is at the bottom of the tree - it is the one thing that all your developers share on an everyday basis - much more so than the code itself; and if it is a mess, than that attitude starts to permeate through everything else.
Then, before you know it you are living in a world where there are 500-character-long, single-line SQL statements embedded without comments in a Stored Procedure that contains "IF" statements with no indenting. And that, like the Bronx in 1985, is no place you want to be. |
|
|
The point is we are all connected... through love... through loneliness... through one lamentable lapse in judgment!
|
|
FairgroundTown.co.uk /
Reflectable Ltd
2010