How work
Technical rigor, open-source and collaboration without commercial pressure. An IT employee who carefully chooses the projects to invest extra energy in.
Work Principles
Four pillars that guide every technical decision
Clean Architecture
I separate domain, application, infrastructure and presentation in every project. Zero cyclic dependencies, architecture rules verified at compile-time.
TDD
Tests before code. Red-Green-Refactor as daily work rhythm. Target: >80% coverage on every relevant feature.
Documentation-first
CLAUDE.md, ADRs, README and inline comments are part of the deliverable, not an afterthought. Code without documentation does not exist in my workflow.
Open by default
I prefer opening code to the public when possible. Permissive licences, clear CONTRIBUTING.md and accessible issue board.
Preferred stack
Technologies on which I have invested years of practice and in which I feel solid
Preferred collaboration types
No pricing, no public availability - only contexts where I can contribute with quality
Open source contribution
Issues, pull requests, review or documentation on existing OSS projects.
Side project co-building
We build something new together - tool, library or micro-SaaS.
Technical speaking
Talk, workshop or hands-on sessions on Angular architecture, Spring Boot or ML.
Occasional code review
Targeted review of a module, a design or a critical pull request.
Do you have an idea to explore?
My preferred channel is email - describe the project, the technical context, and why you think we could work on it together.
I'm not available for unplanned ongoing engagements. I respond to concrete proposals within 48-72h on business days.