From idea to a working system

I take a problem apart, design the solution and carry it through to production. Then I run it myself, which is why I build plainly rather than impressively.

Start a conversation See the projects

Who I am

One job title, a different set of problems

My job title is systems administrator. In practice I handle the work companies normally buy as a service or hand to a contractor: video calling, meeting-room booking, mini-apps, and bots. Every project started either with a colleague's complaint or with a refusal to pay a vendor. All of it is deployed and in use every day.

I have no commercial experience as a developer and I do not hide it. What I have instead is systems people rely on daily, and the experience of supporting what I wrote myself.

I use AI in my work and make no secret of it: it speeds up drafts and routine. But what gets built, and why it is built that way, I decide myself.

How it works

Approach

01
Analysis

I take apart the task, the processes and the constraints before a single line of code is written.
02
Architecture

I design the solution so that it stays simple to extend and to support.
03
Development

I build the system in iterations and show the result at every step.
04
Launch

I roll it out, train the team and stay reachable after release.