It’s a Thursday, it’s raining like crazy in Oslo and we’re just outside the city at a giant hotel complex designed specifically for offsites. We’re there as 4 teams (Omni, Peil, Sports and Upnext), all part of a singular team called NextGen. In theory we’re there to discuss the future of our shared team, and how we fit into the larger organization. There’s several nationalities between us, but our teams occupying Oslo, Stockholm, Gdansk and Krakow.

A week beforehand, my manager has come to ask me to arrange some social activities. We go visit the location, and I propose the…

This article is adapted from an internal article I wrote for

I sit at a table of relatives, eating Christmas leftovers. We are discussing the virtues of having unique facial expressions when playing chess. Buzz buzz. My phone interrupts — it’s a news app, called , telling me that a car bomb has just gone off in Cairo. I have no relatives, friends nor enemies currently dwelling in Cairo. Yet my thoughts are turned, painting the scene vividly in my head. The BBC says the same thing: JUST NOW! Live! Just nu! The news is screaming at me, this…

I’m not going to revolutionize the world with this post, but in the past few years I’ve run a lot of interviews. I’ve been on the receiving end a few times, too. I don’t have too much science behind different interviewing processes — it’s more an amalgamation of personal experience and books or blog posts.

At all points, if more than one person can attend the interview, that’s perfect. Ideally you want someone from the team to either be the interviewer or the shadow at all times. Dedicate time in each interview for candidate questions. …

This post is the first in a series of posts about me leaving my current job to become CTO of another company.

During my time at Schibsted, I got involved in various side projects where the were pretty low.

  • Bi-weekly developer talks
  • A project to calculate the environmental impact of our news sites
  • A pairing bot that creates matches for people to fetch coffee together
  • A book club
  • Interviews

There were other initiatives I was part of, but they required less input from me — the bus factor was considerably higher.


If you’re not familiar with Schibsted, here’s…

As developers, the best support we can get is often directly from the community. In some communities, they might prefer to use Stackoverflow or reddit. Stackoverflow has some decent guidelines on how to ask a question effectively. There’s also ways to ask questions effectively on chat clients like Slack. Here’s a couple of thoughts on something I saw happen recently.

Be specific

I once saw a developer ask “does anyone have experience with React and Redux?” in a channel filled with frontend developers. If you can’t guess, generally the answer to this question is “yes”. The problem with this question…

Imposter syndrome is a common occurrence in the world of programming. It’s not something that I have suffered from with relation to programming in a while, but I have many friends who do. I’ve tried to guide my interactions in such a way as to let the awesome people I’ve worked with feel awesome. This blog post is a write up of some the guidelines I follow to achieve that.

Technical Discussions

As someone who generally has strong opinions about some things, I find it very important to self-reflect on the way I communicate those opinions. Let’s examine some examples.

Another question I get asked a lot is “how can I participate better in open source?”.

Different projects need different input. Everything comes down to the fact that people run things in different ways. Some people like getting issues, others like getting pull requests. Some want documentation fixes, others would rather 3rd party documentation.

Understanding these differences can be crucial in how your interactions are perceived by the community.

The first calling point should always be about communication, not code. Reach out the project owner. See if they have a dedicated chat channel, or Twitter. If the project is big…

Lately I’ve been doing a lot of introspection. These blog posts are less about the technical side of what I do, and more about the human side.

One question I get asked often is “why do you contribute to open source?”. Open source to me is a full time hobby — I will usually spend at least an hour each day on open source activities. It’s not unusual for me to work on something after work until the early hours of the morning.

Let’s take a rough look at the different parts of open source contributions I do.

Learning from…

In my day job, one of my favourite activities is firefighting. Working together to figure out why something isn’t working and fix it. It requires the ability to dive into complex technical issues in a short amount of time. You may also need to have the overall vision of how a piece of your stack functions. But I’ve recently come to realise that it’s not just the technical side of things I enjoy, and that’s what this blog post is about.

During the , the Elm package servers were affected. Essentially, the domain nameserver records for were…


In this blog post, we’re going to explore what it takes to grow the ecosystem of a language. An ecosystem can be considered a combination of tooling, packages, and documentation. In particular, we’re going to look at approaches for helping a community grow an ecosystem without needing a single person to do everything. We’ll explore a range of packages and tools that exist in the Elm ecosystem, and discuss briefly how I helped them come about.

Every package and tool in this list is awesome and so are the authors, and there are many many more examples just like them…


Most of what I make are experiments. I promote both the ideas of getting things done and getting things done the right way.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store