I keep a private knowledge system where every project, meeting, and idea gets written down. This blog is the public end of that pipe.
The short version of what I do: I’m studying electrical engineering at TU Wien, I take on remote project work in software and edge AI, and I’m building two ventures on the side — processpilot, a B2B SaaS, and replai, an AI product. Both are early. I’ll write about them here as they take shape.
Why write in public
Three reasons, in honest order:
Writing is how I actually learn. A concept I can’t explain in a few paragraphs is a concept I don’t understand yet. Publishing raises the bar — a note in my private system can stay fuzzy; a post can’t.
Building compounds when it’s visible. The projects on this site exist because earlier projects were public enough that people found them and asked for more. A blog does the same thing for thinking: it lets people find the ideas, not just the artifacts.
It keeps me honest about progress. Two ventures plus a degree plus client work is a lot of plates. A regular writing cadence is a forcing function — if a month passes with nothing worth writing about, that’s a signal.
What to expect
- Engineering deep-dives — edge AI, embedded systems, and the occasional web-stack piece, in the same spirit as the project write-ups.
- Venture notes — what building processpilot and replai actually looks like: positioning, pricing, first customers, the boring operational stuff nobody writes about.
- Learning in public — book and paper notes, experiments, tools that changed how I work.
No schedule promises beyond “regularly.” If you want to talk about any of it, get in touch.