295
Cloudflare DDoSed itself with React useEffect hook blunder (www.theregister.com)
submitted 1 year ago by to c/technology@lemmy.world
25 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 year ago (2 children)

I think most people have done, or been part of a team that did, something similar.

At least most of the engineers I've worked with have had similar stories from their past

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 5 points 1 year ago (1 child)

    Idk most teams I've worked with have either known better than to deploy anything at EOD or on a friday, or make heavy use of feature flags so any change that caused an issue just got swiftly rolled back. The ones that didn't, I made it ABUNDANTLY clear that I won't be available outside of work hours.

    Maybe I haven't been around the block enough or maybe I got lucky...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 3 points 1 year ago*

    Probably depends on the type of company you work in. If it's a long established one with lots of staff, they've probably realised this issue a long time ago and put plans in for it.

    If it's a more modern one that hired a bunch of solid old heads early on, they probably know better from the outset.

    In both cases, someone, somewhere will have probably experienced it and said "never again", so implemented (or improved) release procedures to ensure it doesn't happen again

    A lot of my teams have been on the younger side and for small companies/startups. So everyone either had a recent example to pull from or had first have experience

  • permalink
  • fedilink
  • source
  • parent