About Me
I’ve been writing code for a long time… just not in a “let me tell you exactly how long” kind of way.
It started with a summer school course when I was 11. By middle school, I’d found a group of friends who were just as into computers as I was — which, looking back, probably mattered as much as the code itself.
After high school, I learned how to build computers before I really knew how to make them do anything interesting. That realization is what pushed me toward a computer science degree.
During college, I got my first real taste of working on production code with a summer job helping maintain the school’s website. After graduating, I went straight into building websites for clients — the kind of work where you learn quickly that “it works on my machine” doesn’t count.
Since then, I’ve worked on large, enterprise web applications across a range of stacks — frontend, backend, databases, APIs. I’ve spent enough time in each layer to appreciate how everything connects… and how everything can break.
These days, what I care about most is building good user experiences. Not just code that works, but code that makes sense — to the user and to the next developer who has to read it.
Why This Site Exists
In tech, we need to always be leveling up. That can come in many forms, not just code, but other skills.
I am building this site as a learning tool for myself, but if I can also help someone else learn something new, that's a bonus.
I will share things I learn including side projects and experiments.
I find that when it comes to documentation and tutorials, a lot of content uses the simplest example that isn't always practical in real-world scenarios. If I'm able to expand my knowledge, and maybe, yours too, then I've done what I set out to do.
How I Think About Learning
The biggest constant in my career has been learning.
New tools, new frameworks, new patterns — they never really stop coming. The only way I’ve managed to keep up is by staying curious and being okay with not understanding things right away.
A few things I’ve learned along the way:
- Struggling with a concept is part of the process, not a failure
- Writing things down (like this) is one of the best ways to actually learn them
- Learning is iterative. You start with the basics and build on it
I still tinker with code outside of work, not because I have to — but because I enjoy it. Yes, I am that guy who writes code for fun.
Side Projects (and the Graveyard of Ideas)
Like a lot of engineers, I have:
- unfinished side projects
- half-built tools
- and more unused domain names than I’d like to admit
I like starting things. I like figuring them out. Each of those projects taught me something, and that’s kind of the point. I can tinker and learn something on my own, then take that and use it in a situation (like at work), where it makes a bigger impact.
Non-Technical Things
I have a slightly corny sense of humor, which tends to sneak into my writing whether I intend it to or not.
I’m also a big fan of sci-fi — books, shows, movies — anything that explores big ideas and weird possibilities. There’s something about that genre that pairs well with programming: both are about imagining how things could work.