
Developer Experience. Documentation. Community.
Hi, I’m Marcus, a Software Engineer turned educator and Developer Experience advocate, with more than a decade of experience building software and educating developers.
Trust is something you build.
Privacy is an engineering responsibility. Transparency is a product decision. Developers deserve a seat at the table.
Software companies are stewards of the data entrusted to them. That responsibility should shape the products we build, not just the privacy policies we publish. People should have control over their own data. They should be able to understand how it’s used, move it elsewhere, and choose tools that work on their terms. Innovation shouldn’t require people to surrender that control.
Privacy engineering, local AI, and self-hosting can help us build ambitious technology without compromising user autonomy. Trust also depends on how we build. Developer-first companies should invite developers into product decisions and be honest about trade-offs, mistakes, and challenges.
Documentation, education, and community aren’t marketing channels. They’re part of the product and help us improve it together. Developer Relations starts with respect for developers, for users, and for the data they entrust to us.
Data Protection & Privacy
View all

Westin's four states of privacy

Deploy Fides to Kubernetes

Privacy code scanning with Privado

Understanding privacy risk with k-anonymity and l-diversity

Get started with Fides
Professional highlights
The story so far.
My career started as a research assistant in the early 2010s, where I worked on migrating computation-heavy workloads for photo-realistic computer graphics to the GPU. That would eventually land me a job developing SDKs for rendering GIS applications at Saab Aerosystems.
Two years later, I joined a small Stockholm-based consultancy called Citerus, where I helped build cloud-native applications.
In 2016, I joined the data team at Bonnier Broadcasting to consolidate both streaming and batch data across the organization. This was right before GDPR went into effect, so this involved migrating existing workflows to comply with the new regulations.
After two years, I went back to consulting teams—focused on data infrastructure and DevOps practices.
At this point, I had also been co-organizing the local Go meetups in Stockholm, where I discovered my passion for working with developer communities. I kept reading about this thing called Developer Relations, and loved the idea of integrating more of my skillsets into work.
In 2019, I joined Grafana Labs as a Developer Advocate, where I led the efforts of creating a thriving community of plugin developers for Grafana.
After an incredible time at Grafana Labs, I left to become an independent Developer Educator, where I advise teams on Developer Experience (DX) and Developer Education.
Selected projects
Plugin development for Grafana
Stockholm Go Community
Domain Driven Design in Go
Archive
- Get started with data privacy vaults using Databunker
- Westin's four states of privacy
- Deploy Fides to Kubernetes
- Privacy code scanning with Privado
- Understanding privacy risk with k-anonymity and l-diversity
- Get started with Fides
- How to include code examples from file with Hugo
- Beginner's guide to executive functioning
- The Power of Busywork
- Useful accessibility features for neurodivergent Apple users
- How I (un)manage time as a neurodivergent
- How to use Apple Focus filters
- I'm joining AssemblyAI
- New maintainer for the Obsidian plugin docs
- How to write tutorials for learning
- Announcing Obsidian Projects
- New maintainers for my Grafana plugins
- How I set and track goals using Obsidian and OKRs
- Beginner-friendly issues
- Adding context and options to your Go client package
- Notes on my GolangUK 2016 talk
- Writing a Go client for your RESTful API
- Events and explosions in a distributed system
- Circuit breaking using hystrix-go
- Thoughts on DDD in Go