Quiet software doesn’t perform for you. It doesn’t celebrate when you complete a task you didn’t want to do in the first place. It doesn’t interrupt to ask how it’s doing. It sits still until you reach for it, does the thing, and gets out of the way. The experience afterward is strange and rare: you remember the work, not the tool.

Dieter Rams said good design is as little design as possible, and the line gets quoted so often it’s become furniture. But the second half of the sentence is the part that matters: because it concentrates on the essential aspects. Less isn’t the goal. Less is what’s left over when you refuse to ship anything that doesn’t serve the person using it.

attention is the budget

Every interface spends its user’s attention, and most spend it like it’s free. A badge here, a nudge there, a “we’ve updated our look!” modal on a Tuesday. Each one is small. Together they’re a tax on the exact resource the software was supposed to protect — the user’s ability to think about their own work.

The economics explain it. Attention captured is revenue measured, so the loudest patterns win A/B tests even when they lose users’ trust. Nobody ships a growth chart labeled “interruptions people forgave us for.” But forgiveness runs out silently, and when it does, people don’t file a complaint. They just leave, and they can’t quite say why.

Quiet software inverts the budget. It treats every demand on attention as a cost to be justified, the way an engineer treats memory or latency. Does this notification serve the reader, or the metric? Does this animation communicate state, or decorate a delay? Run that audit honestly and most interfaces lose half their weight — and nothing of value goes with it.

boring on purpose

The highest compliment I can pay a tool is that it’s boring in a good way. The file syncs. The text saves. The page loads before you notice it loading. Boring means the surprises are gone, and surprise is exactly what you don’t want from infrastructure.

Getting to boring is brutally hard work. It means saying no to features that would demo well. It means spending a week on a failure case one user in a thousand will hit. It means the craftsmanship is invisible almost by definition — effort you can only detect by noticing that nothing ever goes wrong.

That’s why quiet is a discipline, not an aesthetic. You can’t add quiet at the end the way you’d add a coat of paint. It has to be the default answer to every question along the way: no, unless it earns its place.

what this costs

I want to be honest about the trade. Quiet software is harder to market, because restraint doesn’t screenshot. It grows slower, because it refuses the loops that make growth charts steep. Building it is a bet that respect compounds — that the person you didn’t interrupt today is the person who’s still with you in ten years, and who brought a friend.

I think the bet is right. The tools that have lasted decades — the ones people defend with real feeling — are almost all quiet ones. Nobody loves a dashboard. People love the pen that always writes.

This blog is a small attempt to practice what it praises: text, set carefully, served fast, asking nothing of you but your reading. If you noticed the design, I have work to do. If you didn’t — good. That was the point.

Text

Body text is set on a fluid scale — 17px on phones easing to 19px on large screens — with a measure of about 66 characters, which is where long-form reading is most comfortable. Links are always underlined, emphasis comes in italic and bold, and inline code looks like const reader = "first".

Straight quotes become “smart” quotes automatically, dashes work — like this — and footnotes land at the bottom of the page with a way back.¹

Headings get anchors

Hover any heading (or focus it with the keyboard) and a quiet # appears — a shareable deep link to that section, generated at build time with no JavaScript.

Down to level four

Level-four headings share the body size and rely on weight alone. Deeper nesting than this is usually a sign the post wants to be two posts.

Lists

An unordered list:

• everything it needs
• nothing it doesn’t
• set in type that gets out of the way

And an ordered one:

1. function — does it work?
2. convenience — does it remove friction?
3. aesthetics — does it create a meaningful experience?

A table

Tables get minimal horizontal rules and tabular figures, and scroll sideways on small screens instead of breaking the page.

Code

Three languages, one restrained palette per theme. Every block gets a copy button (keyboard-operable, announces “copied”) — unless JavaScript is off, in which case the button simply doesn’t exist.

// counts words the way the reading-time meta line does
function readingTime(text, wpm = 220) {
  const words = text.trim().split(/\s+/).length;
  return Math.max(1, Math.ceil(words / wpm));
}

/* the entire theming system is custom properties */
:root {
  --bg: oklch(98% 0.004 85);
  --fg: oklch(22% 0.005 85);
  --accent: oklch(52% 0.1 250);
}

# preview locally without installing anything (see README for Codespaces)
bundle exec jekyll serve --livereload

An image, with a caption

Images declare their dimensions so the page never shifts while loading, and lazy-load below the fold.

A quote

Good design is as little design as possible. Less, but better — because it concentrates on the essential aspects, and the products are not burdened with non-essentials.

A horizontal rule, for when a section break is quieter than a heading:

That’s everything. If it isn’t on this page, the template doesn’t style it — and that’s on purpose.²

There are no trackers here, no cookie banner, no comment counters asking to be looked at. Just text, set carefully, that loads fast and reads well on anything with a screen.

If you’re reading this on your own fork: welcome. Delete the demo posts in _posts/, edit _config.yml, and write. That’s the whole workflow.