Cost-aware infrastructure
Finding and reducing unnecessary AWS spend without trading away reliability.
Senior software engineer · Buenos Aires
I like understanding how complicated systems actually work.
I’m a software engineer working across AWS infrastructure, backend systems, and legacy modernization. I tend to follow a problem across boundaries until it makes sense.
Selected engineering work01—03
Incremental modernization
Breaking down legacy systems in small steps instead of committing to a risky rewrite.
High-traffic platforms
Building campaign and marketplace systems for large commercial events.
Writing
Technical notes.
Nothing published yet.
I’m resisting the temptation to fill this section with articles I don’t have a reason to write.
How I tend to work
Understand the mechanism
I’m rarely satisfied with “that’s how it works.” I want to know where the boundary came from and what happens when it fails.
Build what is justified
I like knowing what the ideal design looks like. I also like admitting when it is not worth building yet.
Follow the consequences
A technical decision changes cost, operations, product behavior, and how somebody debugs the system six months later.