~/about/editor.yml
Owen Calder, editor of Puffin Notes
name: Owen Calder
role: editor
beat: [linux, cloud, costs]
favourite_command: du -sh *
pager_duty: retired, mostly

$ whoami

We write about the boring parts.
On purpose.

I’m Owen Calder. For most of my working life, my job has been the part of software nobody demos: patching servers at odd hours, restoring backups that should have worked, and explaining to someone why the cloud bill doubled.

Puffin Notes is where I write that knowledge down. It’s for people who run open-source software for real — and who’d like to understand their infrastructure, and what it costs, a little better than they did yesterday.

// the short version

Installing software is a weekend. Owning it is a commitment.

There’s no shortage of tutorials that get you from zero to “it runs”. There are far fewer that help with month eighteen: the security update that breaks a dependency, the database that has quietly outgrown its disk, the managed service whose price changed while nobody was looking.

That’s the territory Puffin Notes covers. We look at open-source projects as things you’ll live with, not just things you’ll try. We compare where to run them, and we take the money seriously — hosting, egress, support contracts, cloud credits, commitments — because in our experience that’s what decides whether a stack survives.

It’s a small operation. One editor, a handful of occasional contributors, and a strong preference for showing the numbers over describing them.

$ cat .github/workflows/publish.yml

How a post gets made.

step 01

Start with a real question

Most posts begin with something a reader, or we, actually got stuck on.

step 02

Run the numbers

If there’s a cost or a performance claim, we work it out and show the maths.

step 03

Try it ourselves

Where we can, we install it, break it and fix it before we write about it.

step 04

Name the sources

Official docs, pricing pages and changelogs, so you can check our work.

step 05

Update, don’t delete

Prices and versions change. We revise posts and note what changed and when.

$ cat /etc/puffin/house-rules.conf

Three house rules.

show_numbers = true

Numbers, or it didn’t happen.

“Cheaper”, “faster” and “more efficient” mean nothing without figures. When we compare options, we put the costs and assumptions in a table so you can swap in your own.

vendor_votes = 0

No vendor gets a vote.

We don’t sell hosting, software or consulting, and nobody pays for coverage. If a post links to a product or service, it’s because we think it helps, and any commercial relationship is disclosed in that post.

admit_mistakes = always

Corrections are public.

If we get something wrong, we fix it in the post and say what changed. Readers who spot an error are doing us a favour, and we treat it that way.

# a note on the name

This domain has history. We’re not part of it.

The thepuffingroup.com domain was once home to an early open-source software company, which was acquired around the turn of the millennium. Its open-source spirit is part of why we chose this domain for a publication about running software.

Puffin Notes is a new, independent publication under unrelated ownership. We have no connection to the original company, its founders, its acquirer or its successors, and nothing here is written by or on behalf of any of them.

$ gh issue create

Get in touch. Pick a template.

bug

Found a mistake?

A wrong number, an outdated price, a command that no longer works. Tell us and we’ll fix it — with credit, if you want it.

feature request

Want us to cover something?

A project you’re evaluating, a line on your invoice you can’t explain, a migration you’re dreading. The best topics come from readers.

pull request

Want to contribute?

If you’ve run something interesting in production and learned the hard way, we’d like to hear it. Practitioner write-ups are always welcome.

Contact Us

We'd love to hear from you