The person behind
the integrations
I am Patrick Røbel, software developer at ZRM and software technology student at DTU. Most of my work lives in the space between systems: CRMs, ERPs, e-signature platforms, and the APIs that are supposed to connect them but never quite do on their own.
I did not take the straight road here. I spent five semesters designing buildings, and I have spent eight years running restaurant floors, which is why I stay calm when production is on fire: I have handled actual fire, and a fully booked Saturday, sometimes in the same shift.
The same instinct spills into my free time, where I build developer tooling and toys that have no business case and need none. This site doubles as a playground: every project gets its own page, and some of them get very silly.
The road here
The restaurant years
Restaurant manager and events lead at Eattoday in Copenhagen, after working every station from bar to kitchen. Eight years of meeting guests at eye level, defusing conflicts, and staying calm during the Friday rush taught me more about teamwork and communication than any course ever has.
The building design detour
Five semesters of building design engineering at DTU: structural analysis, BIM, parametric design, fire safety. I can still size a steel beam and argue about Eurocodes, which comes up less often in software than you would hope.
The switch
One summer course in programming was all it took. I switched to software technology at DTU with only a year of my old degree left, because pretending you have not found the thing you love is a bad long-term strategy. Since 2025 I have been putting it to work as a software developer at ZRM.
What I work with
Integrations and APIs
Making systems that were never introduced to each other work together reliably.
Web development
Modern TypeScript across the stack, with a soft spot for the frontend.
AI-assisted engineering
Treating AI agents as teammates: orchestrated, guard-railed, and verified end to end.
Developer tooling
Building the tools that make the rest of the work faster, from CLIs to desktop apps.
How I work
Fail loudly
Automations that break silently are worse than no automation. Everything I ship logs what it did and shouts when it could not.
Dry-run first
Data migrations show what they would change and wait for a yes before touching anything.
Small iterations
Ship a thin slice, verify it end to end, then widen. Big-bang releases are where bugs hide.
Readable trails
Logs, commit messages, and docs a colleague can follow six months later without asking me.
Fun facts, verified
- I am colorblind. Nobody notices, including me.
- I have run the Eremitage run 16 years in a row, every year since I was 10.
- Core competence: drawing Pokemon. Unrelated to any job I have ever had.
- Golf at VGK, american football for SGD in the Danish National League.
- Big on cooking, good food, and wine. The restaurant years left a mark.
- My toothbrush is blue.
