Notes: Why we're writing this down

A little while ago we wrote about why we build the software we build — that before a single line of code, we ask what kind of software we want our name attached to. That post wasn't a one-off. It was the first entry in something we're calling Notes.

Notes is where we think out loud. The decisions behind a product, the tradeoffs we argued over, the things we got wrong and fixed, the standards we hold web design and custom software to. Not marketing, not changelogs — the reasoning underneath the work. If "Why we build the software we build" told you what we care about, Notes is where we'll keep showing you how that plays out, one decision at a time.

What Notes is

Notes is a home for the thinking behind the building. Most companies show you the finished thing: the shipped feature, the polished site, the case study with the numbers rounded up. We'd rather show you the part before that — why we chose one approach over three others, what we were worried about, and whether that worry turned out to matter.

It's reasoning, not announcements. Some entries will be short. Some will be one decision examined closely. None of them will be a press release.

Why now

The first post opened a thread worth pulling on. When we wrote about picking ideas, the response we kept hearing wasn't "tell us more about the products" — it was "tell us more about how you think."

That's fair, because taste is hard to prove on a services page. A list of what we offer says nothing about the judgment we bring to it. Writing does. So Notes exists to make the judgment visible, in the only way judgment ever really shows: through specific decisions, explained honestly.

What you'll find here

• Product decisions — why a feature exists, why another one didn't make the cut, and what we learned once real people used it.
• Craft standards — the same stance that drives our web design work: no templates, a limited number of projects, full attention on each one. We'll show what that looks like in practice.
• Postmortems — the things we got wrong, what breaking them taught us, and what we changed.
• Opinions on tools and tech — the stack choices, the tradeoffs, and the occasional strong take we're willing to defend.

How we pick what to write about

The same way we pick what to build. Before we publish, we ask whether the piece reflects the kind of software — and the kind of company — we want the Acromia name associated with. If it doesn't clear that bar, it doesn't go up. A note has to earn its place the same way a product does.

The standard we're holding ourselves to

Honest, specific, and occasionally wrong in public. We'd rather write one thing we actually believe than ten things that sound safe. That means naming the tradeoff instead of hiding it, and telling you when a decision didn't age well. It's the craft-first identity from the first post, applied to how we write instead of what we ship.

Where to start

If you haven't read it yet, start with "Why we build the software we build" — it's the foundation for everything here. After that, keep an eye on this space. We've got the next few entries lined up, and they get more specific from here.