About Me

Building reliable systems with intention

Background

I'm learning backend development after working on electronics systems in the Navy. I got interested in programming because I like understanding how things work at a fundamental level. Debugging a circuit board or figuring out why an API isn't responding correctly, it's the same kind of problem-solving.

I'm teaching myself Go and backend concepts by building real projects. Right now I'm working on an image compression API to learn about service architecture, databases, concurrent processing, and deployment. It's messy and incomplete, but that's how I learn best.

I like Go because it's straightforward and doesn't hide complexity. I'm drawn to backend work because I prefer working with data, APIs, and servers over UI. I also enjoy working with Linux systems and learning about deployment, scripting, and developer tooling. I appreciate POSIX-compliant tools and portable workflows. Things that work the same way across different environments.

What I'm Looking For

My first software engineering role where I can learn from experienced developers and contribute to real systems. I want to grow my skills in backend development, infrastructure, or DevOps. I'm interested in the full developer lifecycle. Writing code, deploying it, monitoring it, and improving the tools that make development easier. I'm comfortable being the least experienced person in the room. That's where I'll learn the most. I also work well independently and can figure things out on my own when needed.

How I Approach Learning

Build to Learn

I learn best by building real projects, making mistakes, and figuring out what broke and why.

Ask Questions

I'm not afraid to admit when I don't understand something. Better to ask than pretend.

Document as I Go

I write things down to understand them better and help future me remember what I learned.

Focus on Fundamentals

Understanding how things actually work matters more than memorizing frameworks.