Writing things down

Placeholder post. This text stands in for a real first post. Replace it, keep the front matter shape.

Most of what I learn at work evaporates. A bug gets fixed, a decision gets made, a library gets swapped, and three months later nobody — including me — remembers why. This site is an attempt to slow that down.

A notebook, not a showcase

A portfolio is a shop window: everything polished, nothing in progress. A notebook is the opposite. It has crossed-out lines, half-finished drawings and the occasional coffee ring. I would rather publish the notebook.

Why not a portfolio

A portfolio only shows the finished thing, and the finished thing is the least useful part to anyone trying to learn from it.

What a notebook keeps

The dead ends, the questions I asked too late, and the one sentence that finally made it click.

That means the posts here will be uneven. Some will be short notes about a single command; some will be longer essays about how a system grew. They will all be dated, and they will all say what I believed at the time.

What to expect

• Notes on building small, durable web software.
• Write-ups of things that took longer than they should have.
• Occasionally, a post in Italian only, when the subject is local.

The rules I set myself

Write it while it’s warm

1. Write the post the week the thing happens, not a year later.
2. Prefer one clear example to three vague ones.
3. Correct mistakes in place and say so at the bottom.

Keep it findable

Every post has a date, a few topics and an excerpt that says what it is about in one line. Placeholder text, to be replaced.

Following along

If any of this is useful to you, the RSS feed is the most reliable way to follow along.