Laravel Schematics
I made this to draw Eloquent models and their relationships instead of keeping the whole schema in my head. I no longer maintain it; before I stopped, it passed 1,400 stars on GitHub and was featured by Laravel News.
Based in Den Helder. Available for remote work.
I've spent more than ten years building SaaS products, the internal systems businesses quietly depend on, and open-source tools I wanted to exist. Laravel is where I'm fastest; React and Vue.js are close by. Lately, I've been making plugins for the Omarchy desktop I use every day.
Web & product work
Some started as things I wanted for myself. Others were the systems a growing company relied on for campaigns, finance, and client reporting.
I made this to draw Eloquent models and their relationships instead of keeping the whole schema in my head. I no longer maintain it; before I stopped, it passed 1,400 stars on GitHub and was featured by Laravel News.
I wanted chess analysis to explain itself instead of only showing a better move. Chess Console combines Stockfish with AI explanations, opening detection, move visualization, and PGN/FEN input.
I spent years on the internal systems behind campaigns, finance, client reporting, and integrations with external services. They were not public, but people relied on them every day.
Desktop side projects / Omarchy
I use Omarchy every day, so I keep building the things I miss. These are the plugins I've published so far.
I built this because changing an Omarchy theme meant jumping between tools. It puts themes and Aether-backed wallpapers in one full-screen picker.
I wanted to see what was filling my disk without reaching for another terminal command. Disk Lens shows the large branches first and moves files to Trash instead of deleting them.
My touchscreen needed a keyboard that felt at home in Omarchy. This one keeps the familiar shortcuts and can also appear on the login screen.
Experience
The job gradually grew from backend development into technical leadership. I led two teams, made technical calls, and kept working in the codebase. Managing from a distance has never appealed to me.
Download the full CVAlisQI
Worked on both the frontend and backend of a SaaS product as part of its product team.
Leads.io / Social Blue
Led two engineering teams and kept a hand in design and delivery. The engineering organization grew to roughly three times its earlier size while I was there.
Social Blue
Started on the backend, building the in-house software used for campaigns, finance, client insights, and external integrations.
Toolbox
Laravel and PHP are where I have the most mileage. Depending on the job, I move across React, Vue.js, Linux, Kubernetes, and whatever else it takes to get the feature into production.
PHP and Laravel are still where I move fastest. Python now joins them when a focused local service makes more sense than another web stack.
React and Vue.js for product work; plain JavaScript, Blade, and CSS when they are enough. I like owning the whole path from API to interface.
This is where the newer public work lives: native-feeling Omarchy plugins, shell integration, private networking, and Linux plumbing.
I care about proving software outside the happy path: production debugging, CI, and disposable VMs for changes that can affect a real desktop.
Technical direction and mentoring matter. So do humor, empathy, and making sure people feel comfortable enough to speak up.
This was not the original plan.
Before software
Before I wrote software, I wrote music. I studied counterpoint and composition at the conservatory in Alkmaar.
Counterpoint has several independent lines moving at once without losing the whole. Software teams are not music, obviously, but that kind of problem still feels familiar.
Curiosity about Linux pulled me into programming. Java came first, then PHP and JavaScript. I did not plan the career change; it just stuck.