Reply to: Software Source Control Versioning

[SimonMac]

Lots of people who ended up doing dev work by accident, or in-house developers in places without any real software process.

And I've seen Bobs (from Tata) who made copies of the dir containing source code each time they changed stuff rather than use VC.

Bingo

[d000hg]

What developers in this day and age don't understand version control? Even Bobs use VC ffs.

Lots of people who ended up doing dev work by accident, or in-house developers in places without any real software process.

And I've seen Bobs (from Tata) who made copies of the dir containing source code each time they changed stuff rather than use VC.

[Cliphead]

Natives!

If they're that thick yer fcked.

HTH

[SimonMac]

What are we talking here?

Natives!

[suityou01]

These aren't even Bobs, so back to my original question before the bun fight over which technology is better than which (and you are all wrong, the best is StatTeam) does anyone know of any literature that can help me show them how versioning should work etc?

What are we talking here?

[SimonMac]

What developers in this day and age don't understand version control? Even Bobs use VC ffs.

These aren't even Bobs, so back to my original question before the bun fight over which technology is better than which (and you are all wrong, the best is StatTeam) does anyone know of any literature that can help me show them how versioning should work etc?

[suityou01]

How is git clone or git commit or git push or git pull..hard? Maybe I am over estimating the intelligence of some of you, I had some of you pegged slightly above moron but looks like I was being optimistic.

It's only me and SAS. The rest are cretins

[russell]

SVN is fast, reliable, easy to setup, etc as well. It's also very easy to use.

You shouldn't feel like you've accomplished something when you manage to commit your code... it's a key principle of software tools that the harder they are to use, the more people won't bother.


And no you don't need to build it yourself whoever complained about that... getting Git on my Windows PC was quite straightforward and it works fine, it's just understanding how to use it that is a PITA. We use the github flow which is about as simple as it gets and still SVN is much easier.

DVCS are very cool at merging but I would rather have SVN that can do the merging properly in the first place.

How is git clone or git commit or git push or git pull..hard? Maybe I am over estimating the intelligence of some of you, I had some of you pegged slightly above moron but looks like I was being optimistic.

[suityou01]

After a bit of help from our learned developers, does anyone have any resources that show's the benefits of source code version labeling, either power point presentation or white papers etc?!

I am trying to work with a load of developers that don't quite understand the concept, and I am hoping pretty pictures and small words might make it easier for them to understand.

What developers in this day and age don't understand version control? Even Bobs use VC ffs.

[d000hg]

Nope it's fast, extremely reliable, distributed, easy to setup, low footprint and generally awesome.

SVN is fast, reliable, easy to setup, etc as well. It's also very easy to use.

You shouldn't feel like you've accomplished something when you manage to commit your code... it's a key principle of software tools that the harder they are to use, the more people won't bother.


And no you don't need to build it yourself whoever complained about that... getting Git on my Windows PC was quite straightforward and it works fine, it's just understanding how to use it that is a PITA. We use the github flow which is about as simple as it gets and still SVN is much easier.

DVCS are very cool at merging but I would rather have SVN that can do the merging properly in the first place.

[russell]

I set it up to play with. It's one of those open-source projects that you have to build before you can use it. So first download the code, then spend half an hour reading the instructions on how to build. Then spend another hour trying to find somewhere to download the build system it's using. Then spend another hour trying to work out how to build that...

******* clueless, you can install git using apt, yum there are installer for osx, windows.

[VectraMan]

Nope it's fast, extremely reliable, distributed, easy to setup, low footprint and generally awesome.

I set it up to play with. It's one of those open-source projects that you have to build before you can use it. So first download the code, then spend half an hour reading the instructions on how to build. Then spend another hour trying to find somewhere to download the build system it's using. Then spend another hour trying to work out how to build that...

[russell]

A bit like your wife.

[minestrone]

Nope it's fast, extremely reliable, distributed, easy to setup, low footprint and generally awesome.

A bit like your wife.

[russell]

I agree.
I tried git and it was too complex for me, I need little pictures to click cause I am thick

FTFY