all 50 comments

sorted by: hot top controversial new old
[–] 205 points 2 months ago* (20 children)

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.

  • source
  • hideshow 20 child comments
  • [–] 53 points 2 months ago (9 children)

    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.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 19 points 2 months ago* (last edited 2 months ago) (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 2 months ago

    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.

  • source
  • parent
  • [–] 4 points 2 months ago (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 17 points 2 months ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 21 points 2 months ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 2 months ago

    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.

  • source
  • parent
  • [–] 3 points 2 months ago

    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.

  • source
  • parent
  • [–] 131 points 2 months ago (1 child)

    the politeness of this interaction is what makes me laugh

    "I know but I insist 🙏"

  • source
  • hideshow 1 child comment
  • [–] 114 points 2 months ago (4 children)

    What a power move. Now he gets a paid day off.

  • source
  • hideshow 4 child comments
  • [–] 22 points 2 months ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 72 points 2 months ago* (3 children)

    I'm going to destroy the servers and db then murder the janitor with a hammer.

    Oops *deploy

  • source
  • hideshow 3 child comments
  • [–] 64 points 2 months ago (1 child)

    Claude run destroy production script.

  • source
  • hideshow 1 child comment
  • [–] 46 points 2 months ago (1 child)

    Brb baws imma just do a quick lil dd command in prd

    🙏🙏🙏🙏

  • source
  • hideshow 1 child comment
  • [–] 38 points 2 months ago (1 child)

    Oh yeah baby, destroy my backend!

  • source
  • hideshow 1 child comment
  • [–] 33 points 2 months ago (6 children)

    Who the hell uses WhatsApp for comms in IT?

  • source
  • hideshow 6 child comments
  • [–] 18 points 2 months ago (1 child)

    rm -rf /*

    Oops sorry rm -rf ./*

    Just a typo mb

  • source
  • hideshow 1 child comment
  • [+] 12 points 2 months ago* (last edited 2 months ago) (3 children)
  • [–] 6 points 2 months ago

    It'll never not be hilarious how anyone could be so polite in a scenario like this.

    Kinda feel bad for them tbh.

  • source
  • [–] 6 points 2 months ago

    This is typical tech timeline too. Everything is so rushed that shit literally happen in minutes.

  • source