Skip to content
odinns.dk
Open CV

About

I like useful systems and suspiciously specific words.

I am Odinn. I build software, write small odd things, and spend a lot of time trying to make messy systems less impressed with themselves.

Laravel AI workflows Invented words Garden engineering

The CV has the chronology. This page is the softer furniture: what I keep noticing, what I keep fixing, and why half my projects begin as annoyance with a thing that should have been clearer.

Portrait of Odinn Adalsteinsson

Based

Ringsted / Copenhagen orbit

Usually doing

Making something clearer than it was yesterday

Bias

Less fog. More working thing.

Temperament

The shape of it.

I like the ugly bits

Not because they are glamorous. They are not. But the awkward parts tell the truth first: mismatched assumptions, brittle flows, missing ownership, tiny lies in naming.

I collect words

Some states deserve names. Duhsome. Prunt. Exhausterwhelmulated. A good word can turn a vague irritation into something you can point at, laugh at, then fix.

I make tools when annoyed

The pattern is embarrassingly consistent: notice friction, complain internally for a while, then build the small thing that makes the friction shut up.

Outside the CV

Still mostly the same person.

Things that keep recurring

  • Making practical little systems for things that were previously just floating around.
  • Getting weirdly invested in whether a sentence is true, not just shiny.
  • Turning notes, scripts, half-plans, and side projects into something with handles.
  • Being unable to leave a bad workflow alone once it starts blinking in my peripheral vision.

Elsewhere

The non-keyboard parts.

I live in Ringsted, orbit Copenhagen, and keep dragging the same brain into other rooms: the garden, writing, cooking, home projects, small rituals, unfinished lists with suspicious ambition.

Operating system

How I tend to move through work.

Make it graspable

I dislike systems that require folklore to operate. If the thing matters, it should have names, boundaries, tests, docs, or at least enough shape that the next person is not decoding smoke.

Keep the human in the loop

AI is useful. So are checklists, tests, second opinions, walks, and noticing when a plan has turned into option soup. The trick is not worshipping any of them.

Contact

If the backend is drifting, that is usually my sort of mess.

Hiring, consulting, rescue missions

If you need someone to steady a backend, sort out delivery chaos, or build the thing that keeps biting the team, email is the cleanest route.

Email me

If you want the receipts first

The CV has the career chronology. GitHub has the visible experiments. LinkedIn exists because the world insists on certain rituals.