I liked too many things to pick just one
In high school, I liked too many subjects to imagine choosing one for my future. I spent most of my free time on my computer, but it took two programming classes for me to understand why I enjoyed it so much.
Programming gave my curiosity somewhere to go. I could approach the same problem from different directions, follow one question into more questions, and turn an idea into something useful. All the posts about a saturated market, nonstop AI releases, and online larping haven't changed that. I still find the work interesting. I still think it's fun.
I want the work to be useful
The projects I care about most give someone time back. When a repetitive process becomes a reliable tool, the person using it can stop chasing details and focus on work that needs their attention.
That's what keeps me invested in my nonprofit work. I've built application workflows, a volunteer portal, and event websites for people whose real job is serving their community. Good software gives them one less process to worry about and more time for the people they are trying to help.
How I work with a team
I do my best work on a small or medium-sized team where people can walk over, talk through a problem, and bring in someone with context the rest of us missed. I have learned a lot from people outside my immediate team because they saw the problem from an angle I had not considered.
When a deadline gets tight, I get direct. I clarify who owns what, keep people talking, and cut whatever is making the process harder than it needs to be. Clear instructions and steady communication help a team move without wasting each other's time.
I also like automating repetitive work and staying with a product long enough to understand how it changes. I keep up with open-source tools that might improve the team's workflow, and when I find a useful one, I am usually the person sharing it with everyone else.
Outside of software
Before I wrote code, I played classical alto saxophone. I made it to region and state performances in high school, and I miss having music in my week. I don't own a saxophone now, but I hope to save for a Yamaha YAS-26 and start playing again.
These days, my favorite games are Against the Storm and Satisfactory, so I apparently keep thinking about systems after the laptop closes. I also keep up with anime and travel when I can.
I was born in Nashville and have called South Carolina home for more than ten years. My family taught me patience and perseverance through the way they work, and I grew up watching my parents show kindness to the people around them. I want my work in the local community to carry some of that forward.
What I am looking for next
I'm looking for an entry-level software engineering role on a small or medium-sized team where people talk through problems together and stay with a product long enough to improve it. I want to develop solutions now and grow into architecting them later without losing touch with the implementation.
I'm also working on professional public speaking. Filler words still get the better of me when I present. I'm often the person helping a team communicate clearly, and I want to bring that same clarity when I am the one holding the microphone.