About

What I do

I work across the stack: TypeScript and React on the frontend, Node.js and Go on the backend, and Java with Spring when a system calls for it. I have spent years on business software, integrations and fiscal automation, the kind of system where a wrong number or a lost document has real consequences.

What I do best is the part that decides whether a system survives over time: quality you can verify. Tests that prove behavior instead of mirroring the code, CI that blocks a regression before it merges, and every problem that shows up twice turned into a check that fails on its own the next time.

Zenith

Zenith is fiscal automation software in production at an accounting office. It collects electronic fiscal documents straight from the official web services with an A1 digital certificate, files them by client and period, generates the official printable forms and updates itself on Windows.

I own all of it: product, Go backend, React interface, packaging, release and support. Because it handles documents with legal value and digital certificates, it is the project where I take testing, failure handling and care with sensitive data most seriously. A public page for Zenith is on the way.

The lab

Alongside the products there is a lab: small, free tools where I try ideas in public, such as PushPower, a push-up test and load calculator based on published fitness norms and research. It is also where I experiment with design, performance and search. Lab tools are supported by ads so they can stay free.

How I work

Small scope on purpose: a product should do one thing and do it well. Numbers come from sources you can check, such as official specifications, published norms and studies. And the tools respect your time: no sign-up when it isn't needed, fast on any phone, collecting only what they need.

Want to talk about a project, about Zenith or about something you found in one of the tools? The contact page has my email, and every message gets read.