How it started
init: start building for the web
I started building for the web as a teenager, long before I could call it a job. Friends, family, the odd local business: whoever needed a website or a script got one.
Software developer from Amersfoort, the Netherlands. Here's my history the way I'd read anyone else's: as a git log. Oldest first, one branch per part of my life. Commits marked real come from my public GitHub repos; the app releases are their public release dates. The apps' own code stays private.
~/youri $ git log --reverse --graph --all
init: start building for the web
I started building for the web as a teenager, long before I could call it a job. Friends, family, the odd local business: whoever needed a website or a script got one.
feat: first paid work as a freelancer
Around 2005 the odd job turned into freelance work. Some of it was good, some of it I’d rather not see again, and all of it taught me something.
feat: start the MBO ICT Beheerder
Alongside that I went to school to become an ICT Beheerder: an MBO in IT administration. Windows domains, Active Directory, Exchange. Not the most glamorous start for a developer.
feat: file servers on Debian with Samba
But it stuck. I still want to know what happens on the server, how something gets deployed and what it does when it falls over.
merge: freelance into a job at a web agency
merge: mbo, diploma ICT Beheerder
feat: first lead role
Then lead roles at a few smaller companies. More responsibility, same love for an empty folder.
feat: lead developer at ArchiXL
Since 2013 I’ve been lead developer at ArchiXL in Amersfoort. I work on WikiXL, a knowledge platform built on MediaWiki that organisations use to record how they work: their processes, their terminology, how their systems fit together.
My favourite moment in a project is the very beginning: an empty folder and an idea. I don’t mind the other end either. A bug is a puzzle to me. Somewhere an assumption was wrong or a case was missed, and finding out which one is one of the more satisfying parts of the job.
fix: more variables in someone else’s CS:GO server script
My first commit on GitHub was a small change to a script someone else wrote. That’s open source in one line: you take something good, improve it a little, and hand it back.
Almost everything I’ve built professionally stands on it. Linux on the servers, PHP and Laravel in the code, MediaWiki under the platform I work on, SimpleSAMLphp for signing in. Thousands of people wrote that software and gave it away. The least I can do is give some of it back. So when I solve something others will run into too, I try to publish it instead of leaving it in a private repository.
feat: PHP wrapper for the Uptrends monitoring API
feat: two-factor sign-in for MediaWiki
feat: Jenkins recipe for Franz
feat: many domains on one SimpleSAMLphp codebase
feat: security advisories in a dashboard, with what you did about each
release: Laadpaal Notifications
At work I build for organisations: large groups, long lists of requirements, many people with an opinion. In the evenings I like the opposite. Building for one person with a phone in their hand.
The first one: I simply wanted to know when a charging point is free. There was no simple app for that, so I made one.
docs: twelve years in, and still here by choice
For a long time my job was simply writing code. That’s still a big part of it, but the role has grown. These days I also coach other developers, think along on other people’s problems, and now and then mediate when opinions clash. I didn’t expect to enjoy that side of the work. I do, quite a lot.
release: Laravel SPARQL 1.0, an Eloquent model for triple stores
Lately most of my spare attention goes to linked data. It’s a niche, but a good one: data that says what it means can outlive the system it was first entered in.
feat: parsers for RDF/XML, Turtle, JSON-LD, OWL, SHACL and XML Schema
Eight PHP packages, published source-available. None of it is famous. It’s software I needed and figured someone else might need too.
release: FocusDose
For a plain problem: forgetting whether you already took your dose, and having no clear overview to bring to your doctor.
release: Manifest
Affirmations read aloud, with no ads and no account, that you can buy once instead of paying every month.
release: Storewright
A Mac app that looks after your App Store apps: it reads your numbers, says what is worth doing, plans the next version and shows afterwards what each release did. Open to the public since 18 November 2026.
Each app gets exactly enough features to solve its problem, and then I stop. No account where none is needed, no tracking beyond what’s required, and a fair price.
feat: start van den Bogert Software
The apps now have a company of their own: van den Bogert Software, a one-person business registered with the Dutch Chamber of Commerce. It runs alongside my 40 hours at ArchiXL, in the evenings, the way the apps always have.
docs: write an about page
Use one of my apps, have an idea, found a bug, or want to talk shop? Push something my way.