I build things. Software, games, images, tools. If there's a way to make something from scratch or automate something that used to take forever, I'm probably already deep in it.
I'm based in Asheville, NC. By day I sell cars at a Hyundai dealership, which keeps the lights on and honestly keeps me grounded. There's something useful about spending half your life talking to real people about real problems. It makes you think differently about what you build and who you're building it for.
The other half of my brain lives here.
How I think
I'm not a purist about any one thing. I don't care if something is built in Python or JavaScript or held together with duct tape and a shell script. I care whether it works, and whether it was worth making. I gravitate toward systems that do things automatically, interfaces that feel obvious, and tools that solve a specific problem instead of ten vague ones.
I get obsessed easily. That's not a flaw I'm trying to fix. The rabbit holes are where the interesting stuff is. I've gone deep on local LLMs, Stable Diffusion pipelines, browser automation, agentic workflows, game scripting, ESP32 hardware, 3D printing, web development. And those are just the ones I can remember right now. The throughline isn't a stack. It's a pattern: find something interesting, understand it completely, then build something with it.
// the actual workflow, roughly
see interesting thing
-> read everything about it
-> break it
-> fix it
-> make something with it
-> share it or move on
What I'm good at
I'm good at starting. I know that sounds like a joke but it isn't. A lot of people stall at the idea stage and I don't. I'll have a prototype running before I've fully articulated what I'm building.
I'm good at connecting things that don't obviously belong together. Automotive CRM logic and AI-generated follow-up workflows. A terminal-themed personal site and a meme about Claude's time estimates. Game NPCs that actually negotiate like used car salespeople. These aren't random. They come from living in two worlds at once and noticing where they overlap.
I'm also decent at writing. Not in a formal sense, but in a "making something clear and a little dry and hopefully not boring" sense.
What I don't know
Plenty. I'm not a systems engineer. I haven't shipped a production SaaS or led a team through a full product cycle. My backend knowledge has gaps. There are entire corners of computer science I've only read about. I learn fast and I'm honest about where I'm fuzzy, but I'm not going to pretend I've done things I haven't.
I'm also still figuring out which of the things I build are worth turning into something real versus which ones just needed to exist for a weekend.
What I'm trying to do
Right now I have the luxury of building without pressure. My job pays the bills and doesn't follow me home, which means I can experiment freely and actually finish things instead of rushing them to market.
But I want to build with people. I like collaboration. I like the version of a project that only exists because two people with different instincts worked on it together. I'm not in a hurry, but I'm actively looking for creative and technical work. The kind where someone has a problem that needs a tool, a workflow, an experience, or something they can't quite describe yet and needs someone to figure out what it actually is.
If that sounds like something you need, I'm probably interested.
curren.dev/contact
// or just find me somewhere, I'm not hard to reach
This site
This is where I document what I'm creating, what I'm learning, and the projects worth sharing. Some of it will be polished. Most of it will be works in progress. Either way, it's real.
Welcome.
-- END OF FILE --