[Draft note for Manuel]: mirror of the ES version, same disclaimer applies — confirm if the pricing/engagement model described ("no open-ended scope") matches how you actually want to structure a project.

I design and build custom software when you already know the problem you need to solve, but need someone to take it to production with the discipline a real system demands: tests, observability, and code the next developer can understand without you standing next to them explaining it.

I work mainly with Java/Spring Boot on the backend and Next.js/TypeScript on the frontend — the same stack that runs this site, and the one behind high-availability production systems I've built (real-time tracking for a satellite fleet, with automated deployments and reproducible infrastructure provisioning).

What's typically included:

Backend APIs with Java/Spring Boot (or another stack if the project already defines one).
Frontend with Next.js/React when the project calls for it.
Integration with relational databases (Postgres), event queues (Kafka), and cloud deployment (AWS).
Versioned, tested, documented code — a deliverable that doesn't depend on my memory to stay maintainable.

Scope, timeline, and cost get defined before work starts, in a free initial conversation — I don't work with open-ended scope.

Have a concrete problem to solve? Let's talk.