Matt Farrell

I enjoy building things. That's the short version.

Actually solving a problem, understanding it properly first, then figuring out the cleanest way to build it, that's what gets me going. The code itself is just the execution. The interesting part is the thinking before it.

I work primarily in C# and .NET because I like strong typing and architecture that makes sense. I care about systems that survive production, which means thinking about structure before I write code.

I've been using AI tools for a while now, they speed things up, help me think through problems, and handle the boring stuff. But they're a tool, not a replacement for knowing what you're doing.

I'm also building Looking4Players, a platform to solve a real problem (finding people to play board games with). I own the architecture, backend, and technical decisions. It's taught me more about shipping and iterating than any job has.

I'm not big on testing. I'd rather ship fast and fix what breaks than over-engineer upfront. Honestly, DevOps and runtime instability frustrate me more than the building itself.

Outside work: board games (obviously), 3D printing, hands-on projects. I'm social and tend to end up mentoring or helping others level up.

Currently: Building Looking4Players, printing random things on my Ender 3, and losing badly at board games.