OK @QuanticoCEO
Nobody should be allowed anywhere near a Git client until they have read this book.

They shouldn't be allowed to touch anything to do with git before reading and understanding git, let alone getting near a GUI.

https://git-scm.com/book/en/v2

@C0D4 What if I'm not an Asian woman? Will I still be able to read it?

@Jilano maybe, you might have to work at it.

If you have to read a fucking book on a GUI client, then the GUI is utter shit. Or the underlying tech is so shitty that the GUI can't really work well. It's a step back into the 1980s.

Reading a book for a trivial helper task like version control because Git is a fucked up piece of shit, that is.

@Fast-Nop got as a gui isn't hard, git as a tool is simple, git as a concept is a pain in the ass to get your head around.

Having buttons in a gui is one thing, knowing what those buttons are going to do to make you life miserable later is another.

@C0D4 Git is bad software. That's why we have Github, a fucking centralised hoster just so that people don't have to deal with the crap underneath. That's how bad it is.

If you have to get your head around simple shit like version control, the concept is already wrong.

"the only method that works" - pure marketing strategy

git may not be intuitive and straightforward but people get their job done though they screwup when they have actually thought they understood it

@Fast-Nop hosting a service and using a tool are quite different things

@electrineer Github is more, MUCH more than hosting. It's selling point was to abstract the shitty base away.

@Fast-Nop still, GitLab/hub is just a wrapper to an over complicated problem - I'm not defending it here, it's a bitch some days.

Git being open source means there's a long list of ways to do any single task in stead of just being "do this".

Working with git from a gui requires a fundamental understanding of the tool, regardless if it's a a desktop app or a cloud service.

@C0D4 And that's what's wrong with Git: it's a feature-centred design, and the workflow was an afterthought. That's how you design infrastructure SW, but not SW for interactive use. It's putting the cart before the horse.

Oh I’m gonna have to add this book to my list. I have not seen this book yet! Thank you!

@Fast-Nop I agree. But Working with people of different experience levels and disciplines like ee.
They get the IDEA of version control but they miss it entirely in practice. Makeing git usage as a group even worse. So there should be a version control book before this lol.
I’m talking crazy shut like work on a file change the name to whatever date or version submit.. then the next day work on something copy the file into a folder with that date / version and make changes to the new file? And repeat the process and submit all of it ... I’ve delt with those people still today even.

As a company we were using SVN which is a whole other story.. we moved to HelixCore.. I really like that more than gut but it’s not cheap.

@QuanticoCEO I like SVN (using that in my company) because it's dead simple. I can even use it after MONTHS of not having used it. No weird shit.

OK, it's centralised and thus unsuited for some thousand devs world wide like in the Linux kernel, but most projects don't even have that problem so that Git is just an error-prone overkill and productivity waste. Also, the SVN server repo is under central IT backup, the clients aren't.

@Fast-Nop I agree with you! Lol I don’t use git even on personal stuff.

We were using SVN when I started .., but the idiot did not have a SVN server.. did not use SVN like SVN.. he more or less had everyone using SVN as glorified half baked NAS.. but the NAS was inside our already used NAS.. no branching no nothing.

I choose helix code because it provided the structure to prevent stupid shit. As well as work flows to follow. Built in review process. And it works epically fast even on binaries .. idk it’s like 10 times as fast as our old SVN.. but then again SVN didn’t have its own server here.. was just a folder on a NAS

Git got popular because it was used on the Linux kernel, and everyone started talking about it. It's a typical Linus thing - does the job, gives a lot of control, and has no problems holding its middle finger up to you if you screw up.

I use it because everyone else uses it, everyone knows it to an extent, and no-one wants to be "that guy" that doesn't use it. In truth though I've always preferred mercurial - afaik all the same functionality as git, but with a way saner interface, and you have to *really* try to shoot yourself in the foot.