undefined | Better HN

0 pointsWorldMaker3y ago0 comments

Even if you don't think you need that much operations labor at scale (and I'm assuming you are drastically under-estimating Twitter's current scale), when you do a 50% layoff before you even know your exact bus factor and are assuming a 100x/1000x redundancy (somehow), what are the odds you lay off one of those "few" people that are critical to operations? How do you know you haven't thrown out the needles in that big of a haystack?

0 comments

sillysaurusx3y ago

Software engineers: we’re engineers

Also software engineers: be sure not to fire Ned or else the whole bridge might collapse

jljljl3y ago

At the scale of a company like Twitter, the product and infrastructure are less like a static bridge and more like a complex living, evolving organism. So the analogy is not a very good one.

So your patient might be ok if you fire Ned, but if you try to make changes and a critical system goes down, it might take you a lot longer to fix things without the specialists in that system.

You could keep one specialist around for each system, but then you have a very small bus factor.

ZeroGravitas3y ago

Bridges have ongoing inspection and maintenance work that will lead to collapses if you decide to just skip it for no good reason too.

vineyardmike3y ago

It’s not one bridge it’s thousands of bridges, it’s just not know how critical each bridge is. Or how critical it becomes when another one is down.

Look at all the other major engineering failures in history, it’s always small things (a gasket) on a bad day (too cold?) that somehow works day after day until one day it magically doesn’t and you get the Apollo incident. Everything goes catastrophic over tiny things. Imagine if NASA fired half their team before that incident. The only guy who knew the gasket can’t get cold might not still be there because Ned got laid off.

WorldMakerOP3y ago

Management: Ned didn't print enough code from the last 60 days. There weren't enough pages of paper. Firing Ned.

Software engineers: We did document he was a load-bearing Ned. He was Ops, of course he doesn't code regularly.

SamoyedFurFluff3y ago

To be fair this is how a lot of industrial engineering works too. Ol joe retired and now we don’t know what’s that special modification we need to make to smooth the flight of planes, cause Joe just knew. This is a lot of military and airplane production.

j / k navigate · click thread line to collapse