Some of the situations may be familiar to you. Enjoy!
When I show my boss that I finally fixed a bug:
When the project manager enters the office:
When I prepare the code for release:
When I try to fix a bug at 3 am:
When my regular expression worked exactly as expected:
When my friend asked me to fix a Joomla site:
When I was told that the module I had been developing all week would never be used:
When code that I haven't tested works fine in the stable version of the project:
When the sellers reported that they had sold our software to a client:
The first time I apply new CSS:
When the sysadmin finally gave us root access:
When I ran my script for the first time after hours of development:
When I go on vacation while everyone else is trying to fix bugs:
When we released the beta and got notified about the first bug:
When the boss is looking for someone to urgently fix a complex bug:
When code that works on Friday no longer works on Monday:
When I asked a new colleague to continue working on the code:
When a bug was not noticed during the presentation of the product:
Share your favorite memes and situations in comments!
Btw, you can support my work by buying me a coffee! I'll leave here a few links for you:)
You can also support me on Coinbase
Top comments (21)
Great Collection....
No Gifs from me, only Meme Pics some of them u probl. have already seen on Twitter, from where i've probl. stolen them :D
so long
git commit --amend --no-edit && git push --force origin mainOoooohhh no please shoot me now π€’
Confession time: I do this quite often for projects that I haven't officially released yet and that have no other contributors. Usually for minor changes to previous commits, but also sometimes when I'm just being lazy.
Its slightly-less-evil cousin
git commit --amend --no-edit && git push --force <remote> <some-other-branch>is also really handy for making minor changes to still-unmerged PRs.Well to be fair when u're the only contributor in a repo then its whatever and/or its a hobby project, just to play around with some tech, i do this as well.
But i've seen ppl do this on real projects with multiple ppl where in the end a product or service should pop out. Then its a big 'no no' for me bc in the end you're just lying at that point in what should be your single source of truth.
The only thing i will always defend is squash commits when merging a branch. Because no one wants to see my commit history:
So i squash it, that when you hand over the repo to a customer he has some professional commit history and not the timeline of my rage induced breakdown :D.
So, yeah you're not the only one to do this but like you i would never do this in a real repo :D.
so long
It's hilariousπ
Im partial to the "Wrong Database selected" Meme π
That needs an addendum (last backup 455 days ago)
True Customer Sentence:
Oh yeah we have a backup. Hey βIn-house IT Guyβ letβs restore that vm snapshot from the DB serverβ.
Me: Oh no
Me: π₯² Iβm fine π₯²
The irony about the bricklaying one is that it actually takes way more skill to do this style of masonry βwrongβ than to lay it normal. IIRC the style is called drunken brick.
When the sales team reports that they have sold our software to a client before the product is even ready for testing:
π«‘ποΈ <-- For evey dev who found themselfs in that situation
Well captured.
Perfect list π€£π€£
very nice :D
Pretty accurate I'd say. lol
Wow, Great Collection....
It's funny.
So funny and relevant. I can't stop laughing.
Some nuggets from me:
I met JavaScript for the first time
Too terrible hahaha.
Keeping everyone happy...
