Hacker News Reader

We use SVN still. I'd like to switch to Git soon, given tooling like CI/CD is better/more available with Git, but apart from that it works.

That said, SVN works, and I do think the learning issue is the primary obstacle for us moving to Git.

It should be said we're a small team though, 10 devs. I can imagine Git looking a lot more attractive to a larger team.

View on HN

Almost a decade ago, I was part of a 10 person team (that was growing) and while there was consensus around transition to Git, it kept getting pushed back. I eventually forced the issue by changing the deployment job in Jenkins for one of the main projects to deploy from Git instead of SVN.

I had to give several talks to existing and new employees about how Git works and how to use it. I was also that #1597 guy (https://xkcd.com/1597/). Back then most hires didn't work with Git before joining us, today of course it's different. Over time, all projects moved to Git as whenever someone was working on two projects, one Git and one SVN, they would ask "why is this still on SVN?" and soon it would be on Git.

I worked for General Electric back between 2012-2014. My department brought a trainer in who worked for GitHub for a two day class on git.

Reply on news.ycombinator.com