Skip to main content
MG
Matthew Gentry

Matthew Gentry

Software developer. Amateur musician. Lifelong learner.

I build software because I like making things — the same reason I play guitar, tinker with electronics, and spend way too long picking the right typeface. Based in Canton, Ohio, I'm drawn to problems that sit at the intersection of craft and practicality.

When I'm not writing code, you'll find me chasing new skills, crossing items off a bucket list, or hunting for the best local coffee. This page is the version of me that doesn't fit on a resume.

Hobbies

What I do when I'm not writing code

  • Guitar and Music

    Playing guitar since high school — everything from blues fingerpicking to chord-heavy rock. Music is how I decompress.

  • Dungeon Mastering

    Running D&D campaigns as Dungeon Master — building worlds, driving narrative on the fly, and finding creative solutions to whatever chaos my players throw at me.

  • Problem Solving

    Puzzles, riddles, escape rooms. 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.

  • Reading

    Non-fiction mostly — history, science, psychology. Occasionally a novel when a recommendation lands hard enough.

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.

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 ship small, learn fast, and avoid the trap of building the perfect system no one is ready for.

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.

  • Ownership without silos

    I believe in having clear owners for things without anyone hoarding context or refusing to help outside their lane.

  • Craft without ego

    Good code is good code regardless of who wrote it. I'm happy to have my work improved.

My Approach to AI & Human Ingenuity

How I think about AI as a tool, not a replacement

I embrace AI as a powerful tool to enhance my work — not replace my expertise. My value lies in my ability to solve complex problems, think creatively, and deliver results that AI alone can't achieve. I use technology to work smarter, but my human insight drives the impact.