What it does have is a small, fervent user base: novelists, solo founders, therapists, a few burned-out engineers, and one very quiet Pulitzer-finalist historian who told me, off the record, “It’s the only thing that made me realize I was working 11 hours but only producing for 3. That hurt. Then it helped.” I tested Logtime 42 for 30 days. The first week felt tedious—manually logging every 42-minute block seemed like invented labor. By week two, something shifted. I started noticing my own cognitive contours. I learned that my first block (8:00–8:42) is useless for deep work. I learned that 2:00–2:42 PM is my dead zone, best reserved for admin. I learned that I lie to myself about how long meetings actually take.
Logtime’s founder, former systems architect Elena Morrison, stumbled on the number during a burnout recovery. She realized that modern productivity tools were optimized for planning the future, not witnessing the past. “We schedule in 30-minute blocks,” she told me, “but we live in 42-minute rhythms. It’s the natural horizon of deep attention before the mind needs a soft reset.”
It won’t save your life. But it might save your Tuesday afternoon. And sometimes, that’s the same thing. Available for macOS, Windows, and Linux (terminal-only version free for students). No mobile app. “Your phone is the enemy of duration,” says Morrison. She is not wrong. logtime 42
Tap a segment. A text field appears. You write: “Drafted Q3 report. Stuck on footnote 4 for 11 minutes.” Or: “Emails. Mostly spam. One reply to legal.” Or, gloriously: “Stared out window. Solved nothing. Felt fine.”
But the real surprise came on day 19. I had a terrible day—interruptions, tech failures, a pointless argument. I opened Logtime 42 expecting shame. Instead, I saw: “10:42–11:24: Firefighting. You stayed calm. That’s skill, not failure.” What it does have is a small, fervent
Her research, unpublished but quietly cited in a few niche HCI papers, suggests that 42 minutes is the mean attention arc for complex cognitive work—long enough to enter flow, short enough to resist exhaustion. After that, diminishing returns steepen. Logtime 42 doesn’t enforce this. It simply logs it. Open the app. You see a single, unadorned timeline—today’s date at the top, then a vertical strip divided into 42-minute segments. No colors. No notifications. No “insights.”
That’s it. You can edit retroactively. You can leave segments blank. The app does not judge, does not suggest, does not sync to Slack. I learned that my first block (8:00–8:42) is
Logtime 42 is not another time-tracking app. It is not a Pomodoro timer with gamified badges or an AI that scolds you for “low-focus hours.” It is, instead, a —a quiet, almost monastic interface that asks one radical question: What actually happened? The Origin of the Number The “42” is not a coincidence. In Douglas Adams’ The Hitchhiker’s Guide to the Galaxy , 42 is the answer to life, the universe, and everything—once you understand the question.
Not the existential kind. The smaller, more insidious panic: Where did the morning go? What was I doing at 10:17 AM? Why does my calendar look like a Jackson Pollock painting?