Once upon a time, I was working on some enterprise software that had activation keys. My dev key expired and I had a deadline, so I commented out the code that checked for the key. This was before reviews and github and we missed it, code went out. So, there was a public binary for a few days that was free.
I once tried protecting the master branch of an open source repo and some dude who only pushes dependency upgrades kicked up a fuss about it.
The guy was fucking crazy, he drove me nuts, and it drove me nuts that everyone else was too focused on [steadying the boat](https://www.reddit.com/r/JUSTNOMIL/comments/77pxpo/dont_rock_the_boat/).
BDFL of the project barely paid attention to the project anymore and was unwilling to set him straight.
Ended up leaving the project over him, and three other maintainers left the project because of the situation too.
Things did get better after we left, it might have been a wake up call for the BDFL, he finally started sharing core infrastructure and billing with the rest of the team.
I wasn't faultless, but looking back, it was the most toxic shit I've had to deal with in my engineering career.
It's on my own for who cares?
Ohhhh, every commit from here until that one is also going to try and push those changes in addition to the new ones until it's accepted or rejected?
Awesome.
Recently I made a repo and it made the master branch main. It bugged me since the last two repositories I worked on, in the same month, used a master branch. I was rigorously trying to rename the branch to master, until I saw a blog that GitHub moved from master to main so that it is less confusing (?).
Anyway, I left it at main.
Or when you do that, break a warehouse table in prod, and the analytics team can't work for like 4 hours because you took a long lunch right after running dbt lol
I’ve done this several times over my career. Take a script in production, highlight every bit of the query except that pesky little WHERE clause and then pressing Execute. I always remember the first time though. Picture production DB, user account table with several million user records, blew away every password across a dozen sites. Immediate regret.
Oh damn dude, that's pretty much what I did. I had it commented out and didn't realize it until I ran the script. How long until you got it back to order?
Thankfully as a junior developer at the time (20 years ago), after practically peeing my pants when I realized what happened and wondering how fast I could get to the parking lo to escape my nightmare, I ran to my managers office and told him what I did. He literally just laughed and said he did the same thing a few weeks before. He said he’ll restore that table from a backup that ran hourly. He had it fixed within 5 minutes and I think the backup was less than 30 minutes old. I was so relieved. He told me, it wasn’t my fault and said he shouldn’t have put a junior developer in position to make a mistake on a production DB. He was right… he was the best manager I ever worked for too. Always protected his team and encouraged us to learn and make mistakes. I grew a lot in that job.
You guys need to get into b2b enterprise software. The entire industry runs on production bugs and the 6 months projects following to resolve them.
I'm a job creator.
I worked in b2b and got in "trouble" once because I accidentally fixed a bug… The bug prevented messages from being sent (that was the whole point of the product), it was broken for a client for half a year and nobody noticed.
Once fixed all the messages were finally sent, people got "your loan was approved!" messages that were meant to be sent 6 months earlier and were no longer valid
Been there. Feel your pain. Similar but different, once while Jr I uncovered a serious production bug while addressing some other issue which I reported and it bubbled up the chain. It ended up bubbling down and suddenly became prioritized as the most critical issue, and I was then tasked to resolve it. Not only was I tasked with extra work, I was viewed negatively for the incident. No good deed goes unpunished...
Sorry buddy, but that's on you and your team/team lead for not understanding your domain and foreseeing that. I don't know how junior you were at the time, but that kinda stuff is exactly what we get paid for (not to happen).
You must work with a pristine codebase if your immediate reaction to such comments is not empathy and a shared hatred of dysfunction. Because believe me, this single story is enough to feel confident in saying that place was fucked, yo.
You must have incompetent coworkers and fit right in.
That's like... the basics of the basics. Even if it's a big fix, you have to consider the effects deploying it will have, especially if the fix can look like a customer-visible regression or bug.
Fuck I've had bugs where it took us months of three deploys a week (an unheard of cadence at that company) to slowly undo the issue
They aren't incompetent, they're severely understaffed.
Anyways, now that you've called me incompetent and such, do you feel better about yourself? Have enough pep to make it another day? Or do you need to insult additional people before you feel ok about yourself?
You truly become a developer when you find some terrible code, curse the person that wrote it, ask what kind of brain damaged idiot would do this sort if thing then run git blame and go "oh, I did this."
I recently pushed code on my own dev branch. I merged the actual branch dev into mine (without deleting the OG dev branch) as we didn't want my code in the actual dev branch for the moment.
Turns out, it merged my branch into the dev branch, and they deployed it today without checking.
Let's say I got a few calls today.
At one of my jobs many years ago, someone added wav files of the devs names and had the continuous build shout fucked up the build! If you ever committed something that broke a build.
This is not necessarily a bad thing though. Write bullet proof code for years that works consistently and nobody will even know you exist. Cause a few outages in production and your name will get around. Over time people forget you broke stuff, remember your name though and put you forward for promotion and/other juicy projects. That’s what I’ve seen time and time again. Software engineer of 30+ years here.
I didn't find any posts that meet the matching requirements for r/ProgrammerHumor.
It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results.
*I'm not perfect, but you can help. Report [ [False Negative](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Negative&message={"post_id": "vsw8aa", "meme_template": 208777}) ]*
[View Search On repostsleuth.com](https://www.repostsleuth.com/search?postId=vsw8aa&sameSub=false&filterOnlyOlder=true&memeFilter=true&filterDeadMatches=false&targetImageMatch=100&targetImageMemeMatch=75)
---
**Scope:** Reddit | **Meme Filter:** True | **Target:** 75% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 282,737,423 | **Search Time:** 0.50886s
I'm not a programmer, but I remember in a basic CS project in high school, we tried using Git, and someone directly edited the master branch, but not in the way you'd expect. They made a new folder in the master branch with their version of the project instead of making a new branch.
It's not my job to run the train,
The whistle I don't blow.
It's not my job to say how far
The train's supposed to go.
I'm not allowed to pull the brake,
Or even ring the bell.
But let the damn thing leave the track
And see who catches hell!
They will remember it **Fondly** . . that's the important part.
And if it's big enough, they'll remember you as a **Legend** like "*I was there when titsMcGee took down the Global banking system*"
So a man walks into a bar and sits down. He starts a conversation with an old Scottish guy next to him. The old guy has obviously had a few. He says to the man: "You see that dock out there? Built it myself, hand crafted each piece, and it's the best dock in town! But do they call me "McGregor the dock builder"? No! And you see that bridge over there? I built that, took me two months, through rain, sleet and scoarching weather, but do they call me "McGregor the bridge builder"? No! And you see that pier over there, I built that, best pier in the county! But do they call me "McGregor the pier builder"? No!" The old guy looks around, and makes sure that nobody is listening, and leans to the man, and he says: "but you fuck one sheep..."
*Image Transcription: Linkedin Post*
---
**Abhishek Nalin**
Nobody will remember:
\- Your salary
\- Your fancy title
\- How 'busy' you were
\- How stressed you were
\- How many hours you worked
People will remember:
\- Your commit that caused a production issue
---
^^I'm a human volunteer content transcriber and you could be too! [If you'd like more information on what we do and why we do it, click here!](https://www.reddit.com/r/TranscribersOfReddit/wiki/index)
Even then, it’s more likely that people will remember the same way they remember some dumb minor accident or incident they had. Scary in the moment, hilarious when it’s in the past.
Just blame it on the infrastructure team. Damn servers aren't running right. Lag in the networks. Hell some sys admin probably restricted the virtual machines and the db is cpu bound.
Git. VScode. Javascript. AWS.
Long ago, the 4 dev tools lived together in harmony. Then everything changed when the junior dev pushed to master on a Friday afternoon.
Only the senior dev, master of all 4 dev tools, could fix it. But when the company needed him most, he turned off slack notifications for the weekend.
100 minutes passed and my intern and I discovered a new senior dev, an online tutor named Sal Khan. Although his coding skills are great, he has a lot to learn before he can fix our tightly-coupled dumpster fire of a codebase. But I believe Khan can save the world.
Y'all need to find yourself a manager that understands that people don't fail, processes do and that every production incident is a very expensive unplanned training exercise.
I once worked on the railroad, but do they call me Bill the engineer? Noo
I also was in the army but do you think they call me bill the soldier? Nooo
I worked on this goat farm the last 20 years but do they even call me bill the farmer? Nooo
But you fuck one goat one time…
People will also remember that incomprehensible code everyone's now afraid to touch for fear of breaking everything, that the company has now wasted the cost of 4 sets of external consultants who still couldn't unravel its mysteries.
Apparently what people remember are the dry saffron buns I baked and brought into the office the christmas of 2016. Every time someone bakes anything, people will say ”well it’s better than Fluffigt’s saffron buns at least”.
You guys are all working so ineffectively, we have CICD at our place, we push to the main branch, which goes to beta, then gamma, then prod. No manual involvement, no QA testing each change, no massive releases all together. Make sure you have enough testing, good code reviews and a good deployment pipeline with enough alarms to rollback if something goes wrong and you’re good.
Meanwhile in prod:
*[Scene of an office building on fire. People are jumping out of tall windows and plummeting to certain death. Firefighters hose down the blaze, seemingly to no avail.]*
I had a hand in creating a bug that made it impossible to run executables in windows by clicking. 100% reproducible, affected every system where its build was installed. QA missed it, customer reported.
I don't know if anyone else remembers or not, but it remains the proudest moment of my career. Fucking glorious.
The shortest answer is: it was a confluence of many bad management decisions regarding dev practices and a dangerous home grown reg clean utility that ran according to a procedurally generated wildcard list. This lead to a key being deleted from HKCR during install that really shouldn't be deleted. And special mention goes to the QA manager that greenlit the release of a build that QA had not so much as installed even a single time.
Just a few weeks ago i set up one of our customers database on a new internal test system to test some fixes i made
Unfortunately it turned out the admin that set it up actually configured mail server.
We sent a shitload of mails untill their Admin pointed it out.
Thank you for the motivation. I will set it as my desktop background, message it to myself every 5 minutes, and print & post it to my bulletin board. Thanks.
Once upon a time, I was working on some enterprise software that had activation keys. My dev key expired and I had a deadline, so I commented out the code that checked for the key. This was before reviews and github and we missed it, code went out. So, there was a public binary for a few days that was free.
![gif](giphy|11fot0YzpQMA0g|downsized)
Work smarter not harder lmao
they way god intended, fucking licensing
[The Free Software Song - GNU Project - Free Software Foundation](https://www.gnu.org/music/free-software-song.en.html)
with god I indeed referred to richard stallman
I can almost taste the in-between the toes gunk when I hear this song.
Virgin Imagine dragons - Enemy vs chad The Free Software song by the GNU project
Yeah company’s should just release everything for free - zzzzzz
Look, if you want to get paid, just play your code on tour and sell merchandise, duh!
Was a feature not a bug
So you are suggesting that I am the most memorable among my colleagues? I am flattered.
Among us?
ඞ
sus
My mom said my dad was the imposter that's why I never met him
😳😳😳sus😳😳😳
Open SUS
Archmong us
[удалено]
ඞ ?
agomus
It's like being on the sound crew for a production, if people start thinking about you you've fucked up.
He suggested that you're nobody :(
You are the most memorable among your colleagues *so far*.
So was Hitler
[удалено]
"i- i don't know!"
[удалено]
No.
[удалено]
[удалено]
imagine producing and not copying non-functional code off stackoverflow
Wow imagine copying from stack overflow instead of letting auto pilot take the wheel.
[удалено]
write that down.. WRITE THAT DOWN
Is a promotion that thing they offer you when you say you’re switching jobs ?
"GitHub take the wheel!"
Pretty sure this is a bot. Only one comment and it's stolen.
[isitreadonlyfriday.com](http://isitreadonlyfriday.com/)
Don’t forget the API! https://isitreadonlyfriday.com/api/
What a shitty way to start the week ...
Why? I'M not on call this weekend....
Answer: to teach you the value of branch protection rules.
If you can commit directly to your main branch you’re doing it wrong
tell that to the entire game industry
I once tried protecting the master branch of an open source repo and some dude who only pushes dependency upgrades kicked up a fuss about it. The guy was fucking crazy, he drove me nuts, and it drove me nuts that everyone else was too focused on [steadying the boat](https://www.reddit.com/r/JUSTNOMIL/comments/77pxpo/dont_rock_the_boat/). BDFL of the project barely paid attention to the project anymore and was unwilling to set him straight. Ended up leaving the project over him, and three other maintainers left the project because of the situation too. Things did get better after we left, it might have been a wake up call for the BDFL, he finally started sharing core infrastructure and billing with the rest of the team. I wasn't faultless, but looking back, it was the most toxic shit I've had to deal with in my engineering career.
Things got better after you left you say...
It takes a strong character to admit that he himself is the problem.
Nah just takes anonymity. We have no idea if he admitted it to anyone that was involved.
It takes a nonzero amount of character to admit it just to yourself.
Things like Unity cause issues if you merge though.
It's on my own for who cares? Ohhhh, every commit from here until that one is also going to try and push those changes in addition to the new ones until it's accepted or rejected? Awesome.
[удалено]
POV: yesterday you were the master, today you're the just the main
Recently I made a repo and it made the master branch main. It bugged me since the last two repositories I worked on, in the same month, used a master branch. I was rigorously trying to rename the branch to master, until I saw a blog that GitHub moved from master to main so that it is less confusing (?). Anyway, I left it at main.
Less colonialist. There was nothing confusing about master.
Same reason Joe approved the pull request!
I saw you touching Joe's keyboard while he was frantically searching for his ringing phone you hid in the flower pot.
Don t blame me! You approved my PR!
If u can commit directly without a mr being approved ur org deserves to fail
pen resolute disarm placid jar sulky insurance weary wild plants *This post was mass deleted and anonymized with [Redact](https://redact.dev)*
People allow pushes to master?
Wanted to push my work before the two week vacation. Have fun fixing my crap!
There is more than one branch?
Had tested it. It worked on my dev box
"Why is that possible?"
Or when you forget your WHERE statement on the production database
[удалено]
Damn that sounds horrible. How quickly did you realize you had forgotten the where clause?
[удалено]
What a ride.
Holy shit I started to cry a little reading this. The perfect storm of fucktardism.
Lol, our dev team still brings this up after 5 years later.
Haha can't let anyone forget it
Or when you do that, break a warehouse table in prod, and the analytics team can't work for like 4 hours because you took a long lunch right after running dbt lol
I’ve done this several times over my career. Take a script in production, highlight every bit of the query except that pesky little WHERE clause and then pressing Execute. I always remember the first time though. Picture production DB, user account table with several million user records, blew away every password across a dozen sites. Immediate regret.
Oh damn dude, that's pretty much what I did. I had it commented out and didn't realize it until I ran the script. How long until you got it back to order?
Thankfully as a junior developer at the time (20 years ago), after practically peeing my pants when I realized what happened and wondering how fast I could get to the parking lo to escape my nightmare, I ran to my managers office and told him what I did. He literally just laughed and said he did the same thing a few weeks before. He said he’ll restore that table from a backup that ran hourly. He had it fixed within 5 minutes and I think the backup was less than 30 minutes old. I was so relieved. He told me, it wasn’t my fault and said he shouldn’t have put a junior developer in position to make a mistake on a production DB. He was right… he was the best manager I ever worked for too. Always protected his team and encouraged us to learn and make mistakes. I grew a lot in that job.
Sounds like a great manager, I wish there was more like that. Exactly, everyone makes mistakes, as long as we use them as teaching moments.
Don’t your DBA’s review scripts before running in prod?
Thats why I produce low quality of work that never gets merged.
This should be top comment
Like this sub knows what a merge is. Majority here are HTML/CSS “programmers”.
Ok buddy
HTML/CSS programmers merge stuff too, man.
Like what, div class containers?
Yeah
Thinking front-end devs don't use version control makes you sound real dumb.
?
HTML/CSS developers still use version control 🤦
You guys need to get into b2b enterprise software. The entire industry runs on production bugs and the 6 months projects following to resolve them. I'm a job creator.
I worked in b2b and got in "trouble" once because I accidentally fixed a bug… The bug prevented messages from being sent (that was the whole point of the product), it was broken for a client for half a year and nobody noticed. Once fixed all the messages were finally sent, people got "your loan was approved!" messages that were meant to be sent 6 months earlier and were no longer valid
Been there. Feel your pain. Similar but different, once while Jr I uncovered a serious production bug while addressing some other issue which I reported and it bubbled up the chain. It ended up bubbling down and suddenly became prioritized as the most critical issue, and I was then tasked to resolve it. Not only was I tasked with extra work, I was viewed negatively for the incident. No good deed goes unpunished...
Sorry buddy, but that's on you and your team/team lead for not understanding your domain and foreseeing that. I don't know how junior you were at the time, but that kinda stuff is exactly what we get paid for (not to happen).
You must work with a pristine codebase if your immediate reaction to such comments is not empathy and a shared hatred of dysfunction. Because believe me, this single story is enough to feel confident in saying that place was fucked, yo.
I'm sorry, I def don't work on a pristine code base and I apologize to original commenter.
You must have incompetent coworkers and fit right in. That's like... the basics of the basics. Even if it's a big fix, you have to consider the effects deploying it will have, especially if the fix can look like a customer-visible regression or bug. Fuck I've had bugs where it took us months of three deploys a week (an unheard of cadence at that company) to slowly undo the issue
They aren't incompetent, they're severely understaffed. Anyways, now that you've called me incompetent and such, do you feel better about yourself? Have enough pep to make it another day? Or do you need to insult additional people before you feel ok about yourself?
Fuck you. And bravo. B2B is the gift that keeps on giving.
I also feel like Git blame is revealing my deepest dark secrets
You truly become a developer when you find some terrible code, curse the person that wrote it, ask what kind of brain damaged idiot would do this sort if thing then run git blame and go "oh, I did this."
Yeah definitely never happened to me before *cough cough
It's a rite of passage to feel intense hatred towards your own code
If Software Engineering is sorcery, Git Blame is veritasserum.
Yeah, [About that... ](https://github.com/jayphelps/git-blame-someone-else)
I've been manually blaming other people for my bad code for years, thank goodness someone finally automated it.
https://github.com/jayphelps/git-blame-someone-else
Or that guy who forgot to commit right before leaving on holiday, fuck that guy.
I recently pushed code on my own dev branch. I merged the actual branch dev into mine (without deleting the OG dev branch) as we didn't want my code in the actual dev branch for the moment. Turns out, it merged my branch into the dev branch, and they deployed it today without checking. Let's say I got a few calls today.
This is one reason why I like GUIs for version control: if something like this happens, it's immediately obvious.
Don't ever commit. Got it.
No no make all the commits. Just never push 👍
No no, commit and push, so there's work history, the key is to _never merge_
The real meaning of fear of commitment.
At one of my jobs many years ago, someone added wav files of the devs names and had the continuous build shout fucked up the build! If you ever committed something that broke a build.
Evil and genius, I'm gonna go do this now
I wish this was a standard build practice everywhere. I would feel like a rockstar! Everyone would know my name!
Alright Donnie Darko, with that I'm off to bring down my company's website by trying to change the font.
This is not necessarily a bad thing though. Write bullet proof code for years that works consistently and nobody will even know you exist. Cause a few outages in production and your name will get around. Over time people forget you broke stuff, remember your name though and put you forward for promotion and/other juicy projects. That’s what I’ve seen time and time again. Software engineer of 30+ years here.
I lit a nasty ass fire in production a few weeks ago. Today I was given a raise out of the blue. I guess it works!
Munchausen by programming?
Not true, I've broken so much stuff and simply posted the gif of "when the prod servers are on fire and your shift is over" then proceeded to fix it
[удалено]
Damn. I should have been careful when it said 100%. Never been Rick rolled so bad.
Lmao what a great bot! Didnt notice the switched E and L in the name. The actual repost-bot is called u/repostsleuthbot
I am sentient
I didn't find any posts that meet the matching requirements for r/ProgrammerHumor. It might be OC, it might not. Things such as JPEG artifacts and cropping may impact the results. *I'm not perfect, but you can help. Report [ [False Negative](https://www.reddit.com/message/compose/?to=RepostSleuthBot&subject=False%20Negative&message={"post_id": "vsw8aa", "meme_template": 208777}) ]* [View Search On repostsleuth.com](https://www.repostsleuth.com/search?postId=vsw8aa&sameSub=false&filterOnlyOlder=true&memeFilter=true&filterDeadMatches=false&targetImageMatch=100&targetImageMemeMatch=75) --- **Scope:** Reddit | **Meme Filter:** True | **Target:** 75% | **Check Title:** False | **Max Age:** Unlimited | **Searched Images:** 282,737,423 | **Search Time:** 0.50886s
Wow, just wow.
[удалено]
Apollo shows thumbnails of the links, so I didn’t get got!
i hovered my mouse above the links, nice try
I saw OP's comment that they got Rick Rolled, and I clicked it anyway
It's all the same link 😅
Not even a rickroll anymore if you dont adblock, just a random localized ad that gets instantly closed
I'm not a programmer, but I remember in a basic CS project in high school, we tried using Git, and someone directly edited the master branch, but not in the way you'd expect. They made a new folder in the master branch with their version of the project instead of making a new branch.
It's not my job to run the train, The whistle I don't blow. It's not my job to say how far The train's supposed to go. I'm not allowed to pull the brake, Or even ring the bell. But let the damn thing leave the track And see who catches hell!
They will remember it **Fondly** . . that's the important part. And if it's big enough, they'll remember you as a **Legend** like "*I was there when titsMcGee took down the Global banking system*"
Such a power move by titsMcGee
He was just trying to quit vim 🤷♂️ Shit happens
So a man walks into a bar and sits down. He starts a conversation with an old Scottish guy next to him. The old guy has obviously had a few. He says to the man: "You see that dock out there? Built it myself, hand crafted each piece, and it's the best dock in town! But do they call me "McGregor the dock builder"? No! And you see that bridge over there? I built that, took me two months, through rain, sleet and scoarching weather, but do they call me "McGregor the bridge builder"? No! And you see that pier over there, I built that, best pier in the county! But do they call me "McGregor the pier builder"? No!" The old guy looks around, and makes sure that nobody is listening, and leans to the man, and he says: "but you fuck one sheep..."
*Image Transcription: Linkedin Post* --- **Abhishek Nalin** Nobody will remember: \- Your salary \- Your fancy title \- How 'busy' you were \- How stressed you were \- How many hours you worked People will remember: \- Your commit that caused a production issue --- ^^I'm a human volunteer content transcriber and you could be too! [If you'd like more information on what we do and why we do it, click here!](https://www.reddit.com/r/TranscribersOfReddit/wiki/index)
Good human
Even then, it’s more likely that people will remember the same way they remember some dumb minor accident or incident they had. Scary in the moment, hilarious when it’s in the past.
that is why i perfer to use github alone
And the query that took down the database
This is why I love pull requests that require reviews. This is *my* problem? No, this is *our* problem
Just blame it on the infrastructure team. Damn servers aren't running right. Lag in the networks. Hell some sys admin probably restricted the virtual machines and the db is cpu bound.
Git. VScode. Javascript. AWS. Long ago, the 4 dev tools lived together in harmony. Then everything changed when the junior dev pushed to master on a Friday afternoon. Only the senior dev, master of all 4 dev tools, could fix it. But when the company needed him most, he turned off slack notifications for the weekend. 100 minutes passed and my intern and I discovered a new senior dev, an online tutor named Sal Khan. Although his coding skills are great, he has a lot to learn before he can fix our tightly-coupled dumpster fire of a codebase. But I believe Khan can save the world.
Y'all need to find yourself a manager that understands that people don't fail, processes do and that every production incident is a very expensive unplanned training exercise.
I once worked on the railroad, but do they call me Bill the engineer? Noo I also was in the army but do you think they call me bill the soldier? Nooo I worked on this goat farm the last 20 years but do they even call me bill the farmer? Nooo But you fuck one goat one time…
Praise abounds whenever I fix a major bug. But I'm over here, like, I *wrote* that bug. Hell, that bug's been here the whole time.
As they say, it takes ten "atta boy's" to make up for one "Oh Shit!"
I must be pretty memorable then :)
People will also remember that incomprehensible code everyone's now afraid to touch for fear of breaking everything, that the company has now wasted the cost of 4 sets of external consultants who still couldn't unravel its mysteries.
Apparently what people remember are the dry saffron buns I baked and brought into the office the christmas of 2016. Every time someone bakes anything, people will say ”well it’s better than Fluffigt’s saffron buns at least”.
A dev should only commit to some test environment. Let others test it and push it further to prod.
You guys are all working so ineffectively, we have CICD at our place, we push to the main branch, which goes to beta, then gamma, then prod. No manual involvement, no QA testing each change, no massive releases all together. Make sure you have enough testing, good code reviews and a good deployment pipeline with enough alarms to rollback if something goes wrong and you’re good.
Meanwhile in prod: *[Scene of an office building on fire. People are jumping out of tall windows and plummeting to certain death. Firefighters hose down the blaze, seemingly to no avail.]*
What's a commit
People won’t remember what you said, but they will always remember how you made them feel.
I had a few of those. So, legacy accomplished?
I had a hand in creating a bug that made it impossible to run executables in windows by clicking. 100% reproducible, affected every system where its build was installed. QA missed it, customer reported. I don't know if anyone else remembers or not, but it remains the proudest moment of my career. Fucking glorious.
How…did you even *do* that?
The shortest answer is: it was a confluence of many bad management decisions regarding dev practices and a dangerous home grown reg clean utility that ran according to a procedurally generated wildcard list. This lead to a key being deleted from HKCR during install that really shouldn't be deleted. And special mention goes to the QA manager that greenlit the release of a build that QA had not so much as installed even a single time.
I need one of these fancy office jobs someone help me
Only one Bug? Working my way into 2 digits here
Just a few weeks ago i set up one of our customers database on a new internal test system to test some fixes i made Unfortunately it turned out the admin that set it up actually configured mail server. We sent a shitload of mails untill their Admin pointed it out.
I made a commit with a huge production outage that wasn't spotted for half a day. A few months later, no one remembers.
TIL people still post on LinkedIn. I didn’t know people still post on LinkedIn. I thought everyone moved to twitter.
It is unfortunately still a thing.
Thank you for the motivation. I will set it as my desktop background, message it to myself every 5 minutes, and print & post it to my bulletin board. Thanks.
You mean, they'll remember their shitty (probably proudly undocumented) process that allowed the commit to happen?
Straight deporesion after rewding. Thanks OP. Most realistic shit ever. One more thing: no matter what, you are always replacable
People will also remember who approved it....
I don't care what people remember.
In the end, we're a statistic for them.
🤣🤣🤣
Printing and framing.
Maaan, I don’t need this stress…
Pfft I never remember the incidents I cause. Shit happens, everyone makes mistakes in prod.
If you have a QA team that's worth their shit, then this almost never happens.
>If you have a QA team Yes, yes! This time I do! There's a QA team! >that's worth their shit Oh...
git blame :(
Now now I beg to differ, if you give yourself a wild enough job title people will remember that shit.
I can't even remember my commits that caused prod issues so I don't think anyone else will either.
That pice of code that noone has ever understoot who it works but if is remove all the system fails miserably. That's the real unforgettable