I started programming as a hobby and tried many directions. That's why I understand how a system fits together, from the server to the interface.
I worked on modernising enterprise systems. Here, engineering discipline replaced the 'just make it work' approach.
I was responsible for the company's technology strategy, architecture and development processes.
I take on the same responsibility as a CTO, just directly, without an agency layer. I am also studying computer science, and I bring what I learn back into client work.
The person who hears your request builds and runs the system. No runaround; decisions are made in minutes.
A version you can try every two weeks, an itemised quote, and you always know where the project stands and what it costs.
The code, the documentation and all access belong to you. If you later continue with someone else, I will help with that too.
Web interfaces and the logic behind them.
Reliable databases, migrations, reports.
Backups, monitoring, safe updates.
Document processing, internal knowledge bases, on your own server.
When I'm not building systems, I'm probably hiking, taking photos, or looking for the perfect espresso.