A 5-person external team spent 3 months building an audit system. It did not work. I rebuilt it from scratch in 3 weeks.
Not only was their code full with bugs. It required us seed our entire database as an audit trail to work at all. I discussed the issues with management, proposed a clean solution, and delivered a working system in the remaining time before the deadline.
Though I will always have a passion for
PCB design and product prototyping,
I currently work as a Laravel developer.
Coming from a hardware background gives a certain edge
When you have to write code in Assembly and the only way of verifying that a piece of code works, is a blinking LED
You get very creative with debugging
A deep understanding of the system is necessary to do the work
Most of the time there is no manual, because you build the hardware yourself
I will tell you, when you do not need custom code
I love writing code, but only if it is actually needed
I want to solve the problem, not sell you a piece of code
I was the "break glass in case of emergency" developer
When something needed to be fixed fast
I spot in minutes, what others might spend days on
Both in known and unknown code bases
Projects that are stuck, behind, or abandoned - I finish them.
Connect your Laravel app to CRMs, payment systems, and external APIs.
Add LLM and AI capabilities to your existing applications.
Slow queries and bottlenecks identified and fixed.
For the last 3 years, I was the only team member trusted to work fully remote. While colleagues were in the office, I delivered from wherever I was — same quality, same speed.
Based in the Netherlands. Available for remote projects or on-site.
From Dutch accounting software to enterprise CRMs
1-3 month projects. Fixed scope. Delivered with tests and documentation.