Menu

Why Your Automatic System Might Be Hiring and Firing for the Wrong Reasons
📰

Why Your Automatic System Might Be Hiring and Firing for the Wrong Reasons

DEV Community: cloud·Haripriya Veluchamy·22 days ago
#OhdhZU9J
#devtocloud#devto#dev#number#average
Reading 0:00
15s threshold

Imagine you run a small restaurant chain five branches, one shared kitchen manager watching all of them from head office. Instead of visiting each branch, the manager watches one number on a screen: "average busy-ness across all branches." When it's high, hire more chefs. When it's low, let some go.

Sounds efficient. It's also exactly how a lot of automatic systems decide when to add or remove servers and it can go wrong in the exact same way it would go wrong for our restaurant.

Lie #1: the average can hide the real picture

Say two of your five branches are completely slammed, and three are quiet. The "average busy-ness" comes out looking... totally normal. Nothing about that one number tells you two branches are drowning and need help right now .

Or the opposite happens: all five branches are only a little busy, but the way the number gets calculated say, by adding up small readings from each branch at slightly different times makes the combined number spike for no real reason.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.