@ame oh my fucking GOD
can i please ask you to alt-text this? this is fucking glorious, im fucking wheezing
@ShadowJonathan @ame I was being silly, could have just saved it twice.
#Alt4You (in images, because long).
Edit: I would also like to add that it seems highly likely this is either LLM-generated (author apparently behaves suspiciously, see comments on reddit) or a creative writing exercise (you would not leave comments like this in the code, COBOL comments donβt look like this, β¦).
But it is fun.
@crypticcelery @ShadowJonathan @ame I just assume everything is generated until proven otherwise.
While I have no idea what "fr fr no cap" and "bussin" means, and even if this is fake, I wish more devs were like this. Makes the job more entertaining.
My colleagues don't even use git. "It's too complicated" yeah it is, but it makes working together on one code base so much easier. Instead they just keep the code for themselves or send it to me on teams and I have to merge it manually π
Any decent manager would accept this over most other types of delinquency... At least it shows interest.
At my last job, when I arrived I realised that all the other devs had been using PyCharm to do got commits, and it had an option "use same commit message as previous commit"... There were literally hundreds of commits, years worth, with messages unrelated to their contents, sometimes 20 in a row touching completely different parts of the codebase.
A screenshot from Reddit sub r/csMajors:
2 hr. ago
hocobozos
My team's intern just found a critical bug by shitposting in our codebase
So our summer intern (who I'm 90% sure is a professional shitposter moonlighting as a dev) just saved our entire authentication service by being, well, an absolute agent of chaos.
Background: We have this legacy auth system that's been running since before Tik Tok existed. No one touches it. It's documented in ancient Sanskrit and COBOL comments. The last guy who understood it fully left to become a yoga instructor in Peru.
Enter our intern. First week, he asks why our commit messages are so boring. Starts adding memes to his. Whatever, right? Then he begins leaving comments in the codebase like:
// This function is older than me and probably pays taxes
// TODO: Ask if this while loop has health insurance
// Here lies Sarah's hopes and dreams (2019-2022), killed by this recursive call
The senior devs were split between horrified and amused. But here's where it gets good.
He's reading through the auth code (because "the commit messages here are too normal, sus") and adds this gem:
// yo why this token validation looking kinda thicc though
// fr fr no cap this base64 decode bussin
// wait... hold up... this ain't bussin at all
Turns out his Gen Z spider-sense wasn't just tingling for the memes. Man actually found a validation bypass that's been lurking in our code since Obama's first term. The kind of bug that makes security auditors wake up in cold sweats.
The best part? His Jira ticket title: "Auth be acting mad sus rn no cap frfr (Critical Security Issue)"
The worst part? We now have to explain to the CEO why "no cap frfr" appears in our Q3 security audit report.
The absolute kicker? Our senior security engineer's official code review comment: "bestie... you snapped with this find ngl"
I can't tell if this is the peak or rock bottom of our engineering culture. But I do know our intern's getting a return offer, if only because I need to see what he'll do to our GraphQL documentation.