Feedback in seconds, not in CI
The same checks run in the editor, before push and in CI, so problems surface while the code is still in your head, not twenty minutes later.
Seen in: Foundry →
~/what-i-do/dx
Developer Experience
Developers are fastest when the right thing is also the easy thing. I look for the friction that quietly eats a team’s week (slow feedback, flaky setup, manual steps) and remove it with tooling, not more documentation.
01How I work
One command to a working setup
Pinned toolchains and reproducible environments end "works on my machine". A new developer should be productive on day one.
Remove steps instead of documenting them
Scaffolding, CLI tools and previews beat a wiki page listing twelve manual steps nobody reads.
Seen in: Email Template Preview →
Ask where the time goes first
Before picking tools I watch how the team actually works. The biggest win is often not the one anyone asked for.
02What I’ve built
Foundry
A polyglot engineering gate for AI-assisted development
- GitHub Actions
- mise
- Python
- POSIX shell
jev-sort
jq for judgment - bulk classification at pennies per 10k rows
- TypeScript
- Node.js
- Jev
- JSONL
Email Template Preview
Preview transactional emails with real order data, rendered like Gmail would
- PHP
- Shopware 6
- Symfony
- Vue
DevInsight
GitHub activity turned into an evidence-based portfolio
- Java
- Spring Boot
- Spring Security
- OAuth2
03What I can do for you
from 7,000 DKK fixed
CI/CD & quality-gate setup
One deterministic rule set - format, lint, types, tests, coverage, security - that runs identically in the editor, before push and in CI. Ratcheted so legacy code can adopt it on day one.
from 4,500 DKK fixed
AI-assisted development enablement
Get real leverage from coding agents without the chaos: skills, hooks and a gate the agent can’t quietly weaken, plus workflows from ticket to reviewable PR.
04Writing
One rule set, three placements
Why I stopped treating CI and "AI coding standards" as two separate things - and what Foundry does instead.