Biosystems engineer who'd rather build the tool than do the task by hand. Self-teaching the rest, one project at a time.

I came to programming sideways — through engineering problems that were easier to solve with code than without it. These days I spend most of my time learning to write software that actually holds up: clean backends, sensible APIs, things that don't fall over the first time someone else touches them.

• Backend development — mostly Python (FastAPI), with the usual suspects around it: auth, payments, databases, deployment.
• Turning vague real-world problems into something a computer can actually do.
• Understanding why things work, not just getting them to run. I reverse-engineer more than I copy-paste.

I'm building things end to end to learn how the pieces fit — from a request hitting an endpoint to something useful coming back out. My main playground right now is a SaaS project where I'm figuring out the full stack the hard way: API design, JWT auth, Stripe integration, a RAG pipeline, and getting it all deployed and running.

• 💻 Engineer who got pulled into software and decided to stay.
• 🎓 Biosystems Engineering, USP.
• 📍 São Paulo, Brazil.
• 🧠 Permanently mid-project. Always learning something I'll pretend I always knew.

_{Still figuring a lot of it out — which is mostly the point.}