"My name is Jason, and I write a lot of APIs. The nickname arrived on its own and I stopped fighting it somewhere around year two. It is a better fit than it has any right to be.",
Questions I Get Asked
Some about the work, some about the bees. Everything here is genuinely something someone has asked me.
"FAQs":
"I own my clients end to end. I run the monthly planning meeting, work out what they actually need as opposed to what they first asked for, turn that into the backlog, build it, deploy it, and answer the questions afterward. I also train their teams on whatever I hand them. The code is maybe half of it.",
"I was an automotive technician, and I kept getting pulled off repairs to handle the front of the shop: the phones, the scheduling, and the conversations with customers about what was wrong and what it would cost. Eventually that became the job. The part I was best at was never the wrench, and it turned out to transfer.",
"I work AI-first. I find the gap, decide what should exist and how it ought to behave, direct the implementation with Claude Code, and own the result in production. The leverage is not typing speed. It is that one person can run the engineering for a whole agency, which is exactly what I do.",
"Not the code. It is figuring out what someone actually needs, which is often a few layers under what they first asked for. A client who says they want a report usually wants to stop worrying about something. Find that, and the build gets a lot simpler.",
"I am the only developer at a small agency, so every technical decision is mine. I also set the standards we build to, run our weekly team review, and decide what our copywriter and AI engineer are working on. Small team, wide surface area.",
"The same thing I did with a car that would not start. Stop guessing, find the actual failure point, and change one thing at a time. Most stubborn bugs are a wrong assumption made three steps earlier.",
"Laravel with Livewire and Tailwind, deployed through Forge or Laravel Cloud. I am happy in other stacks, but that is the one I am fastest in.",
"A role where the client-facing technical work is the job rather than something I do alongside everything else. Integration engineering, implementation, solutions, technical account management: the titles vary, but it is the same shape. Equally comfortable in a codebase and in a room full of stakeholders, and the roles I enjoy most need both.",
"Sometimes. Get in touch through the contact form and tell me what you are building.",
"I keep them. Also chickens, worms, a few 3D printers, and an ongoing interest in solar power. I like systems that run themselves once you get the setup right, which is probably the same instinct that makes me enjoy CI/CD pipelines.",
"It is. They are wonderfully impractical machines and I think about them more than a grown adult should.",
"Build it, take it apart, build something that was not on the box. Same reason I like this job.",