I build the machine that ships your software.
Fractional software engineer and architect. I take over platforms that have eroded past the point where anyone can safely change them, and turn them into a delivery operation that runs on one meeting a month.From a release once a quarter to one every 8 days
Client-reported production issues down from ~100 to ~5 a month
Deploys in 15min instead of 2h
You know the system is the bottleneck. You just can't prove it in a meeting.
- Your last release was a quarter ago, and everyone still remembers it.
- Nobody touches that one module without clearing the afternoon.
- The engineer who understood the system left, and the documentation left with them.
- Every deploy is an event, with a rollback plan and a prayer.
- Features arrive three to six months after you approved them, if they arrive.
If you nodded twice, we should talk. If you nodded at all five, we should talk this week.
Work modes
Rescue
I reconstruct how your system actually works, then tell you what to fix and in what order.
- Fixed scope and fixed duration, ending in a written map: what's broken, what it costs you, what to do first.
- No rewrite proposal. A rewrite is what got the last team into this.
- You keep the map whether or not you hire me for what comes after.
Delivery Machine
Requirements go in, reliable releases come out — and the technical overhead stops being yours.
- Monthly retainer. Pipelines, test suites, staging-to-production promotion, monitoring, and release notes on every deploy.
- Modernization happens in increments, alongside feature delivery. The business keeps running; there is no freeze.
- One meeting a month. Everything else is written and async.
Build
From requirement to production, one person, no handoffs.
- Discovery with your team, then database, backend, frontend, and deployment.
- The delivery machine is installed from day one, before the erosion starts.
- No perfectly-written ticket required before work begins.
Engagements
Medical education platform — medical-residency exam prep
Fractional engineer · sole owner of ten repositories, three in active development · 2024 – present
Ten repositories with no automated pipeline anywhere. A release roughly once a quarter, delivered inconsistently and with heavy rework. An approved request took three to six months to reach production. Two people on support hand-sent hundreds of personalized emails every week.
The full delivery machine — automated tests, CI/CD with staging gates, contract validation, monitoring, and release notes pushed on every deploy — plus an AI-native development workflow running under my sole architecture and review, and a modernization of the codebase carried out in increments alongside feature delivery.
An approved request now reaches production in about a week instead of three to six months. Releases run about four a month, one every eight days, with little rework. Client-reported production issues fell from around a hundred a month to about five. Zero downtime. Deploys went from two hours to fifteen minutes. The monthly follow-up operation went from a month of manual work to about two hours. Client involvement: one meeting a month.
Newspaper platform modernization — via Muvz
Senior engineer and architect · team of eight developers · 2023 – 2024
A legacy Java EJB monolith mid-modernization, already three months behind schedule.
Five Spring Boot microservices extracted incrementally — no rewrite, no freeze — with event-driven integration over Apache Kafka, a centralized back-office for shared configuration, and engineering practice (Hexagonal Architecture, SOLID, DDD) established across the team.
The three-month delay eliminated and delivery back on schedule. System performance up 40%. The team held a restored 15-day sprint cadence after I rolled off.
Presidential campaign platform — via Conddiz
Senior engineer and frontend architect · 2022
A national campaign with a fixed, immovable date and no platform.
One backend serving three frontends — the official website plus two production PWAs — with integrations across every major social network.
Shipped on the campaign calendar and sustained traffic peaks of around 200,000 users at its most critical moments.
Your involvement is one meeting a month.
Requirements, architecture decisions, and backlog live in the repository, as one source of truth you can read without me in the room. Every deploy pushes release notes — technical and business — to you automatically. You get proactive, high-signal updates instead of status calls, and you own the code and the pipeline from the first day, not from the last one.
- Async-first, remote, GMT-3 — overlapping business hours with the Americas and half of Europe.
- One scheduled meeting a month. Anything urgent has a channel; nothing urgent needs a calendar invite.
- Decisions written down where the code is, so the next person — including future you — can reconstruct why.
- For 2 years now, the commit log across all 10 repositories shows one human name: mine. The only other author in it is an AI agent I built the harness for. That is what the machine buys you.
Testimonials
Bugada
Gata
“Miau.”
Leão Lascado
Leão empalhado
“Não faço a mínima ideia de como vim parar aqui.”
Lesada
Gata
“Miau miaaaaaau! Fsssssst!”
Recent writing
AI Didn't Organize My Life. It Helped Me Get My House in Order
I didn't build a cyberpunk workflow that reads my emails for me. I used AI to unlock real work: refactoring, tests, documentation, and projects I had been postponing for far too long.
AI and Developers: Another Brick or Another Floor?
AI will shake the market — that much is certain. Whether it walls developers in or elevates them depends on a timescale most people forget to consider.
Interfaces aren't villains
A technical and architectural analysis on the value of defining explicit contracts even when there's only one concrete implementation.
Why am I still invisible?
Why, despite being qualified, am I still invisible to the job market?
Is learning coding really hard?
Spoiler: Learn how to code isn't hard. Its just a lot of work. And we usually confuse these two concepts.
Three places I write
Blog
Essays on delivery, architecture, and what actually happens when one engineer runs a platform with AI agents.
Workaround-Oriented Programming (livropog.com.br)
A living technical book about the gap between the architecture we present and the workarounds we ship. Written in Portuguese, published continuously.
Codex Technomanticus
My grimoire — the working notes I keep for full-stack engineering and share with colleagues when a question comes up twice. Written in Portuguese.
Let's look at your system.
Thirty minutes, no slides. You describe what's breaking; I tell you what I'd look at first and whether I'm the right person for it.
Book a 30-minute call