Kyle
Taylor.

I’ve been making things since before I knew what to call it — taking apart electronics I shouldn’t have, drawing floor plans for rooms I’d never build, writing small scripts to automate things that probably didn’t need automating.

At some point that turned into a career. I work across the full stack — software, AI systems, hardware — but I don’t think of myself as a developer or an engineer in the traditional sense. The label I keep coming back to is creative engineer: someone who uses technical tools to make things that didn’t exist before, and who cares as much about how something feels as how it works.

Most of what I build lives here in the Lab — small experiments, useful tools, half-finished ideas that grew into something interesting. I publish everything. Not because it’s all good, but because I think the process of making things is worth documenting. Shipping beats perfecting.

When I’m not writing code I’m usually soldering something, reading about something I don’t understand yet, or figuring out how to put a camera on a robot. If any of that sounds like your kind of thing — let’s talk.

"Shipping beats perfecting. Documentation beats memory. Open beats closed."

— The rules I try to follow