Human beings and computers alike share the challenge of how to get as much done as possible in a limited time. Over the last fifty or so years, computer scientists have learned a lot of good strategies for managing time effectively — and they have a lot of experience with what can go wrong. Brian Christian shares how we can use some of these insights to help make the most of our own lives.
Lesson by Brian Christian, animation by Adriatic Animation.
Thank you so much to our patrons for your support! Without you this video would not be possible! Jordan Tang, Christopher Jimenez, Juan, Tracey Tobkin, Sid, emily lam, Kathryn J Hammond, Elliot Poulin, Noel Situ, Oyuntsengel Tseyen-Oidov, Latora Slydell, Sydney Evans, Victor E Karhel, Bernardo Paulo, Eysteinn Guðnason, Olivier Brunel, Andrea Feliz, Natalia Rico, Josh Engel, Bárbara Nazaré, Gustavo Mendoza, Zhexi Shan, Hugo Legorreta, Steph, PnDAA, Marcel Trompeter-Petrovic, Sandra Tersluisen, Ellen Spertus, Fabian Amels, sammie goh, Mattia Veltri, Quentin Le Menez, Sarabeth Knobel, Yuh Saito, and Joris Debonnet.
Content
13.962 -> In the summer of 1997,
16.132 -> NASA's Pathfinder spacecraft landed
on the surface of Mars,
20.611 -> and began transmitting incredible,
iconic images back to Earth.
25.241 -> But several days in,
something went terribly wrong.
28.48 -> The transmissions stopped.
30.662 -> Pathfinder was, in effect,
procrastinating:
34.232 -> keeping itself fully occupied
but failing to do its most important work.
39.691 -> What was going on?
40.901 -> There was a bug, it turned out,
in its scheduler.
44.933 -> Every operating system has something
called the scheduler
48.203 -> that tells the CPU how long
to work on each task before switching,
52.544 -> and what to switch to.
54.414 -> Done right, computers move so fluidly
between their various responsibilities,
58.863 -> they give the illusion
of doing everything simultaneously.
62.343 -> But we all know what happens
when things go wrong.
66.446 -> This should give us, if nothing else,
some measure of consolation.
70.462 -> Even computers get overwhelmed sometimes.
73.555 -> Maybe learning about the computer science
of scheduling
76.636 -> can give us some ideas about our own
human struggles with time.
81.025 -> One of the first insights is that all
the time you spend prioritizing your work
85.644 -> is time you aren't spending doing it.
88.775 -> For instance, let's say when you check
your inbox, you scan all the messages,
93.074 -> choosing which is the most important.
95.374 -> Once you've dealt with that one,
you repeat.
97.703 -> Seems sensible,
but there's a problem here.
100.052 -> This is what's known
as a quadratic-time algorithm.
103.925 -> With an inbox that's twice as
full, these passes will take twice as long
109.387 -> and you'll need to do
twice as many of them!
111.875 -> This means four times the work.
115.085 -> The programmers
of the operating system Linux
117.615 -> encountered a similar problem in 2003.
121.273 -> Linux would rank every single
one of its tasks in order of importance,
125.816 -> and sometimes spent more time
ranking tasks than doing them.
130.276 -> The programmers’ counterintuitive solution
was to replace this full ranking
134.606 -> with a limited number
of priority “buckets.”
138.107 -> The system was less precise
about what to do next
141.287 -> but more than made up for it
by spending more time making progress.
146.191 -> So with your emails, insisting on always
doing the very most important thing first
150.909 -> could lead to a meltdown.
152.89 -> Waking up to an inbox three times fuller
than normal
155.783 -> could take nine times longer to clear.
158.967 -> You’d be better off replying
in chronological order, or even at random!
163.718 -> Surprisingly, sometimes giving up
on doing things in the perfect order
167.886 -> may be the key to getting them done.
171.037 -> Another insight that emerges
from computer scheduling
173.866 -> has to do with one of the most prevalent
features of modern life: interruptions.
178.638 -> When a computer goes
from one task to another,
181.509 -> it has to do what's called
a context switch,
184.696 -> bookmarking its place in one task,
187.029 -> moving old data out of its memory
and new data in.
191.448 -> Each of these actions comes at a cost.
194.028 -> The insight here is that there’s
a fundamental tradeoff
196.858 -> between productivity and responsiveness.
200.029 -> Getting serious work done
means minimizing context switches.
203.83 -> But being responsive means reacting
anytime something comes up.
208.549 -> These two principles
are fundamentally in tension.
212.401 -> Recognizing this tension allows us
214.899 -> to decide where
we want to strike that balance.
217.88 -> The obvious solution
is to minimize interruptions.
221.639 -> The less obvious one is to group them.
225.242 -> If no notification
or email requires a response
228.76 -> more urgently than once an hour, say,
232.011 -> then that’s exactly how often
you should check them. No more.
236.59 -> In computer science, this idea goes by
the name of interrupt coalescing.
242.029 -> Rather than dealing with
things as they come up –
244.631 -> Oh, the mouse was moved?
245.981 -> A key was pressed?
247.071 -> More of that file downloaded? –
248.792 -> the system groups these
interruptions together
251.549 -> based on how long they can afford to wait.
254.721 -> In 2013, interrupt coalescing
257.648 -> triggered a massive improvement
in laptop battery life.
261.942 -> This is because deferring interruptions
lets a system check everything at once,
266.753 -> then quickly re-enter a low-power state.
270.623 -> As with computers, so it is with us.
273.212 -> Perhaps adopting a similar approach
275.641 -> might allow us users
to reclaim our own attention,
279.471 -> and give us back one of the things
that feels so rare in modern life: rest.
