Friend, how would you rollout the covid vaccine?
You want to ensure equitable access, fairness, prioritize the vulnerable, immunize frontline workers, go as fast as supplies allow, and eventually get everyone immunized. If they want to.
Fun thought experiment for you, huge problem for policy makers.
While Israel delivered the first dose to 1.5 million people – 16% of the population, the US sits at 11 million – 3% of the population. With some states going as fast as possible and others saying "We'll have a plan that ensures fairness in 5 weeks".
Everyone is worried about jumping the line. Stealing doses from those more deserving. Yet up to 40% of those offered say no. Causing huge delays.
How would you approach this?
You could try statistical regressions or plain old simulation, but really this is a problem for queueing theory. The most useful comp sci class I took in college.
Not because I remember the formulae, because of the intuition. 😅
Queueing theory talks about the behavior of queues. How do you design a system that processes every request in time? What if some requests fail? What if long waits lead to bailing? What if time to process a request varies? It's cool.
λ – request rate (typical time between requests) μ – typical number of requests served per unit of time
A basic M/M/1 queue – memoryless arrival, memoryless service time, 1 server – assumes requests don't affect each other. Complexity blows up fast when they do.
Let's assume we have infinite supply. You can buy or produce vaccines as fast as we can distribute them.
USA has purchased 100 million doses and distributed 11. Supply is not the problem.
Fairness is a problem. 100 million is a 3rd of the population. Distribute without priority and you could leave the people who need it most.
But if you can vaccinate fast enough, fairness doesn't matter. If everyone gets vaccinated in 4 weeks, does it matter that grandma waited 2 weeks and you waited 2 days? Nah.
Queue performance depends on λ – arrival rate – and μ – processing speed. Arrival rate fills up your queue, processing drains it.
We know the queue is full. That leaves processing speed.
I recently lucked into getting vaccinated. It took 60 seconds. Doctor says hi, walks you to a chair, asks about allergies, gives you a pamphlet, delivers the shot, walks you out.
60 seconds of their time.
You spend many minutes getting there, 5 minutes in the waiting room, 15 minutes afterwards waiting for any allergic reactions. We can ignore your time for now.
What's the fastest you can get everyone vaccinated?
Let's try a [first-in-first-out queue](https://en.wikipedia.org/wiki/FIFO_(computing_and_electronics). First come first served. Like a taco truck.
You've got 1 doctor working their butt off. They need no sleep and no rest. Everyone shows up on time.
At 60 seconds per patient, you'll need 328,000,000 minutes. 624 years.
You'll need more than 1 vaccination site. How many? Is FIFO the best approach?
If you had 328,000,000 doctors, the queue falls to zero. Everyone vaccinates themselves and you're done in 1 minute. The problem becomes delivering the medicine.
USPS is good at logistics, but do you trust people to do it themselves? And to keep the medicine at cryogenic temperatures?
To vaccinate everyone in a month, you'll need:
To achieve a vaccination rate of 7488/min, you'll need 7488 vaccination sites that never rest. We don't have that many and they do need rest.
Let's assume a typical clinic stays open for 8 hours. Hospitals have shifts and operate 24/7, but that averages out.
Or as physicists say: "A cow is roughly a sphere"
At 8 hours/day and working full-time on vaccinations, your 7488 sites take
91 days. That's 3 months. Is 3 months long enough to worry about priority and equitable outcome? 🤔
You've got 7488 doctors working 8 hours per day, vaccinating 1 person per minute. You don't need 7488 clinics for this, doctors can work side by side.
And when 30% say no that destroys your FIFO queue.
FIFO holds spots. You put everyone in the queue. When it's their turn you reach out.
1. Hey your turn
3. move on to next person
That takes time too! It's processing before processing. Technically a queue feeding into the vaccination queue.
To ensure absolute fairness, you have to wait for a response. Even if everyone is ridiculously fast to reply – 5 minutes – that increases processing time to 6 minutes.
In the best case (everyone says Yes) that increases your time from 91 days to 547 days. Just to stay fair. 🤯
And we know people don't reply that fast.
Every No adds another 5min wait. You can model average wait time as a Bernoulli trial and that's where my math taps out.
Lossy fairness means you don't wait for a response. Offer vaccine, move on to the next person.
You go as fast as you can, prioritize the needy, and replies don't slow you down.
Intuitively, a lossy fairness approach works best. You make vaccines available based on priority and vaccinate based on who says Yes first.
Rejections don't affect processing time. Fairness guaranteed by probability. It takes time to go down the prioritized list and send emails. You can do it in batches.
That's what Israel did. "If you're 85 and older, come and get it". When batch runs out, say "If you're 80 and older, come and get it".
Shots. In. Arms. Forget fairness and priorities, dole that shit out. Make it fly.
And we kinda derived Little's Law. Queue length depends on arrival rate and time spent in the system. Nothing else.
And we had nerdy fun ✌️
PS: this is all back-of-the-envelope math, I am not a licensed statistician and it took me 4 tries to pass the damn queuing theory exam. Also I don't have all the data
Continue reading about What computer science can teach us about vaccine distribution
Semantically similar articles hand-picked by GPT-4
- Hire these interns
- Build better software with The Theory of Constraints
- Why you don't have time to advance your career
- Own the outcome, not the work
- How to lie with facts
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Senior Mindset Book
Get promoted, earn a bigger salary, work for top companiesLearn more
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️