How to Study After Work When You're Too Tired

Keep weekday evenings small and the deep work for the weekend. Build something instead of watching someone else build it. When a bad week hits, restart with the smallest step and don’t try to catch up.

Weekdays are small, weekends are deep

After nine hours at the office you still have time in the evening, but your head is spent. So plan your learning around your energy and let the clock decide less.

A weekday evening gets one small step that’s already defined before you sit down:

• run EXPLAIN ANALYZE on one slow query and write down what it tells you;
• add one index and measure the query again;
• read one incident report from your project and note what you’d have done;
• fix one comment from a code review.

Save the weekend for work that needs a fresh head, like designing a schema or redoing a submission that came back with red pen on it.

One habit makes weekday evenings much easier. Before you stop, write down the exact next step for tomorrow. Tomorrow then starts with doing, and you skip the twenty minutes of deciding what to do, which is where tired evenings usually die.

If you don’t know where to find problems worth a weekday evening, I wrote about that in No Learning in a Service Company? Where to Find Hard Problems.

Build, don’t watch

When you’re tired, a video keeps playing and you keep nodding along. Code doesn’t run until you’ve understood it, so building keeps you honest even at 10 pm.

Abhijit, a Sr. TSE at SAS India and one of my learners, wrote:

I was stuck reading and watching tutorials for a very long time. Vyson is building my confidence with hands-on assignments.

Md Sohel, a frontend developer at HireQuotient, put it more simply:

I really like this over videos because I never code watching videos.

If an evening does go into a tutorial, end it by typing out what you learned and running it. If you can’t run it, you haven’t learned it yet.

Bad weeks are part of it

You will have release weeks and on-call weeks, and weeks where family needs you. You’ll miss evenings.

Don’t try to make them up on Sunday. Stacking three missed evenings into one weekend turns learning into a debt you’ll dread paying. Pick up the smallest step from your note and carry on as if the gap never happened.

Vyson is self-paced for the same reason. A bad week at work doesn’t sink you, and doubt sessions get you unstuck, so the hours you do have don’t go into staring at an error.

Keep score every week

On Sunday night, write three lines: what you built, what broke and what you learned. It takes two minutes and shows you whether the week moved you forward, however many hours it took.

For a first weekday evening right now, try the 1 Million Row Challenge: a slow Postgres query in your browser and five minutes to fix it. Or play The Latency Game, which takes three minutes.

If you’re wondering whether all this is worth it at your stage, read Will AI Take My Job? A 2-Minute Test for Developers and Is It Too Late to Switch to a Product Company at 8 Years? When you’re ready for a full program with someone reviewing every submission, that’s Vyson.

What did you get done learn this week?