Jump in the discussion.

No email address required.

Another day, another git sneedpost.

I'm on the side that git's ux is balls.

Jump in the discussion.

No email address required.

I'm only stumped at people not having forced git to conform to a standardised naming convention, or even consistent behaviour that's easy to understand. If half the world fricks up at your tool it's stupid not genius. Trying to force everyone else to git gud at your bullshit memorise all your made up names and buy books to "learn" is a microsoft tier scam :marseynerd2:

Jump in the discussion.

No email address required.

:#marseysmug2:

Remembering the names for the concepts is not the obstacle preventing you from using Git effectively

Jump in the discussion.

No email address required.

Same as everyone else, the problem isn't how I use git but that the rest of the entire company doesn't 100% agree with my awesome flow strategy :marseyseethe:

Jump in the discussion.

No email address required.

H-hey @ThousandBestLives can you stop rebasing onto master and force pushing while I'm reviewing your work?

:#soyjaktalking:

Jump in the discussion.

No email address required.

git's ux is shit but the core model is not hard to grok and any software "engineer" that still doesn't understand it after a 1-2 hours of use should rope.

Jump in the discussion.

No email address required.

The JetBrains IDEs admittedly makes Git a lot more intuitive. Resolving a merge conflict in a JB IDE is 1000x easier than any other piece of software on the market to handle this

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.