This is typical tech timeline too. Everything is so rushed that shit literally happen in minutes.
Oh yeah baby, destroy my backend!
I’m going to destroy the servers and db then murder the janitor with a hammer.
Oops *deploy
Please take a vacation!
He has a family. 🙏🏽
Assuming green is the boss: I totally agree. If you don’t proofread your texts before hitting send, that might be indicative of how you deploy things, too.
I’d love to know how the story continues - did they lose their job? - but considering the JPEG patina on this I don’t think we’ll ever find out.
I doubt it’s real. Most of the screenshots here are just Ai generated for people to react to. It’s entertainment.
Normally i would disagree completely as texts have crappy input on a small screen and are meant to be fast. I have typos in mine constantly because swide input and it’s obvious what the word should have been.
But yeah, an important text like this does merit at least one read through.
My texts are rubbish because, somehow, the keyboard predictions & autocorrect are worse now than 5 years ago. We have LLMs barfing out fully coherent sentences on their own, how does this even happen.
Yeah, we could have functional input but no we have to destroy our planet to summarize a one sentence email into a multi-paragraph bulleted list - it’s bullshit
on android Heliboard + the swype library is ok. It’s at least consistent.
Jpeg patina 🤣
That also cracked me up. Great phrase
If you have to proofread when deploying you’re doing things wrong
I barely proof read anything I type on my phone, and my comment history is a testament to that. I deploy code or system changes most days, but I proof read the shit out of those on top of the QC they goes through. Any company worth anything will have a process for reviewing and approving anything being deployed, or probably destroyed for that matter.
Up until recently I worked for a company worth anything, and you would be surprised at how *many" major outages were caused by either skipping the process or gaps in the process.
You know that adage: “the safety rules are written in blood”? The same is true for change processes, just with a cost measured in dollars instead of human injury/worse.
Or sometimes there are just multiple failures. That’s what I learned from reading Admiral Cloudberg about air disasters: even if you have n safety measures, there’s still the chance that there’ll be n+1 failures.
You vastly overestimate the number of companies that are ‘worth anything’.
Code should ideally be going through tests before prod anyway. There should be no code changed from successful test to prod. Proofreading shouldn’t matter at that point. Just scheduling the actual deploy.
I mostly mean proof what I’ve written prior to having someone else test. I often will comment out lines when trying different things so I just make sure I clean up what I’ve done. We have a few human checks as well as some automated checks between each stage of deployment for each environment.
Yeah that’s what the MRs are supposed to be for. To catch those and proofread.
There shouldn’t be any changes at all from the last test to going to production though. Even cleaning up comments.
Correct. I’m just saying that I proof read my work, that I deploy things, and that I don’t proof read my texts.
No I got that. I’m saying that by the time the prod deploy comes around, there’s no proofreading left to do anyway.
Not proofreading texts should have zero bearing on being able to write and deploy software because it should be proofread several times before the actual prod deployment. Hell it very likely isn’t even the same person doing the deployment that wrote the code.
could just be ADHD. the impulse to speak your mind rarely translates to the impulse to speak to da computah
The older the jpeg the more likely it is that he’s moved on to another job by now.
the politeness of this interaction is what makes me laugh
“I know but I insist 🙏”
Applogies
What a power move. Now he gets a paid day off.
I had a coworker who tried something like this on a federal holiday, ended up bringing down production on everyone’s day off, and ruining a bunch of people’s days to clean up the mess just because someone was trying to go above and beyond.
John’s playing 4D chess
He’ll be the next US president, but for that he’ll have to actually destroy everything he touches, not just make threats to do it.
Claude run destroy production script.
Aka Claude, do a basic task
Brb baws imma just do a quick lil
ddcommand in prd🙏🙏🙏🙏
du* - applogies hehe
I don’t get it. Why the other person, presumably their boss, asked them to take a day off?
Because if you are about to destroy the db and you dont pick up the calls, you give him the day, so he wont do it. Thats what I get.
Some people try to work the weekend or weird hours, even when no one asked them to.
And a deploy by someone you don’t trust to deploy on the weekend would be a concerning situation
Especially someone who typos.
