Matthew Gentry
Bio
I like to get my hands on projects as much as I can, it can be related to software, electronics, or even a new hobby. I try to make sure I give my best effort and it drives me crazy when I don&apost;t finish a project.
When I'm not working on technical projects, I'm usually working on one of my hobbies or salavating over a nice cut of Ribeye. I try my best to be well rounded and give everything I have. You can check out some of my hobbies, bucket list entries, and my work style below.
Hobbies
Other than projects, this is what I love to do
Guitar and Music
Playing guitar since high school — everything from blues, bluegrass, country, rock, grunge, and R&B. Music is my life passion and I never want to give up on it.
Dungeon Mastering
Running D&D campaigns as Dungeon Master — Nerd Stuff. I love to build worlds and history that comes from my own mind. I'm very data driven so I love to make it up that makes sense to people in the real world.
Problem Solving
Puzzles, riddles, escape rooms, word searches, YOU NAME IT. If there's a system with a hidden logic, I want to find it.
Gaming
Strategy games and anything with a strong narrative. I'm interested in game design as much as playing. Legend of Zelda is my favorite series.
Reading
I love reading real stories about people's problems that are supposed to help you understand your own situation.
Bucket List
Things I've done and things I'm working toward
Work Style
How I work and what I look for in a team
I work best in environments where craft is taken seriously and opinions are welcome. I'm the kind of teammate who asks "why" before "how", reads documentation before asking questions, and cares about code that others will have to read six months from now. I&apost;m very driven to also be in a flexible situation because nothing really ever goes according to plan.
How I Work
Async-first, but not async-only
I do my best thinking in writing and in focused blocks. I'm not a fan of meetings that could have been a message — but I know when a five-minute call beats a thread of twenty replies.
Documentation before heroics
If I build something, I write down how it works. Future-me and future-teammates deserve that.
Iterative and incremental
I try to small, learn fast, and avoid the trap of building the perfect system no one is ready for. But as we all have learned, it's a lot harder to make that a habit that it would seem.
What I Value
Honest feedback culture
I'd rather hear "this is broken and here's why" than polite silence. I give the same in return. That's how we keep progressing.
Ownership without silos
I believe in having clear owners for things without anyone hoarding context or refusing to help outside their lane. It helps a lot when I'm allowed to give you what you want without jumping through hoops.
Craft without ego
Good code is good code regardless of who wrote it. I'm happy to have my work improved. Just tell me when you change it.
My Approach to AI & Human Ingenuity
I think about AI as a tool, not a replacement. I embrace AI as a powerful tool to enhance my work and not to replace it. My values lie in my ability to solve complex problems, think creatively, and deliver results that AI alone cannot achieve. I use technology to work smarter, but my human insight drives home the completed product.