software engineer :: distributed systems :: backend & infrastructure :: computer science @ UBA :: systems thinker

I'm a Software Engineer and Computer Science student at the University of Buenos Aires, interested in understanding how computational systems behave and in building reliable software based on those principles.

My interests sit at the intersection of software engineering and computer science — particularly distributed systems, concurrency, operating systems, networking, databases, and scalable infrastructure.

I enjoy going beyond "how do I implement this?" and asking:

• What is actually happening under the hood?
• What assumptions does this system make?
• What happens when components fail or run concurrently?
• How does the system behave as it scales?
• What are the trade-offs behind this design?

I care about writing software that is not only functional, but also understandable, observable, reliable, and maintainable.

• Distributed Systems
• Concurrency & Parallelism
• Operating Systems
• Computer Networks
• Databases & Storage Systems
• Algorithms & Data Structures
• Computer Architecture
• Systems Programming

• Backend Architecture
• Event-Driven Systems
• Message-Oriented Architectures
• API Design
• Scalability & Performance
• Fault Tolerance
• Observability
• Infrastructure & DevOps

I like understanding systems from first principles.

A technology is interesting to me not because it is popular, but because of the problem it solves, the guarantees it provides, and the trade-offs it introduces.

I'm particularly interested in the space between theory and practice: taking concepts such as process isolation, synchronization, caching, message delivery, consistency, failure handling, and concurrency and seeing how they shape real-world systems.

• Distributed systems and system design
• Process communication and synchronization
• Operating system internals
• Concurrency and parallelism
• Message delivery semantics
• Caching and cache coherence
• Fault tolerance and failure modes
• Observability of distributed applications
• Database consistency and storage systems
• Systems programming in C
• Low-level computing and computer architecture

I learn best by building, breaking, measuring, and then trying to understand why the system behaved that way.

Most of my repositories are experiments driven by questions rather than just products.

Some things I enjoy exploring:

• Distributed systems: message passing, queues, workers, coordination and failure handling.
• Operating systems: processes, signals, pipes, scheduling and inter-process communication.
• Infrastructure: containers, monitoring, logging and production-like environments.
• Backend systems: event-driven architectures, APIs, databases and asynchronous processing.
• Computer systems: low-level programming and understanding what happens beneath abstractions.

Outside engineering, I'm usually doing something that keeps me curious:

• 🎮 Gaming — a curiosity that started when I was 6.
• 📚 Reading about technology, philosophy and systems.
• 🏋️ Training and pushing physical limits.
• 🌊 Surfing.
• 🧘 Meditation.
• 🐈 Spending time with my cats.
• 🎤 Karaoke with friends.
• ☕ Good coffee.

"The interesting part of a system is often what happens when things don't go according to plan."