rulocode
Start free
Start free
Blog

A real day in the life of a software engineer (hour by hour)

September 8, 2026· 3 min read
The day-in-the-life you see on social media — pretty code, coffee, a mechanical keyboard in slow motion — looks nothing like the real thing. So I logged mine, hour by hour, exactly as it happened. An ordinary Monday.
The setup: a meeting on one screen, the code on the other
First things first: a good coffee to start the day with the best energy. It isn't content — it's that without it the next two hours don't exist. A couple of meetings with the team to make some architecture decisions. This is the part of the job nobody films because there's nothing to see: two people and a diagram, deciding something that will either hurt or save you six months later.
With the team: the part of the job that's talking, not typing
Here's the trick I apply: I record all my meetings. That lets me pull the action items straight out, without relying on my memory or on whatever I managed to scribble while talking. It's the cheapest, highest-return change I've made to how I work. It isn't a spectacular agent — it's just no longer losing agreements. Then I spent time preparing a freelance quote for a real estate company in Panama. Part of an engineer's day-to-day is, plainly, selling. Estimating scope, putting a number on it, defending it. Together with a teammate, planning the database migration for one of our chatbot projects. Planning, not executing: most of a migration's risk gets resolved before you touch anything.
Planning at the desk: the work before the work
Around four in the afternoon I stepped away from the computer for a bit. Time to move. A bit of upper body. Nothing heroic: just enough to remember what going to the gym feels like. Add up the blocks and you get something uncomfortable and true:
BlockWhat it actually was
9:02 a.m.Talking to people
9:51 a.m.Automating my own memory
10:18 a.m.Selling
1:09 p.m.Planning before executing
Writing code doesn't show up as its own block anywhere. Not because it doesn't exist, but because today it's spread across everything else — and because part of the work gets done by agents while I'm doing something else. That's the real change this year, and it doesn't show up in a keyboard timelapse. I'll be making more content about automation and agent engineering. If that's your thing, stick around.
Newsletter

One real automation, explained, every two weeks.

What I'm building with AI for my work and my students': the flow, the click-based tools and the hours it gives back. No news digests.
No spam. Unsubscribe in one click. If you're already in Week 0, you already get it.
Rulo, the rulocode robot, at the final station of his world