Lukas Geyer
← All Writing

Building Calm Tools in a Loud Year

Notes on writing fiction at dawn, shipping iOS updates at night, and keeping software quiet.

There is an unexpected kinship between editing a short story and trimming an interface down to what a student actually needs two days before an exam.

In both disciplines, the first draft is almost always too eager to explain itself. In fiction, you over-describe the room because you don't yet trust the dialogue to carry the tension. In software, you add another badge, another chart, another configuration toggle because you don't yet trust the underlying schedule to make sense on its own.

When I started building Semestra, my goal was deliberately narrow: take the anxiety out of looking at a semester's worth of scattered .ics links, PDFs, and exam dates.[1] A student doesn't want a dashboard full of productivity theater. They want to know, when they open their phone on a rainy Tuesday afternoon, what needs attention today and whether they still have time to breathe.


Writing longform stories keeps my taste calibrated for software. Fiction teaches patience with pacing:

  1. Respect the reader's time. Never force someone through three introductory paragraphs—or three onboarding modals—before the real thing begins.
  2. Let whitespace do the heavy lifting. A pause between scenes gives weight to what came before it; generous margins around a timetable make a full week feel manageable.
  3. Cut anything that exists only to show off. If a paragraph or an animation draws attention to the author rather than the subject, it belongs in the draft folder.

Most evenings I spend an hour fixing layout edge cases, refining Live Activities, or improving how Semestra recalculates study blocks after a canceled lecture. Most mornings I try to write a page that has nothing to do with screens at all. Keeping both practices under one roof feels less like a split personality and more like two halves of the same attention.