About Me
- Lifelong learner passionate about understanding the “how” and “why” behind software by peeling back layers of abstraction all the way down to the silicon.
- Main interests: hardware/software co-design, computer architecture, operating systems, networking, compilers, and tooling used to understand and debug these systems in production.
- Currently working as a Software Engineer at Supabase on the Storage team.
- Co-organizer of Madison Systems meetup, a community run meetup focused on system internals.
- Driven by curiosity, grounded in gratitude.
Background
I studied finance and started my career in investments. After a year and a half, I realized I was more interested in computers, software, and data.
As a result, I began teaching myself programming through books, videos, and online courses. My favorite way to learn is to get a general high-level understanding of a topic and then dive into building projects.
I later left investments and worked in various data related roles. While I enjoyed working with data, I often felt removed from the actual product and wanted to be closer to the systems and software creating value for users. This is what lead me further into software engineering.
As I have continued building my computer science foundation, I have become increasingly interested in how computers work. This curiosity led me to talks from people like David Patterson, Chris Lattner and Bryan Cantrill, where I kept encountering a recurring theme: the hardware driven performance gains software relied on for decades are slowing down.
As a result, hardware is becoming increasingly specialized. Taking full advantage of this new hardware will require software engineers who understand how their code executes.
That is the kind of engineer I am working to become. Someone who can reason across the hardware/software boundary to build software for the next era of computing.
