I had to explain git merge to a senior level dev. It is 2025

Actually, there was a long time I only did it using github. I only knew command line branching and rebasing. Now i'm a ninja.

Edit: yeah, but these days senior dev positions are given to someone doing some nice tricks with a year of experience instead of a raise or something. Back in dem day, it required literally years. You could be the biggest ninja, but three to five years was the sweet spot.

To be fair, I have no clue how git cli works, either.
I‘m just not masochistic enough to do without git gui.

@Lensflare I had to explain how to diff between revisions, resolve conflicts and merge. Even the webapp makes that process pretty clear! I genuinely do not know how this person reached a senior level without understanding the basic concepts of version control

That's pretty horrifying. I don't understand how people never learn basic git commands. Are they forever in the .NET world? You're just using VCS as a glorified file sync at that point, not a careful documented tree of all your individual feature revisions.

@djsumdog You don't squash and merge? /jk

@djsumdog bullshit. What does this have to do with .Net?
Ever heard of dedicated git gui clients like Fork?
It‘s not dropbox like file sync.

He’s probably coming from non git based version control. But if he doesn’t know version control concepts that can be found everywhere then that’s a major issue

Yea, not sure about the DotNet slight, Visual Studio has fairly good (and getting better) git integration and no self respecting DotNet dev is using VSC's electron garbage over the real Visual Studio.

On the broader point, I don't think young devs understand how version control as standard practice simply wasn't a thing until relatively recently. Sure SVN and the like existed, but it wasn't at all the norm like it is today.

Your senior definitely should get comfortable with git basics, but it's not that surprising to find a few that don't yet have that skill set. My buddy has been out of the industry for the past seven or so years and he hadn't even heard of git when he recently got back into the field.

I die a little bit more every time I see a year mentioned as part of an argument.

@D-4got10-01 But what about >current year<

@BordedDev Yeah... An argument stating that 'why x? it's year yyyy' is no argument in my eyes.

@D-4got10-01 hmmm…

Why horse-drawn carriages? It’s year 2025.

😏

@Lensflare Because it's been outlawed as causing too much C02 ;P

Today, someone explained to me how I can create a pull request for my branch. 😛

Greetings from the tinkering project manager 😎

@djsumdog I never needed Git commands, SourceTree did everything for me.

Curious: Was this senior dev working solo?

In the cases I've seen where senior devs suck at git it has been where they've been solo so they rarely deal with merge conflicts.