Most productivity advice fails tech people for one reason: it treats all work as the same shape. It isn’t. Managing your time well starts with knowing which kind of time you’re actually spending.
Manager time vs. builder time
Paul Graham split it well. Managers live in hour-long blocks, hopping between meetings and decisions. Builders need long, uninterrupted stretches to get into flow.
A tech lead can survive a morning of back-to-back meetings and still make progress. A developer trying to solve a hard problem in the same conditions gets nothing done. Every interruption costs more than the interruption itself. It costs the ramp-up time to get back to where you were.
Know which mode your work requires today, and protect your calendar accordingly. If your role is hybrid, batch your meetings on specific days and keep the rest clear.
AI agents just made every engineer a manager
Agents shift this whole framework. A developer who used to spend the day in pure builder time is now running two or three agents on separate tasks, checking their plans, redirecting them, catching what they got wrong. That’s not building anymore. That’s managing.
The tempting move is to push it further. If three agents work, why not ten? Spin them all up, review the output at the end. I don’t buy it. Context switching has a real cost for humans, and reviewing an agent’s work is still a context switch. Every task you delegate needs your attention at some point, to check the plan, catch the mistakes, decide what “done” actually means. That attention doesn’t scale just because the labor did.
I’d cap it at 2-3 tasks in parallel per person. Past that you’re not managing, you’re skimming, and skimming is how bad code and bad decisions get through. A manager running 15 direct reports without ever checking in isn’t scaling, they’re gambling. Same problem, new tool.
Treat your agents like reports, not extra CPU cores. Give each one a clear scope, check in on schedule, and don’t confuse “I delegated it” with “it’s handled.”
Build deep work blocks
Deep, focused work is a real advantage now precisely because so few people protect it. A few ways to build it in:
Block 2-4 hour chunks explicitly labeled for deep work
Build a short pre-work ritual that signals to your brain it’s time to focus
Kill notifications
Tell people you’re unavailable during these blocks
Set one clear goal per session, not five
A machine learning engineer might claim Monday and Wednesday mornings for model work. A writer might claim Friday for drafting. The point isn’t the schedule, it’s the claim.
Cut the noise
Digital minimalism means using only the tools that add real value, and cutting the rest. Concretely:
Do a 30-day digital declutter. Drop every optional tool, then bring back only what actually earned its place
Audit what’s on your phone and your desktop. Does it help, or does it just pull your attention?
Set tech-free times and spaces: no phone at meals, none in the bedroom
Batch email and messages instead of checking continuously
Removing Slack from your phone stops work from bleeding into your evening. Checking email three times a day instead of thirty often makes you more responsive, not less, because you reply with a clear head instead of reflexively.
Energy is the real constraint
Time management without energy management doesn’t work. Time is fixed. Energy isn’t, you can build and protect it.
Know your chronotype. Put your hardest cognitive work in your peak hours.
Protect physical energy: sleep, movement, food, water. A short walk beats a second coffee.
Manage mental load with brief resets between tasks, not just at the end of the day.
Build real relationships and find meaning in the work. That’s fuel too.
Stay connected to why you’re doing any of this. Purpose is what gets you through the bad weeks.
A QA engineer might be sharp on detail in the morning and useless at it by 2pm. That’s not a discipline problem, that’s a scheduling problem. Put the test case work in the morning and the collaboration in the afternoon.
Priorities, tools, routine
Three more things worth doing, briefly:
Sort tasks by urgency and importance before you start your day, not after. A data analyst prepping for a key presentation beats organizing old files every time, but only if you decided that on purpose.
Use tools that fit how you actually work, not the ones everyone recommends. Trello, a Pomodoro timer, whatever. The tool matters less than actually using one. My personal favorite is just a document listing the next 1-2 things I’ll be working on on a notepad.
Build a routine that reduces decisions. Mornings for creative work, afternoons for meetings, whatever your version is. Consistency saves the willpower you’d otherwise burn deciding what to do next.
Say no, and leave room for chaos
Every yes is a no to something else. Decline what doesn’t serve your priorities and you protect the time for what does.
At the same time, leave buffer in your schedule. Tech is unpredictable. A cybersecurity analyst who has zero slack for incident response isn’t managing time well, they’re gambling.
Structure gives you a plan. Flexibility keeps the plan from breaking the first time something goes wrong.
Start with one thing: protect your next deep work block, and notice when your energy is actually highest today. That’s the whole system.