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 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.
So we called this meeting to discuss a change in procedures. HR would like us to remind you that this is entirely unrelated to last week. Also has anyone seen Joe? We'd like him to be here for this. No reason why.
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.
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.
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.
I swear to god this drives me nuts. It was fine years ago. Now it’s ass. What the fuck?
I think it has to do with the architecture. Just a wild guess, but I assume that the design is susceptible to indeterminate results based on device performance. Because it’s really fucking bad when my phone gets a little hot.
My guess is that modern phones are doing 50x more shit than they need to. So passive QoL features like autocorrect are being choked.
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.
Some managers would praise him for his "spirit", congratulate the rest of the team for their "sacrifice", and still not give anyone a bonus nor a raise, because "that's just the job!".
52 Comments
A_norny_mousse@piefed.zip · 201 pts · 39d
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.
Sanguine@lemmy.dbzer0.com · 94 pts · 39d
Jpeg patina 🤣
hosaka@programming.dev · 26 pts · 39d
That also cracked me up. Great phrase
BassTurd@lemmy.world · 52 pts · 39d
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.
sp3ctr4l@lemmy.dbzer0.com · 35 pts · 39d
You vastly overestimate the number of companies that are 'worth anything'.
almost1337@lemmy.zip · 18 pts · 39d
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.
Sergio@piefed.social · 11 pts · 39d
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.
yggstyle@lemmy.world · 1 pts · 38d
So we called this meeting to discuss a change in procedures. HR would like us to remind you that this is entirely unrelated to last week. Also has anyone seen Joe? We'd like him to be here for this. No reason why.
Earthwormjim91@lemmy.world · 4 pts · 39d
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.
BassTurd@lemmy.world · 4 pts · 39d
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.
Earthwormjim91@lemmy.world · 1 pts · 39d
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.
BassTurd@lemmy.world · 1 pts · 39d
Correct. I'm just saying that I proof read my work, that I deploy things, and that I don't proof read my texts.
Earthwormjim91@lemmy.world · 2 pts · 39d
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.
untorquer@quokk.au · 17 pts · 39d
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.
filcuk@feddit.uk · 21 pts · 38d
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.
untorquer@quokk.au · 7 pts · 38d
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.
partofthevoice@lemmy.zip · 3 pts · 37d
I swear to god this drives me nuts. It was fine years ago. Now it’s ass. What the fuck?
I think it has to do with the architecture. Just a wild guess, but I assume that the design is susceptible to indeterminate results based on device performance. Because it’s really fucking bad when my phone gets a little hot.
My guess is that modern phones are doing 50x more shit than they need to. So passive QoL features like autocorrect are being choked.
FaceDeer@fedia.io · 13 pts · 39d
The older the jpeg the more likely it is that he's moved on to another job by now.
Aatube@kbin.melroy.org · 12 pts · 39d
could just be ADHD. the impulse to speak your mind rarely translates to the impulse to speak to da computah
tias@discuss.tchncs.de · 5 pts · 39d
If you have to proofread when deploying you're doing things wrong
1984@lemmy.today · 2 pts · 38d
I doubt it's real. Most of the screenshots here are just Ai generated for people to react to. It's entertainment.
EmilieEasie@fedinsfw.app · 129 pts · 39d
the politeness of this interaction is what makes me laugh
"I know but I insist 🙏"
db2@lemmy.world · 40 pts · 39d
Applogies
aeronmelon@lemmy.world · 111 pts · 39d
What a power move. Now he gets a paid day off.
DickFiasco@sh.itjust.works · 30 pts · 39d
John's playing 4D chess
roofuskit@lemmy.world · 14 pts · 39d
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.
bamboo@lemmy.blahaj.zone · 22 pts · 39d
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.
matlag@sh.itjust.works · 4 pts · 37d
Some managers would praise him for his "spirit", congratulate the rest of the team for their "sacrifice", and still not give anyone a bonus nor a raise, because "that's just the job!".
nexguy@lemmy.world · 71 pts · 39d
I'm going to destroy the servers and db then murder the janitor with a hammer.
Oops *deploy
Janx@piefed.social · 29 pts · 39d
Please take a vacation!
He has a family. 🙏🏽
Dumhuvud@programming.dev · 8 pts · 38d
What's the point of deploying a janitor with a hammer when the servers are already destroyed? Smh my head.
hoohoohoot@fedinsfw.app · 1 pts · 33d
Thats a good one
vane@lemmy.world · 64 pts · 39d
Claude run destroy production script.
RogueBanana@piefed.zip · 31 pts · 39d
Aka Claude, do a basic task
Rentlar@lemmy.ca · 46 pts · 39d
🙏🙏🙏🙏
eager_eagle@lemmy.world · 21 pts · 39d
Diplomjodler3@lemmy.world · 36 pts · 38d
Oh yeah baby, destroy my backend!
hoohoohoot@fedinsfw.app · 2 pts · 33d
No problem
I jus need to run touch
Then mount
nitroemdash@lemmy.wtf · 32 pts · 38d
Who the hell uses WhatsApp for comms in IT?
roserose56@lemmy.zip · 13 pts · 38d
Not all companies have fancy teams and other related apps to communicate.
WhyJiffie@sh.itjust.works · 12 pts · 37d
teams is not fancy, I would say its worse
hoohoohoot@fedinsfw.app · 4 pts · 33d
Fancy?
Matrix is fancy
unquietwiki@programming.dev · 5 pts · 38d
I used to do contract work for AVASO; they were using WhatsApp for comms at the time.
vivalapivo@lemmy.today · 4 pts · 38d
Banks with obscure security rules
matlag@sh.itjust.works · 2 pts · 37d
Yeah, probably so obscure that no one could decipher them…
mexicancartel@lemmy.dbzer0.com · 17 pts · 37d
Oops sorry
rm -rf ./*Just a typo mb
roserose56@lemmy.zip · 7 pts · 37d
Please take a the day off 🙏, please 🙏!
garbage_world@lemmy.world · 12 pts · 39d
terranoid@lemmy.cafe · 36 pts · 39d
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
mjr@infosec.pub · 3 pts · 38d
Especially someone who typos.
roserose56@lemmy.zip · 3 pts · 38d
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.
1984@lemmy.today · 6 pts · 38d
This is typical tech timeline too. Everything is so rushed that shit literally happen in minutes.
SwissArmyKazoo@lemmy.world · 5 pts · 38d
It'll never not be hilarious how anyone could be so polite in a scenario like this.
Kinda feel bad for them tbh.