Whoami
I’m Vicente Sanchez. I’m interested in the systems, tools, and abstractions that make software possible.
I’m 17, based in São Paulo, Brazil, and currently working at Warp.
I spend most of my time thinking about infrastructure, distributed systems, programming languages, databases, and the abstractions we build on top of them.
I’m particularly interested in authentication, payments, and financial infrastructure. How we establish trust, move money, and build systems that make financial services accessible without exposing the complexity underneath.
I believe the best technology is often the technology people never have to think about. Blockchains, cryptography, and distributed systems are interesting not just for what they are, but for what they make possible when the underlying complexity gets out of the way.
How I got here
I started coding at 11, during the pandemic. I was playing GTA V with friends and got obsessed with how people were modifying the game. I started writing my own mods, then Discord bots for the servers running them, since every one of them needed things like whitelisting systems.
What started as a hobby gradually became something I wanted to pursue full-time. I eventually left high school to go all in.
At 16, I joined Tela as a Foundation Engineer, working on developer tooling and infrastructure. Today, I’m at Warp, working primarily on payments and internal tooling.
Interests
- Systems engineering: distributed systems, concurrency, fault tolerance, orchestration.
- Authentication & identity: identity infrastructure, authorization, access control, trust.
- Payments & financial infrastructure: payment processing, money movement, settlement, financial rails.
- Crypto & blockchains: distributed ledgers, consensus, cryptographic protocols, and the infrastructure behind onchain applications.
- Databases: storage engines, transaction processing, consistency, analytical systems.
- Programming languages: type systems, runtimes, interpreters, functional programming.
Philosophy
I believe good abstractions come from understanding the underlying complexity, not hiding it.
Technology should solve more problems than it creates. The best infrastructure doesn’t ask users to understand how it works. It just works.
I prefer boring infrastructure, explicit behavior, strong guarantees, and systems that are easy to reason about.
A few things I tend to believe:
- The best technology is invisible technology.
- Correctness before performance. Performance before convenience.
- Understand the primitive before adopting the abstraction.
- Prefer composition over unnecessary complexity.
- Make failure a first-class part of the design.
- Build things that should exist, not just things that can exist.
Why this guide
The explanations I wanted didn’t exist in one place. Most material on distributed systems is either a paper that assumes you already know the vocabulary, or a blog post that stops before the hard part.
I want to explore the ideas behind the systems we use, understand the trade-offs involved, and document the things I wish I’d understood earlier.
So I write the version I wish I’d had.