![](https://programming.dev/pictrs/image/9de36669-449a-4be0-8e8f-8409552a6c64.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
When I stopped, subversion was what we used. I’m trying to understand Git, but it’s a giant conceptual leap.
It’s probably not ‘that much of a leap’ as you imagine. If you’re looking at Git tutorials, they’re usually covering all kinda complex scenarios of how to ‘properly use Git’. But a lot of people barely care about ‘properly using Git’ and they just kinda use it as a substitute for SVN… You create branches, you merge them back and forth, and that’s about it.
Like if you want to contribute to an open source project, all you have to do is create a fork (your own branch in SVN terms) - commit some stuff to it, and create a pull request (request to have your changes merged) back to the original branch. git pull
is just svn update
- getting someone elses commits
Not saying there aren’t more complex features in git, or that learning git properly isn’t worth it, just saying, I don’t think you have to see it as a ‘giant conceptual leap’ that’s preventing you from jumping back into programming. Easiest approach just to get started would be probably to just download a GUI like Sourcetree or Fork, and you just kinda pretend you’re still using SVN - approach wise
Do you have any measurements on how long it takes when you just ‘do it raw’? Like trying to do the same insert though SQL Server Management Studio or something?
Because to me it’s not really clear what’s slow. Like you’re complaining specifically about the Microsoft ODBC driver - but do you base that on anything? Can you insert faster from Linux or through other means?
Like if it’s just ‘always slow’ it might just be the SQL Server. If you can better pinpoint when it’s slow, and when it’s fast(er) that probably helps to tell how to speed it up