Hi, I'm a full-stack developer. I spent years writing optimized code while letting my life outside the IDE stay completely unoptimized and chaotic. I started this blog because my digital life was actively breaking my physical life — and I could no longer pretend the two were separate systems.
The contradiction was hard to ignore once I saw it. At work I refused to ship anything I hadn't measured. I profiled before optimizing, I set budgets, I wrote tests, I reviewed every change. Then I closed the laptop and ran the rest of my life on vibes, autopilot, and whatever the algorithm served me at 11pm.
The week the numbers showed up
It started with a screen time report I opened by accident: 7 hours and 42 minutes of daily average, and a third of it on an app I could not have named a single thing I learned from. My first instinct was the honest engineer's instinct — that number is probably wrong, let me instrument it properly.
So I did. I logged five days in 30-minute buckets, the same way I would trace a slow request. The report was, if anything, generous.
What the trace actually showed wasn't a volume problem. It was a fragmentation problem. I had plenty of hours. I had almost no uninterrupted ones. My day was a scheduler thrashing between contexts and paying a full reload cost on every switch, and I had been blaming the workload instead of the schedule.
What I tried, and what actually worked
I did all the obvious things first, and most of them failed:
- Apps that block apps. I knew the passcode. A runtime check you control is not a check.
- Digital detox weekends. They worked for exactly as long as they lasted. Monday reset everything.
- More willpower. The classic move of blaming the operator instead of the system.
What eventually worked was unglamorous, and it looked like engineering:
- Measure first. A real time audit, repeated, with the numbers compared week over week.
- Fix the schedule, not the person. Batch by context. Protect block boundaries. Stop optimizing for total hours.
- Design the environment. Phone charging in another room beats any app that asks permission to stop you.
- Ship one change at a time. Then re-measure to see whether it moved anything. Most changes don't.
Eighteen months in, my screen time is a little under two hours a day and — far more importantly — my deep work blocks went from roughly one clean block a week to eight or nine.
Why this blog exists
There is a great deal of writing about digital minimalism, and much of it is either monastic or moralizing. Delete everything. Buy a dumbphone. Feel bad about your dopamine.
None of that is a system. A system has inputs, measurements, and a feedback loop you can actually run on a Tuesday when you are tired.
So everything here follows the same shape: a mechanism explained plainly, a way to measure whether it is working for you, and an honest account of where it failed for me. I publish the failures because a framework that only reports its wins is a framework you cannot trust.
What you'll find here
- Time auditing — profiling your week the way you would profile a service.
- Digital detox — friction design and shutdown protocols that survive bad days.
- Frameworks — the mental models, mostly borrowed from systems work, that carry the most weight.
I still use a laptop for ten hours a day. I am not writing from a cabin, and the goal was never purity. The goal is that the time is chosen rather than defaulted into.
If that sounds like the problem you are actually having, start with the free Notion framework. It is the same workspace I use every week.