./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.

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.

Week 1

Week 1

Read

I read the code, the tests and the last year of history. You get a two-page summary of what I found.

Week 2

Week 2

Smallest useful thing

One change that proves the approach, behind a flag, with a test.

Weeks 3 to 5

Weeks 3 to 5

Build

Small pull requests every day or two. A short note at the end of each week.

Final week

Final 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

Got a project in mind? Tell me what it should do.

$ subscribe --notes

New notes by email, when there are any. About one a month.

Iri Halvorsen

Software engineer

Bergen, Norway

Open to work from January 2027

Colophon

Set in Geist and Geist Mono

Built in Framer

No tracking, no cookie banner

buildlog_

© 2026 Iri Halvorsen. All demo work is fictional.

exit 0

Create a free website with Framer, the website builder loved by startups, designers and agencies.