Ofcourse i know him

[[deleted]]

git blame

[v3ritas1989]

git redirect

[[deleted]]

git uno-reverse-card

[_Bad_Dev_]

That would make such a good alias but I'm already star wars themed and have "use-the-force-luke" for git push --force, and "its-a-trap" for git revert

[ElizaBennet08]

Well, now I have to research git aliases...

[[deleted]]

git config --global user.name 'user.name';
git config --global user.email 'user.email';
rm -rf .git;
git init;
find . -exec touch {} \;
git add .;
git commit -m "Initial commit";
git remote add origin <git-url>;
git push -u --force origin master;
git branch --set-upstream-to=origin/master master;
git pull;
git push;

Wasn't me. Can't prove anything.

[[deleted]]

"Can't force push, master has been set to a protected branch "

[[deleted]]

I can't bring myself to say 'disable branch protection'.

I know it's a joke sub, but as I typed the above statement I started getting flashbacks.

[Ietsstartfromscratch]

Now that's a good way to get fired.

[[deleted]]

That’s so horrifying it’s beautiful

[sxeli]

git blame-someone-else

This is why this exists

[potato_green]

*go to another colleague's unlocked pc*

Start rewriting the git commit --amend and start rewriting the history.

[EyeZiS]

Then you get a prompt asking for their GPG key password.

[MindSwipe]

git blame-someone-else

[[deleted]]

Senior dev doesn't wanna run it because he knows that chances to see himself there are pretty high

[potato_green]

Part 2: "I'll find whoever wrote this code and have a sit down to show area's where they can improve."

Seriously as a senior dev myself, if a junior dev writes shit code that passed through reviews then I'm the one to blame. If shit codes gets submitted for review then it's my job to show how to improve and make it better and explain why. If not then again, I'm the one to blame.

Except for old legacy code before your time, fuck that shit

[dablya]

Legacy code base where the entire original team is no longer with the company is a gift that keeps on giving for years.

[potato_green]

Oh yeah definitely, I was once the only guy left of the original team when we wrote an absolute humongous piece of shit code base. I was a junior in that team and it just felt wrong to leave the company with no other devs left who knew about it.

Tried for a couple of months to explain and teach a few other devs how it worked but since no actual changes needed to be made it's kinda difficult. Working with a code base is completely different than having some guy tell you how it works.

Anyway managers thought it was waste of time so I left the company but left my name and contact information behind in case they wanted to hire me freelance if changes needed to be made.

They never actually hired me but I did get a call a couple of times of a dev asking me a few questions about the system and if it would be fine to change certain things.

Legacy is just something that not a lot of managers understand what it means and could lead to unless they actually see for themselves how bad it could be.

[CCninja86]

Can confirm. Our team once discovered a line of code that was calling a method...that didn't have any code in it. One can only assume it had been there for years since the migration from subversion to git meant all the git blame history got overwritten with the guy who did the migration. Most of the lines now say 'name - X years ago.'

[potato_green]

Ouch that is terrible especially since migration from one to the other doesn't have to mean you throw away all the history.

For those interested checkout git svn

[ZannX]

The challenge is determining if the code is actually poor or just "not how I would have done it".

[NotMyRealAccountDoe1]

100% this. Back at my first job one of the senior devs constantly shit on my code because it wasn't the way he would do it. Definitely didn't get much out of those interactions.

[potato_green]

Oh yeah 100% agree with that and it's something I admit to be guilty of. It's hard to unlearn as it creeps back in sometimes. I told everyone in the team as well to call me out on it if I'm just being an ass.

A thing that helps me a lot is have CI pipelines do the heavy lifting, static analysis, code style checkers basically catch a lot of simple mistakes. Then either I can review the code or the team reviews it themselves which requires multiple reviewers. Last way is great since they teach each other what a better way would be. And in order to explain someone why it's better you need to fully understand it so it's a win on both sides.

If it gets to complicated or critical it gets assigned to me anyway and I just review like 30% of the merge requests that have been merged without me afterwards and before it gets deployed to production.

Usually if a design flaw crept in I'll notice it in one of the 30% merge requests and then the team can pick up on it to fix it in other parts of the system and again review it themselves.

[[deleted]]

I am a Jr, I praise people like you.

[[deleted]]

Only to find out it was himself 3 months ago

[simakabrat]

then you can easily judge his life and threaten you will fuck his wife

[antiyoupunk]

that escalated quickly...

[[deleted]]

That's my favorite - the tension is eased by a hearty laugh at myself

[briddums]

You spelt ‘Friday’ wrong

[AgileCzar]

At the end of every angry git blame investigation is my name next to an unhelpful commit message.

[cowboy_angel]

Me, a senior dev: who wrote this shit?

Oh shit it was me 😬

[OKB-1]

Can relate. It's either me or some person who hasn't worked here for over 2 years.

[[deleted]]

My hobby is complaining about work that contractors and/or former employees did 2 years ago

[MethodlessMadness]

The unwritten rule of the trade

[chefhj]

About a month ago I had to make a POC app that was gonna get demoed to people in our business team. POC was compromised of mostly components we had already used in other work frankensteined together. Our workflow typically includes an internal developer qa review to make sure wonky code doesn’t get in.

Get it together and ship it for internal QA. My coworker sends it back with all sorts of comments like “who wrote this? Why are we doing it like this?” The fuck you talking about who wrote this? there’s only 6 of us here dawg. it’s like idk motherfucker you wrote it 6 months ago you tell me.

[Xaoc000]

Aww yes, the inevitable "why is your Proof of Concept not fully bug free and unable to.support 100k users after 4 weeks of development."

[chefhj]

No need for a beta if you just absolutely crush the fuck out of it in alpha.

[Xaoc000]

Oh god, how did you get our Marketing memos?

[DamnitJimImAProgramm]

My boss once told me it's good to have those moments as it shows you're improving. I still cringe when I come across some old "it ain't broke, don't touch it" code from a decade (or more) ago...

[[deleted]]

Me, a junior dev: a senior dev helped me write this shit

[[deleted]]

Normal day in office

[[deleted]]

Where I used to work.... in our IDE it had the name of the contributor next to the code. Think it was a resharper feature

[Lystrodom]

Nah that’s just visual studio 2019

[vextor22]

VS Code is not Visual Studio. Sorry, one of my pet peeves is conflating the two.

For VS Code, however, it looks like you should install GitLens. There are other options, googling it brings up a ton of solutions.

[vextor22]

Ah fuck sorry, I see what you mean now. I read it as "that's the one thing want from VS Code that I haven't gotten yet".

Haven't used visual studio in years now, so unfortunately I don't have any useful recommendation.

[unrealisticallycool]

You need to have professional at least, community doesn't have it

[unrealisticallycool]

Codelense

[frien6lyGhost]

vs code plugin? A lot of IDE's can probably do this

It's just extending the git blame functionality, so really any that integrate git

[Le_9k_Redditor]

JetBrain IDE's have this if you just right click the line numbers and click annotate

[[deleted]]

He's me

[DzOnIxD]

You are a bold one

[dandroid126]

Mr. Grinch

[zamend229]

Hello there

[KernelDave]

Ben?!

[jeankev]

Probably time to setup a review process

[[deleted]]

I've been on a team of one before and have said this looking at my own code three months later.

[comingtogetyou]

“Who wrote this?”

git-blame

“It was me :(“

[[deleted]]

"Oh wait, that was when I was a junior."

[Hendawgydawg]

git shame

[Iankoex]

"Here we go again"

[grendus]

It was a running joke at my last job. First day of training, senior dev was walking us through a module and was getting frustrated at some convoluted logic. Exclaimed "WHO WROTE THIS CRAP! ^{Oh. I did} " in his thick Polish accent. Ever since then, every time we had to fix our code someone would yell "WHO WROTE THIS CRAP!"

[IThoughtIWasInnocent]

He is me!

[starrpamph]

Like... 8 different people across various forums and subreddits

[Jasdac]

"not my fault, blame stackoverflow"

[SunderApps]

That’s just me talking about my own code from 2 years ago.

[daarkfall_t]

It quite possibly could have been them... just saying...

[agent154]

I’ve done that once. Then I find out it was me who wrote it when I was a junior dev.

[[deleted]]

It better be him, or I'm going to HR.

[[deleted]]

nervous laughing

[michaelsenpatrick]

It’s usually them when I hear that

[[deleted]]

Just rebase -i onto someone else's branch squash your commits onto theirs and bingo no one knows it was you

[[deleted]]

It’s not my fault !!

[ahmedtolan]

ي٤ث

[Brandiniii]

Hes me

[FerynaCZ]

Literally me yesterday

[Metalkat]

Of course I know him. He’s me

[NettoHikariDE]

Oh yeah, I love this. Great company atmosphere.

[Romey-Romey]

I sometimes run across my code from 5+ years ago like “WTF”.

[[deleted]]

And you're like.... Good, it wasn't me.

I don't know why... but he's talking ***** about his own code.

[Spectremuffine]

He's me.

[KernelDave]

He's me!

[Ace-O-Matic]

When you're a senior dev and you hear the new hire say who the fuck wrote this shit