this post was submitted on 07 Jul 2026
552 points (99.3% liked)
Programmer Humor
32162 readers
1217 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
If you have to proofread when deploying you're doing things wrong
Jpeg patina 🤣
That also cracked me up. Great phrase
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.
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.
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'.
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.