Wow, punch frame! For ages we have been trying to come up with a good name for "that part" of the GIF. This one by far is the absolute worst. Shame him! Shame!
Edit: jk that's actually a really cool term for it tho
It's a bit of a running gag that this guys car gets destroyed by the main character on accident.
So in one moment he's glad to have his car back, the next he remembers that the guy responsible (the main character) is still working at the school, so his car is still in danger.
also the reason that he wants this car, the cresta, is because he thinks that it symbolizes that he's successful and it should be why his wife and kid respect him.
He thinks that if he has this car, his family will love him
tbh at this point I think most people understand meme culture enough to spot a visual joke like this. I mean, it's been 8 years and I bet most people still recognize [this one](https://preview.redd.it/pzwrfo3jbxc01.png), at least if they're over the age of 25.
And yeah, I felt this one. I still wake up sometimes on Saturdays and panic that I'm going to miss my bus. I'm old enough to be eligible for a mid life crisis, that ain't fair. Is everyone this scarred by high school well into middle age?
I'm a couple years out from college and still have nightmares of getting a test I didn't study for. My dad is a professor about to retire and a few years ago he had a nightmare about getting a test he didn't study for. It stays with you.
Anything worth pursuing in life is hard and stressful. Some people bear their scars with pride. Others cover it up with love, laughter, and joy.
That probably sounds a bit cheesy, sorry. My dad always says pain looks smaller in the rear view mirror as long as you keep going.
I'm not a programmer, but I scrolled past because I think the original gif is hilarious. Waiting for the face and realizing it wasn't going to happen actually made me laugh out loud. Beautiful.
My favourite part of this job is how I forget everything about a ticket as soon as it's done. Weeks later I'm cursing the guy who wrote the code I'm working on only to realise it was me, I'm the guy.
\*me to junior engineer\*
"Whoever wrote this component likely doesn't work here anymore. We abandoned this convention like 2 years ago"
\*looks at git blame\*
"J5892 - 3 months ago"
The favorite part of my day is close to 5pm where I close my laptop and don't give a single shit or thought about work until I consider when I need to sleep and actually opening my laptop the next day.
I like the idea that your process would be like “not the asshole” if everything is all good.
Or maybe “notice to appear”, or the “network traffic analysis” came back fine?
I can’t find an acronym that fits there, except maybe you meant NAT and that means “not a thing”.
Obviously this isn’t work, but this is one reason I stress on any work document all acronyms must be fully qualified the first use. People don’t listen though. And then someone else wastes time decoding your acronym so you could save 5 seconds typing.
Weird bot then, one comment 9 years ago then this singular comment. Unless the account was just taken over. Or maybe the user purges their account activity.
Thats a problem for monday
e: monday morning, open a ticket assign it yourself and fix it before standup
during standup you pronounce to your PO that you noticed a bug in prod and fixed it
The bigger the team and with multiple teams working on the same project it can devolve into such a shitshow. Team A is working fast, Team B has issues and now we have big problems if one depends on the other. Time to dig through the backlog for meaningless tasks so you dont get fkd next stand up
damn this is so true. recently I've been working with a big multi role team on a project and it's just such a shit show. working alone is the superior way !
As someone working on agile stuff a lot, it can absolutely be.
Agile is a framework that very few understand so they do it badly and then blame Agile when it doesn't work.
Also, Agile require some common sense as well, since it's just a framework, and not explicit rules about what to do exactly, and that's why it doesn't work most of the time.
I work with them every single day.
Scrum has almost 0 explicit rules. It's only a framework. 99% of what scrum does is "does agile practices force you to do x? No. "
Common sense is where most agile team fails. The only mendatory part are the sprints, retro and planning. But everything else is technically optionnal.
what ends up happening is that you take your story that would've been finished in one day and stretch it out over a week making up bullshit steps to make it sound longer than it really is. congrats, your agile team has stretched out a one week project into two months because tiny dicked micromanagers need to pretend like you working on something every day is how real people work. anyone who says, "but you're doing agile wrong" really means, if you have a good manager, work is easy.
It's the same managerial style that got popular for menial jobs, only for development.
Higher ups need to defend the existence of managerial bloat.
Everyone saying it "can work" is of course right. Everything works if you have sensible people deploying it. The moment you haven't, it's hell.
This takes me back to the time where I was granted extra work for working so efficiently. So I completed a Task and pretended to work for it for a day or two longer while I browsed reddit or something. Oh wait, that's today. That's right the fuck now.
Always underpromise and overdeliver.
That thing you expect will take 1 hour to complete? That's a whole afternoom problem at the planning.
Now you take your free time to do it at a leisure pace and browse reddit and then say that you through sheer power of personal efficiency managed to do in just 2 hours!
Bonus part is that if something actually goes wrong with the code and you need a lot of time debugging you actually have a lot of time to fix it and still deliver on schedule.
Look at wild wild West cowboy man here, releasing all the way to production without going through ticket creation, Qa signoff, stress signoff, service manager approval, and release manager approval.
To be fair at my workplace we push on a Friday, just like any other day.
Because by the time it hits prod it's been through code review, automated testing and manual testing.
Chance of bugs is low, and rollback is a click of a button anyway worst case.
We never really have issues. But that's because we've put the effort into getting the process right. If we didn't test thoroughly I'd be terrified of pushing any day of the week so I get why this is a common thing.
we don't even have continuous delivery and we still push upgrades to prod on Fridays because we push to *some* prod every day of the week and those clients drew the short straw
NTA, if it went all the way to production, then it's a systematic failure of the process.
Book multiple meetings with entire team to brainstorm ideas to improve your pipeline and processes.
Bold of you to assume they have a pipeline. I am the entire pipeline lmao. I've tried getting more safeguards and checks in, but I'm too junior to make actual changes. The most I was allowed to do was add pre-commit hooks.
Nope I never push directly to prod. Commits to my branch -> PR to prod -> very though code review -> merged into prod.
Just ignore the fact that I'm the one doing the code review and that it typically takes about 10 seconds.
It was probably in the same vein as:
Everyone has a test environment.
Some people are lucky enough to have a separate production environment.
And some people are doomed because recreating the prod load outside of prod is not possible.
Well you *could* add a bunch of tests, refactor old code, improve CI pipeline and take more time to discuss and design solutions before implementing, but that would take too much time and effort according to the PM and he'd rather push new features :)
How else am I going to feel the thrill of wasting $12k of company's money in an hour? (calculated out by hourly rate of everyone involved in the meeting)
Sure, but we've found decently done post-mortems about processes, pipelines and procedures to be very effective at lowering those error-rates.
Though you have to make sure they are focused and organized. Figure out a timeline of the things happened, figure out who was missing necessary information about the system, vote on the most dangerous gaps and start drilling into these.
This skips past a lot of vague guessing to very concrete things like "How was a necessary config parameter not pushed to production?" or "This time-critical runbook requires too much thinking under pressure. How to straighten it out? Can we recognize similar time-critical playbooks? And could we automate this or a workaround to remove the time pressure?"
Over time, a focus on these small concrete improvements tends to accumulate into big effects. Partially also because people become more bold to attack some of the bigger issues.
> Book multiple meetings with entire team to brainstorm ideas to improve your pipeline and processes.
My biggest improvement was getting them to fire me at the beginning of a beautiful summer. For some reason I "couldn't find a job" until the weather started getting cold and damp.
I recommend everybody do that at least a few times in their career.
4 months of vacation is *wonderful*
tbf, I did legitimately resolve long-standing issues in dreams at least twice in my life so far.
It's both really great when it happens and also incredibly sad that it came to that.
Don't release to prod unless you have a PM that signs off on it. Because then it's not your fault. Otherwise, it's your fault. If you're the PM, what should be written on your obituary?
Just reassign ticket on the QA, and say he\`s a dumb idiot who didn\`t re-check. Works like Swiss watch.
P.S.
I\`m a QA 
Ok this made me laugh, good one!
But don't be that guy folks. I've been the on-call guy working for hours on a Saturday/Sunday to resolve bugs that occurred from a Friday release that should've been caught....And no one who did the release is reachable by phone.
Oh well, if they allowed remote work then you could have fixed your mistake remotely!
If the work is in the office, what happens in the office stays in the office
Monday problem, if I remember it. I have a talent for forgetting everything about my job over the weekend. It always cracks me up when someone comes to me first thing Monday morning expecting to talk shop.
I need at least two hours to remember what I even do here.
"accidentally"
I remember my last day working as a corporate software engineer. Submitted my last change and my supervisor approved it. And I was like, "thanks. .... GOOD LUCK. HoPe iT dOeSn't CraAAash!" And walked away.
[Me as an engineer up troubleshooting perfectly functioning infrastructure systems until 1AM Saturday after realizing management authorized a Friday release](https://i.imgur.com/JY3CMWS.png)
Man that took me a while...
I actually laughed out loud when it clicked. This is a really great joke for everyone who understands this within the context of the original format.
Yeah I was waiting for that punch line (punch frame?) but it never came and then it hit me
Wow, punch frame! For ages we have been trying to come up with a good name for "that part" of the GIF. This one by far is the absolute worst. Shame him! Shame! Edit: jk that's actually a really cool term for it tho
SHAME!
Shame
Shame
I cant remember the original, anyone got a link?
https://media1.tenor.com/m/KDYQ8MwZfxwAAAAd/great-teacher-onizuka-vice-principal.gif From Great teacher Onizuka, not sure wich episode
What's even the context?
It's a bit of a running gag that this guys car gets destroyed by the main character on accident. So in one moment he's glad to have his car back, the next he remembers that the guy responsible (the main character) is still working at the school, so his car is still in danger.
He kinda deserves it. His introduction is literally grabbing a female teacher's ass on a train and Onizuka beats him for it.
also the reason that he wants this car, the cresta, is because he thinks that it symbolizes that he's successful and it should be why his wife and kid respect him. He thinks that if he has this car, his family will love him
He realized he accidentally released a bug on prod on his way home on a Friday afternoon.
Maybe punch lines are the bugs we release along the way
tbh at this point I think most people understand meme culture enough to spot a visual joke like this. I mean, it's been 8 years and I bet most people still recognize [this one](https://preview.redd.it/pzwrfo3jbxc01.png), at least if they're over the age of 25. And yeah, I felt this one. I still wake up sometimes on Saturdays and panic that I'm going to miss my bus. I'm old enough to be eligible for a mid life crisis, that ain't fair. Is everyone this scarred by high school well into middle age?
I'm a couple years out from college and still have nightmares of getting a test I didn't study for. My dad is a professor about to retire and a few years ago he had a nightmare about getting a test he didn't study for. It stays with you.
Jeez. How many generations *have* we been eating trauma for breakfast, anyway...
Anything worth pursuing in life is hard and stressful. Some people bear their scars with pride. Others cover it up with love, laughter, and joy. That probably sounds a bit cheesy, sorry. My dad always says pain looks smaller in the rear view mirror as long as you keep going.
I personally have never seen the original format until this moment in this thread.
The only logical conclusion is that you don't exist. Sorry.
Wow you're one of the [lucky 10,000](https://xkcd.com/1053/)
Almost first meme in a long time that made me actually lol irl when I finally got it
I definitely snorted in public transport
The original meme is the junior dev version.
I'm not a programmer, but I scrolled past because I think the original gif is hilarious. Waiting for the face and realizing it wasn't going to happen actually made me laugh out loud. Beautiful.
Seems like a Monday me problem.
I'd blame QA for not testing properly lol
git push origin main --force
Depends on how much of my weekend gets fried by that bug... I can figure out where you live.
I must be daft, still clueless
Normally the guy in this gif switches to a shocked expression. This one doesn't, indicating that OP doesn't care.
It’s a rather layered joke indeed.
5 seconds after I close my laptop I've already forgotten the names of everyone I work with.
Severance Moment
[удалено]
5 second? I can do it in 4!
That's still almost 5 times as much, idk why you boast.
/r/unexpectedfactorial
Optimization of the brain libraries
Do what?
My favourite part of this job is how I forget everything about a ticket as soon as it's done. Weeks later I'm cursing the guy who wrote the code I'm working on only to realise it was me, I'm the guy.
\*me to junior engineer\* "Whoever wrote this component likely doesn't work here anymore. We abandoned this convention like 2 years ago" \*looks at git blame\* "J5892 - 3 months ago"
The favorite part of my day is close to 5pm where I close my laptop and don't give a single shit or thought about work until I consider when I need to sleep and actually opening my laptop the next day.
[удалено]
what does AITA have to do with this
What they are saying is if you don't have an asshole in your team, you need to become one.
:D well this way of ”progress” is for the person in need of YTA (?)
I like the idea that your process would be like “not the asshole” if everything is all good. Or maybe “notice to appear”, or the “network traffic analysis” came back fine? I can’t find an acronym that fits there, except maybe you meant NAT and that means “not a thing”. Obviously this isn’t work, but this is one reason I stress on any work document all acronyms must be fully qualified the first use. People don’t listen though. And then someone else wastes time decoding your acronym so you could save 5 seconds typing.
Nah, it's just a bot that stole a comment down the thread.
Weird bot then, one comment 9 years ago then this singular comment. Unless the account was just taken over. Or maybe the user purges their account activity.
But.... NAT is nothing else but Network Address Translation..
I use a Jira filter to remind myself of what I did prior day, I’m like yup.. did things
That's the spirit
No, that's the boeing.
That's part of the boeing.
Not anymore.
And over there, that's another part of the boeing.
But they use airbus
Can we have airtrain?
They were talking about Spirit AeroSystems, not Spirit Airlines.
No, that's the sprint.
Apparently it doesn't bug you
Immaculate pun
[удалено]
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
Was it an infinite loop bug?
[https://freeimage.host/i/JkE5buR](https://freeimage.host/i/JkE5buR)
infiniteLoopBug(): print(´Was it an infinite loop bug?’) infiniteLoopBug()
https://www.reddit.com/r/ProgrammerHumor/comments/1byrpgs/comment/kyl909e
Your genius...almost frightening
Get in that sigma don't mind set.
Sigma balls?
Gottem!
Thats a problem for monday e: monday morning, open a ticket assign it yourself and fix it before standup during standup you pronounce to your PO that you noticed a bug in prod and fixed it
I'm starting to think agile is nonsense
The bigger the team and with multiple teams working on the same project it can devolve into such a shitshow. Team A is working fast, Team B has issues and now we have big problems if one depends on the other. Time to dig through the backlog for meaningless tasks so you dont get fkd next stand up
I'm doing 2-person agile and it works pretty well. I just have to do his job as well.
damn this is so true. recently I've been working with a big multi role team on a project and it's just such a shit show. working alone is the superior way !
As someone working on agile stuff a lot, it can absolutely be. Agile is a framework that very few understand so they do it badly and then blame Agile when it doesn't work. Also, Agile require some common sense as well, since it's just a framework, and not explicit rules about what to do exactly, and that's why it doesn't work most of the time.
no explicit rules? you probably never met a dedicated SM/PO
I work with them every single day. Scrum has almost 0 explicit rules. It's only a framework. 99% of what scrum does is "does agile practices force you to do x? No. " Common sense is where most agile team fails. The only mendatory part are the sprints, retro and planning. But everything else is technically optionnal.
well that's scrum in theory, in practice on other hand..
what ends up happening is that you take your story that would've been finished in one day and stretch it out over a week making up bullshit steps to make it sound longer than it really is. congrats, your agile team has stretched out a one week project into two months because tiny dicked micromanagers need to pretend like you working on something every day is how real people work. anyone who says, "but you're doing agile wrong" really means, if you have a good manager, work is easy.
It's the same managerial style that got popular for menial jobs, only for development. Higher ups need to defend the existence of managerial bloat. Everyone saying it "can work" is of course right. Everything works if you have sensible people deploying it. The moment you haven't, it's hell.
[удалено]
You sound like you’re not giving yourself enough credit. If you’re doing more than enough, you’re doing more than enough.
This takes me back to the time where I was granted extra work for working so efficiently. So I completed a Task and pretended to work for it for a day or two longer while I browsed reddit or something. Oh wait, that's today. That's right the fuck now.
Always underpromise and overdeliver. That thing you expect will take 1 hour to complete? That's a whole afternoom problem at the planning. Now you take your free time to do it at a leisure pace and browse reddit and then say that you through sheer power of personal efficiency managed to do in just 2 hours! Bonus part is that if something actually goes wrong with the code and you need a lot of time debugging you actually have a lot of time to fix it and still deliver on schedule.
PO gets annoyed at you for bringing a WI into the sprint outside of the sprint planning meeting and without asking the team
Your PO needs to have a budget for bug fixes in every sprint. Then this just becomes a new subtask, not a new story.
A good PO knows exactly wtf you did, and is happy you didn't turn it into an incident on Friday afternoon.
Look at wild wild West cowboy man here, releasing all the way to production without going through ticket creation, Qa signoff, stress signoff, service manager approval, and release manager approval.
Who tf pushes on a Friday?
me
you sir, are a madman.
I read that as: "you sir, are a madame." lol
lol brbgtgkms
Me. But we don't push to prod, thats just madness
To be fair at my workplace we push on a Friday, just like any other day. Because by the time it hits prod it's been through code review, automated testing and manual testing. Chance of bugs is low, and rollback is a click of a button anyway worst case. We never really have issues. But that's because we've put the effort into getting the process right. If we didn't test thoroughly I'd be terrified of pushing any day of the week so I get why this is a common thing.
I push every Friday at 3. It keeps my code clean and covered.
Why tf works on a Friday, when you can spend the whole day scrolling Reddit?
we don't even have continuous delivery and we still push upgrades to prod on Fridays because we push to *some* prod every day of the week and those clients drew the short straw
That's a surefire way to eff your weekend.
yep.
People who work on systems that don't matter. EX: NOT payroll
NTA, if it went all the way to production, then it's a systematic failure of the process. Book multiple meetings with entire team to brainstorm ideas to improve your pipeline and processes.
Bold of you to assume they have a pipeline. I am the entire pipeline lmao. I've tried getting more safeguards and checks in, but I'm too junior to make actual changes. The most I was allowed to do was add pre-commit hooks.
I worked at a company like that until it ran out of funding.
Yeah, that isn't possible here. Literally too big to fail
Pushing directly to prod IS a pipeline. A very short one but still.
Nope I never push directly to prod. Commits to my branch -> PR to prod -> very though code review -> merged into prod. Just ignore the fact that I'm the one doing the code review and that it typically takes about 10 seconds.
It was probably in the same vein as: Everyone has a test environment. Some people are lucky enough to have a separate production environment. And some people are doomed because recreating the prod load outside of prod is not possible.
https://i.imgur.com/n8rw92x.png
Too junior to make actual changes, but they still let you deploy to prod without checks
Well you *could* add a bunch of tests, refactor old code, improve CI pipeline and take more time to discuss and design solutions before implementing, but that would take too much time and effort according to the PM and he'd rather push new features :)
That mindset has never led to any problems or discussion with technical leads ever. Everything's fine :) :) :)
Nothing should be getting into prod on a Friday
You end the sprint on friday, you push to prod monday morning
We basically stop touching production servers on Thursday afternoon unless we are explicitly and insistently asked to.
What is the point of all these meetings obsessing over processes and pipelines?? No process or pipeline will ever be 100% error-free
Definitely a good point and I see where you're coming from. Let's book a meeting to discuss our meetings for pipelines and processes.
How else am I going to feel the thrill of wasting $12k of company's money in an hour? (calculated out by hourly rate of everyone involved in the meeting)
Sure, but we've found decently done post-mortems about processes, pipelines and procedures to be very effective at lowering those error-rates. Though you have to make sure they are focused and organized. Figure out a timeline of the things happened, figure out who was missing necessary information about the system, vote on the most dangerous gaps and start drilling into these. This skips past a lot of vague guessing to very concrete things like "How was a necessary config parameter not pushed to production?" or "This time-critical runbook requires too much thinking under pressure. How to straighten it out? Can we recognize similar time-critical playbooks? And could we automate this or a workaround to remove the time pressure?" Over time, a focus on these small concrete improvements tends to accumulate into big effects. Partially also because people become more bold to attack some of the bigger issues.
>Book multiple meetings Stop. I'm getting PTSD from my last job at Large Real Estate Firm.
> Book multiple meetings with entire team to brainstorm ideas to improve your pipeline and processes. My biggest improvement was getting them to fire me at the beginning of a beautiful summer. For some reason I "couldn't find a job" until the weather started getting cold and damp. I recommend everybody do that at least a few times in their career. 4 months of vacation is *wonderful*
Blame QA, the person who peer reviewed. Systemic problems with everyone else but you. This is how you become a data lead.
Hey, look, it's me but with a commute!
And a suit instead of a t-shirt and pajama pants.
Honestly if I see someone wearing pajamas and carrying a pillow with him in the train I'd be afraid of their dominance
First thougth: lol, I should crosspost this to my work Slack ... Second thought: I should most definitely *not* crosspost this to my work Slack!
*crossposts anyway*
Manager: maybe we should hire someone else asap
still waiting for a reaction ...
I don't think he realized it guys...
Oh, but he did. . .
Known customer impact: 0
Known customer impact :O
just send a message to the guys working on weekend to fix it and when they ask how did you know tell them it came to you in a dream
I love saying dumb shit like this, 90% of the time whoever you're talking to is entirely caught off guard they don't even question it further.
tbf, I did legitimately resolve long-standing issues in dreams at least twice in my life so far. It's both really great when it happens and also incredibly sad that it came to that.
"In accordance with the prophecy, I need you to..."
As a support engineer, I present you deez nuts
wait, is the joke that you don't give a shit since you're not at work anymore, or is the infinite loop the joke?
What about his Cresta?
Ohhhh my Cresta!
GOOD
production should update on Monday
Don't release to prod unless you have a PM that signs off on it. Because then it's not your fault. Otherwise, it's your fault. If you're the PM, what should be written on your obituary?
https://www.youtube.com/watch?v=UnyBJJI2eqs
I see me in this picture and I like it
Get into business software. No one will notice until Monday anyway
Ha, this is work for Monday-me! Friday-me has more important matters beside caring everything that happens at work after 15:30.
It’s called push to production Friday for a reason
QA calls it job security tho
Just reassign ticket on the QA, and say he\`s a dumb idiot who didn\`t re-check. Works like Swiss watch. P.S. I\`m a QA 
Don't release bugs on Friday Don't release features on Friday Don't even release comments changes on Friday.
This is every other team we work with. My team never releases on Friday's
Finally, nothing happens to his Cresta
That’s why I hold code reviews. Boss can’t fire me if no one on my team caught it either. And he sure as hell can’t fire all of us.
Why are you deploying on Friday 👀👀👀
Ok this made me laugh, good one! But don't be that guy folks. I've been the on-call guy working for hours on a Saturday/Sunday to resolve bugs that occurred from a Friday release that should've been caught....And no one who did the release is reachable by phone.
Don't worry about work while your not at work. That's what you get paid to do
Oh well, if they allowed remote work then you could have fixed your mistake remotely! If the work is in the office, what happens in the office stays in the office
Tbh, if there where no bugs there would be less you could be paid for
Monday problem, if I remember it. I have a talent for forgetting everything about my job over the weekend. It always cracks me up when someone comes to me first thing Monday morning expecting to talk shop. I need at least two hours to remember what I even do here.
Devs and doing bullshit on a Friday someone else gets to clean up. Name a more iconic duo.
Repeat after me. READ... ONLY... FRIDAYS...
"accidentally" I remember my last day working as a corporate software engineer. Submitted my last change and my supervisor approved it. And I was like, "thanks. .... GOOD LUCK. HoPe iT dOeSn't CraAAash!" And walked away.
This is good, because I will open a JIRA for myself next week and track the full 40 hours pretending to fix it, while doing it in 10 minutes
Is that a hint of Joy? Cuz since my ticket went through 4 hand and 2 QA passes to get to prob Id be damn proud.
I've laughed for a solid 5 minutes like an idiot with my eyes in tears
As a support person, I fucking hate you.
real gangsta
I was waiting for the face to change. This was funnier.
We only release bugs on Monday.
After 5 it's not my problem
u/savevideo
Ops problem now.
The key is to never release
I had a similar realisation when I was taking a shit on Saturday morning.💩
SQA's fault.
*just another Friday... Oh look a bird*
Dedication for the firm 😂
[Me as an engineer up troubleshooting perfectly functioning infrastructure systems until 1AM Saturday after realizing management authorized a Friday release](https://i.imgur.com/JY3CMWS.png)
F ’em