I'm a self-taught maker who picks up projects across hardware and software. No formal training, no special background — just curiosity and an internet connection. If I can figure this stuff out, so can you.
Circuits, sensors, lasers — I've taught myself enough to be dangerous. Most projects start with a tutorial and end somewhere I didn't expect.
Electronics · Lasers · Learning3D printing and modeling. And now subtractive manufacturing, too. I'm getting better at designing parts that actually work on the first print, but "iterate until it fits" is still the real process.
3D Printing · CAD · Prototyping · MachininingLight programming. I'm not an expert, but the internet age has made this so much easier. I can get things working — just don't look too closely at the code.
Web · ToolsModern titles and retro collecting — I've got a growing PS3 library that I'm genuinely proud of. Games are how I unwind and sometimes how I find my next project idea.
Modern · Retro · PS3 CollectorText-based multiplayer games — the original online worlds. There's something about a game that runs entirely on words and imagination that still hasn't been topped.
Text Games · Online · Old SchoolThis is what I actually do for a living. I design learning experiences and write about a wide range of topics. Teaching others how things work is one of my favorite things to do.
Writing · Teaching · Learning DesignTools, resources, and ideas that started on the job. Some solve specific workflow problems, others are just things I thought were worth building or writing about.
Browse →
The gear, tools, and equipment I use or collect. Printers, electronics, lasers, retro consoles — if it's on my desk or shelf, it might end up here.
Builds, experiments, and things I've made for myself. Hardware, software, or somewhere in between — this is where the hands-on stuff lives.
What I'm actively working on right now. Some of these will graduate to finished projects. Others might not. That's how it goes.
Short thoughts, observations, and occasional updates. The stuff that doesn't fit neatly anywhere else.
I rarely know what I'm doing when I start a project. That's the point. I pick something that seems interesting and learn whatever I need to make it work.
Google, forums, YouTube, documentation — I'm not proud. If it helps me understand something or solve a problem, I'll use it.
When I build something useful, I try to document it well. Partly for others, partly because I know I'll forget how it works in six months.
I'd rather finish something rough and improve it later than polish forever and never release it. Most of my projects have a version two for a reason.
Whether it's about a project, a shared interest, or just to say hey — I'm always happy to hear from people.