Someone put an unrelated "lol" inside your comment.
Wollen Sie ganz einfach Ihre eigene Homepage erstellen, ohne HTML-Kenntnisse, einfach, professionell und mit viel Freude? Probieren Sie unser Desktop Content Management System (CMS) Zeta Producer für Windows aus. Komplett mit eigenem Shop, Gästebuch, Weblog, Bildergalerien, Integration von YouTube-Videos. Wir haben eine aktive Anwender-Community, schnellen Support, sympathische Support-Mitarbeiter.
Even on personal projects where I'm the only developer I use source control. In this day-and-age I wouldn't ever consider doing anything without source control other than a very quick throw away thing.
Why shocked? You have to learn this lesson somewhere. Some learn the lesson by hitting the wall, some may not hit any wall since they live on their own universe that has no walls. Just kidding
Instead of being shocked: it's more interesting *why* they did not have the need for it in a *professional environment* (or why they think the have no need for it).
Why shocked? Because I thought this was a done deal (sort of thing). It is an argument that was made years (decades?) ago and the everybody agreed that source control was the way to go. I've been using source control since the mid-90s and these days I thought the only question remaining was "which one?"
It is interesting to turn the question on its head. And perhaps if it was a start-up that hired fresh faces graduates with no real world experience then I'd understand.
I'm used to version control system since the late-80s and it's no question that this is a must for productive software development.
But why for software development only?
What about other documents and files? All your MS Word (or you name the tools) documents, project plans, backlogs, invoices, reports, ...
There is no good reason *not* to have them in some kind of version control system... I wonder how many manage them in some kind of version control system.
I am one of those not using source control. But that doesn't mean I don't do any source control.
When I work on a project I am used to make at least 1 backup a day (there are days with several backups). The name of the backup is like:
Just in case: I am more PLC-Oriented, so we are limited in using 3rd party tools. But when I use VS I almos do the same.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
Apparently, many in the team found the Git/GitHub learning curve to be too difficult so we moved to TFS. It takes ages to do things, the Visual Studio integration crashes VS, and if there are network issues then it becomes very difficult to do any work.
Political, mostly. People didn't like it or were not willing to learn it, even with GitHub for Windows which hand holds you through most things that you'd want.
Also, I'm told that the CVs we were getting in for developers overwhelmingly had TFS experience and very little Git/GitHub (which at the moment is the most common source control according to this poll) and we are desperate to attract good developers, so anything to make the transition easier...