|
swordfish wrote: VSS over a VPN
swordfish wrote: so we can get the original source and merge it with our local copy
cough, cough. Uhm, good luck with the merge. 
Incidentally, second in importance to Source Control is Backup/Recovery procedures. If you don't have those for development environments, you are asking to be put out of business.
Chris Meech
I am Canadian. [heard in a local bar]
When I want privacy, I'll close the bathroom door. [Stan Shannon]
BAD DAY FOR: Friendly competition, as Ford Motor Co. declared the employee parking lot at its truck plant in Dearborn, Mich., off limits to vehicles built by rival companies. Workers have to drive a Ford to work, or park across the street. [CNNMoney.com]
Nice sig! [Tim Deveaux on Matt Newman's sig with a quote from me]
|
|
|
|
|
I really can't imagine working without source control system even if I work alone, but it seems to be the second most popular answer here.
Two questions for people who don't use SC:
1. Why?
2. How?
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
On projects where I am the sole developer I don't see the need to use source control. The benefit is that you have access to previous versions of your code. Are there any other compelling reasons for using s/c for single-developer projects?
To me it's just an extra complication to set it up and maintain and then use. However I have been planning to put a few bigger projects onto s/c so that it can have other developers working on it and file versions. I'll get around to it at some stage..
|
|
|
|
|
Ashley van Gerven wrote: The benefit is that you have access to previous versions of your code. Are there any other compelling reasons for using s/c for single-developer projects?
Having the complete history of code changes is essential to successful maintenance. If something works in version n and not in version n+1, it takes just a diff between the versions to narrow down the problem.
Ashley van Gerven wrote: To me it's just an extra complication to set it up and maintain and then use.
Learning curve for simple SC systems like Subversion is very short, and the time spent is payed off very quickly.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
Nemanja Trifunovic wrote: Having the complete history of code changes is essential to successful maintenance. If something works in version n and not in version n+1, it takes just a diff between the versions to narrow down the problem.
This is the biggest reason why I use a cvs on all of my projects even the 100 line test app to evaluate a new algorithm ...
John
-- modified at 18:38 Tuesday 7th March, 2006
|
|
|
|
|
Ashley van Gerven wrote: On projects where I am the sole developer I don't see the need to use source control.
I use Subversion for all my projects, for Word Documents and WebPages too.
There is a lot of advantages using a source control system:
- You can Tag important milestones in your project.
- You can Backup All your projects and the history of them in one step.
- You can Branch your project.
- You can go back to see your changes.
- If you use TortoiseSvn you can setup a repository in two clicks
- ...
Regards
------------
Take a look to my Articles[^]
|
|
|
|
|
Source control is certainly the MOST important element of a safe development cycle (well, with the exception of sleep i suppose!)
Without source control you dont have any history of your changes and you can edit files randomly (destructively) without being aware...
There is also an audit trail to think about. And not just for multiple developers. If your used to submitting change lists to your sc server after every relevant change you make (ie, not just checking all your files out for a day and checking them back in at home time. Actually checking the same files in and out) then its extremely easy to add a remove 'features' that you made a 3am on a saturday since you know what time you did it.
Without SC you'd be forced to just hunt and hope... never a good idea really...
Ian
"He who only hopes is forced to spend his life in the dark"
|
|
|
|
|
It is scarily easy. Company I worked for before CP had zero source control. We simply never used it. 10 projects a month, developers all over the world, no source control. Sometimes updates were emailed to me so I could FTP it up to the live server. No staging, no test.
Now that I use source control, I don't know how I could have lived without it.
regards,
Paul Watson
Ireland
Feed Henry!
K(arl) wrote:
oh, and BTW, CHRISTIAN ISN'T A PARADOX, HE IS A TASMANIAN!
adapted from toxcct:
while (!enough)
sprintf 0 || 1
do
|
|
|
|
|
Paul Watson wrote: Sometimes updates were emailed to me so I could FTP it up to the live server. No staging, no test.
At one of my previous companies, I distinctly remember a day when I saw a senior lead directly edit a perl script (using vi) on our live server in a US hosting center through an ssh session. Funnily, I didn't think it was a bad thing to do, and actually even thought it pretty cool at that time.
Regards,
Nish
|
|
|
|
|
I have seen the same scenario at the company i work right now. When I joined in 2004 we did not have any source control setup.
But now it is much better as we have VSS installed on local area network to keep versions of code- A very helpful thing.
Thanks
Lav Pathak
Application Developer
Auxiliary Enterprises
Kalamazoo, MI
|
|
|
|
|
Nearly as cool as lumberjacks without safety equipment.
The ones without look much cooler, but the others are the ones who still have got all their toes / fingers / arms / legs.
All the label says is that this stuff contains chemicals "... known to the State of California to cause cancer in rats and low-income test subjects."
Roger Wright
http://www.codeproject.com/lounge.asp?select=965687&exp=5&fr=1#xx965687xx
|
|
|
|
|
now if you worked for a proper company you would have a helpline to do this for you, so that the developers would not have to be bothered with little things like this!
actually, thinking of it, it is always "interesting" (in a "oh my god" sort of way) to discover the scripts the helpline have written and installed on servers without telling the programmers, especially when the first we hear about it is something broke because a script has undone a required feature... 
zen is the art of being at one with the two'ness
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
