./work
Six projects, five of them still maintained.
Libraries, command-line tools and one piece of client work. Each has a page with what it does, how it went and how to try it.

Library
2025
Plumbline
Reads an API description and gives you a fully typed client, with retries and timeouts you can actually read.
2.6M installs a month, 38 kB, no dependencies

Sync engine
2024
Quire
A local-first sync engine for notes and small documents. Works offline, merges without asking you to resolve conflicts.
214 operations merged in 38 ms, 11 MB of memory

Command-line tool
2024
Tern
Feature flags from your terminal. A tiny server, a single binary and a flag list you can read out loud.
One 6 MB binary, 1,900 stars

Charts
2023
Lantern
Accessible chart components for React. Every chart ships with a table view, keyboard controls and a text summary.
12 chart types, 22 kB, WCAG AA

Client work
2022
Harbor Desk
A support console for a shipping co-operative: berth changes, customs forms and crane slots in one queue.
Tickets handled 31% faster, 14 staff, 6 ports

Build tool
2021
Dovetail
Turns one file of design tokens into CSS, Swift, Kotlin and JSON, so design and code agree by construction.
1.1M installs a month, 4 output formats
01 / what I take on
Three kinds of work I say yes to.
01
Libraries and tools
A small, well-tested package your team can depend on, with docs a stranger can follow.
02
Internal apps
The console, queue or dashboard your staff use all day. Built to be boring and fast.
03
Reviews and rescues
A week reading your code and telling you plainly what is worth keeping.
02 / how a project runs
Small steps, written down.
You will always know what has happened and what happens next.
Read
I read the code, the tests and the last year of history. You get a two-page summary of what I found.
Smallest useful thing
One change that proves the approach, behind a flag, with a test.
Build
Small pull requests every day or two. A short note at the end of each week.
Hand over
Docs, a runbook and a call with whoever looks after it next.
Iri’s pull requests read like short essays. You always know why a change exists before you read the code.
Marta Solheim
Engineering manager, Fjordline Systems
We asked for a support console and got one that our night shift stopped complaining about. That has never happened before.
Joakim Reinsnes
Operations lead, a port co-operative
03 / mail iri