Why I finally built this site

I have been shipping mobile applications for about ten years. Banks, retailers, a national newspaper, a Bitcoin app, an education platform in Switzerland. In all that time I never kept a single public note about any of it.

That is a strange thing for someone who spends his days reading other people’s notes. Every time I hit a wall — a native module that would not link, a React Native upgrade that broke Hermes, a CI pipeline that only failed on Tuesdays — I got out of it because someone else had written down how they got out of it first. This is my attempt to start paying that back.

What this site is

Two things.

The first is my CV. It lives here as structured data rather than a PDF attached to an email, which means it is always current, it is readable on a phone, and I can print it when someone insists on a PDF.

The second is this blog. I want to write about development in the round, not just React Native:

• Mobile engineering — the parts that do not fit in release notes.
• Architecture — what clean architecture actually costs, and when it pays.
• Testing — what a test suite is actually for, and why the coverage number is the least interesting thing about it.
• Tooling and delivery — Fastlane, Bitrise, EAS, and the CI pipelines that either save your week or eat it.
• The job itself — contracting, technical leadership, mentoring, and what changes when you are the only senior developer on a greenfield project.

How I intend to write

Short posts about real problems, with the details left in. No listicles. If something did not work I will say so, because the failed approach is usually the useful half of the story.

If you want to argue with something here, my email is at the bottom of every page. I would rather be corrected than agreed with.