Bjartnes smiling







HTTP is my trusted friend and building block 🧱. I enjoy working on Web API design and implementation.

🧠I have been exploring DDD and applying it in my daily work for years. Running event-storming workshops is 🎉. I can help with technical leadership and architecture.

I💖F#. I am a .NET developer. Azure has been the main platform I have been building services on for the last six years.

Until July 2021 I am working with NRK TV where I have been in-house for the last six years. As a .NET backend-developer, tech-lead and architect I have had central roles in transforming NRK TV from a catch-up service to a modern streaming service. In close collaboration with product owners, designers, tech-leads, backend- and frontend developers I have worked on increasing our capacity to develop new functionality while improving robustness of the overall service.

I have now started as an independent consulant, formally known as siv. ing. Bjørn Einar Bjartnes AS, more informally as I am currently open for opportunities, so feel free to contact me at

I wrote this webpage for fun in Tailwind CSS as part of taking a CSS course. I am not a frontend developer by modern standards. Probably not by old standards either, but I enjoy working accross the stack and learning new things. If nothing else, building homepages like we did back in the days are fun. So be it that they are messy and a mix of content and techniques I wanted to try out for my own enjoyment. It is hosted on a static website in Azure using Azure CDNs. Way overkill.

More about me and my work

Bjartnes smiling
Bjørn Einar Bjartnes
Principal Engineer at NRK TV
View LinkedIn profile
On architecture, fifth post: How I got programming to an interface wrong

tl;dr API documentation is about defining an interface rather than documenting an implementation. We write API documentation by hand using OpenAPI and it is working well for us.

Workshop: Building and testing resilient services

Users' patience with services not working is gradually decreasing as the quality of services online is improving. With current trends of moving services to the cloud and building smaller and network-intensive services, meeting these expectations can be challenging for us developers. We want to be able to build services that we can run confidently despite partial failures and outages.