System Architect & Software Developer. 37 years in the game. 26 professionally.
Building minimal tools that earn every byte. Inspired by the demoscene. Guided by Unix philosophy. Using AI to engineer, educate and validate, not to replicate the bloat faster.
I design systems where reduction is the method, not the compromise. Small binaries. Semantic markup. Honest interfaces. Every abstraction must justify its weight.
Currently Senior Developer at a German DIY wholesale giant, working with React, TypeScript, and Spryker. Privately building small tools for testing ideas, ultralight and rooted in demoscene constraints.
System architecture, performance engineering, and the frontend that sits on top of both. Full-stack, if you must; I prefer to call it taking responsibility for the whole path.
The common thread is root cause over symptom: I would rather remove the reason a system is slow than buy hardware to outrun it.
The writing here runs in three parallel series: Lean Software, on building less and getting more; Unix Universe, on the operating systems that outlived their critics; and IT Philosophy, on why we keep making the same expensive mistakes. Different angles, same argument: complexity is a cost, not an achievement.
A tool that was free on every corporate laptop for a decade grew a coin slot in 2021, and the meter has been turned twice since. The subscription does not charge for containers. It charges for the distance between a laptop and the kernel its software runs on.
An empty Next.js project declares 11 dependencies and receives 438 packages. Checking that nothing takes 12.4 seconds, on hardware faster than your CI. Every stage is a repair for a property that arrived with the tooling.
In 2004 three engineers wrote down what an observability tool must guarantee before anybody may switch it on in production: nothing at all when disabled, absolute safety when enabled. Both sides of the divide met it. And the dashboard still gets asked first.
A demo has no size limit at all, and this one still needed a new tool. Nearly 4,000 rows of sync data and around 592,000 values, all of which shifted every time the music grew a bar. The music led, the code followed, and the prize went to the soundtrack.
In a fire, seventy-one per cent leave through the door they came in by. In a meeting nothing is burning, and people do it anyway, then close the discussion with four words. State of the art is a legal test, and widespread adoption is the documented way out of it rather than into it.
No framework. No build step. Measured live in your browser. Pure CAST Daemon.
The numbers above are measured live in your browser: your connection, your device, no averages. Below is what Google thinks of the result. Lighthouse audits four dimensions: raw speed, semantic accessibility, security and API hygiene, and search engine visibility. Four perfect scores from a self-made Rust binary web server with zero dependencies.
Google Lighthouse. Measured on vivianvoss.net, this site, served by CASTD — an extremely fast self-made and full scale web and content server written in pure Rust with zero dependencies.
