Have you ever wanted to be productive after work but are constantly exhausted? That was me until I discovered these few things that helped me stop wasting my evenings...
Two years ago, I was stuck in a cycle that might sound familiar: arrive home exhausted, collapse on the couch for "just one episode," then get up five hours later wondering where my evening went. The side project remained untouched. The new skill stayed unlearned. The hobby collected dust.
What changed wasn't discovering some magical productivity hack or joining the 5 AM club. It was understanding that productivity is fundamentally a systems problem - and like any engineering challenge, it requires the right approach.
Here's what most productivity advice gets wrong: your brain isn't a monolithic resource that's either "on" or "off." It's more like a network of subsystems that exhaust and recover independently.
Research backs this up. When your cognitive subsystem is exhausted from debugging code all day, your physical subsystem might be perfectly fresh. The key insight? You can reset your overall energy by switching subsystems.
In practice:
I discovered this accidentally when I arrived home at 6 PM and forced myself to hit the treadmill. The difference was immediate - I actually wanted to work on my projects afterward.
Tech loves its early morning standup culture, but here's the uncomfortable truth: chronotypes are genetically determined. Forcing yourself to be productive at 5 AM when you're naturally wired for evenings is like trying to use a diesel engine with regular gasoline: you might get some movement, but you're lacking efficiency and hurting your long-term performance. It's important to recognize your chronotype:
Once you know this, don't fight it. Use your evenings for deep work and mornings for routine tasks if you're a night owl. The productivity gains (💪) from working with your natural energy cycles far outweigh any perceived benefits of forcing yourself into an unnatural schedule.
As engineers, we understand system reliability. We build in redundancy, implement circuit breakers, and plan for failure modes. Yet when it comes to personal productivity, we often run ourselves like a hastily bootstrapped service with no rate limiting.
I learned this the hard way: 4 hours of sleep, 4+ coffees, and the inevitable crashes that left me unproductive for spurts. The biological reality is that our bodies are not designed to operate at peak efficiency without cycles of rest. Disrupting the rest phase causes system deterioration.
The solution is what I call the "One Other Day" rule. Nerd alert:
if (exhausted && days_off_this_week < 2) {
take_evening_off = true
} else if (took_yesterday_off) {
must_be_productive_today = true
}Take a day or two off per week to not be productive in the evening. Allow yourself to recharge. The critical constraint: never take two consecutive days off. This prevents the habit formation that makes restarting difficult while still providing necessary recovery time.
Here's something that rarely appears in the sphere of tech productivity discussions but might be your biggest limiting factor: nutrition is your fuel quality.
For years, I optimized for food deals and convenience — $5.99 pizzas, app coupons, whatever was cheap and filling. Unsurprisingly, my day-to-day came with frequent fatigue, brain fog, and zero post-work motivation.
The data is clear: deficiencies in B vitamins, iron, and Omega-3s directly impact cognitive function and energy levels. Nutrition and fitness can be a sneakily effective way to improve your engineering efficacy.
It doesn't have to be complicated or expensive either. Start with the basics, avoid processed foods, eat whole foods. Pick a few primary supplements that cover common deficiencies and you're golden:
And lastly, in my opinion everyone should be taking creatine.
We understand parallel processing. Why run tasks sequentially when you can run them in parallel? We can apply the same principle to personal time management through task stacking. Don't try to stack everything, of course. Multitasking can be counterproductive and actually take you out of that 'flow state'.
Valid parallel operations:
Invalid (blocking) operations:
This isn't multitasking in the traditional sense—it's about pairing complementary activities that use different cognitive resources.
Every Sunday, I create a backlog for the week. I build a prioritized queue of work that eliminates daily decision-making overhead using a few tools. My To-Do list / planning drivers consist of a combo of Apple Notes, Things 3, and iCal.
I'll go into details about my specific workflow in a separate article. It is largely based on principles from David Allen's Getting Things Done (GTD) methodology & Cal Newport's Deep Work.
Importantly, find a system that works for you and aim for the task equivalent of 'inbox zero'. This means that you should aim to complete all tasks in your planned backlog within the week. Prioritize new tasks daily based on their urgency.
Don't try to implement everything at once. That's a recipe for failure. Instead, apply the minimum effective dose principle. Here's my suggestion for starting better post-work habits:
Evening productivity isn't simply willpower or motivation. Your body is hardware with specific operational parameters. Your energy is a resource with distinct recovery patterns. Your time is finite but can be parallelized.
Stop treating productivity advice like magic formulas. Start treating it like engineering: experiment, measure, iterate, and optimize based on what works for you!