I like turning ideas into things that survive contact with reality.

The IT part explains some of this

My background is in IT infrastructure, so even the hobby projects tend to become little systems: version it, test it, work out what broke, keep a record of why it changed, and try not to repeat the expensive mistake.

I also have a fairly unreasonable interest in AI and how far one person can push an idea when the tools become a force multiplier. D4Maker is where I test that properly — physical ideas through 3D printing, digital ideas through games and tools, and apparently an entire website because “I should make a bag tag” got slightly out of hand.

AI is the multiplier, not the final judge

AI can help turn the half-formed thought into a concept, code, CAD direction, checklist or next experiment much faster than I could alone. But the print still has to fit, the code still has to run and the game still has to be fun.

The interesting part for me is not pretending the AI is infallible. It is seeing how much more one person can build when the machine helps hold context, explore options and keep the boring bits moving.

What I build

3D printing is the anchor, but not the boundary. I build practical parts, parametric designs, small software tools, HueForge projects, AI-assisted experiments, music and whatever else earns a place on the bench.

I’m particularly interested in reusable systems instead of one-off files: change a name, size or fitting and generate the version you actually need.

How I build

I like the loop more than the illusion of perfection: make something, test it, work out what annoyed me, change it and test again.

If I call something print validated, I mean I have physically printed and checked it. Prototypes are labelled as prototypes. Failed versions stay useful when they explain why the next one changed.

Why the strange name?

D4N63RM0U53 is the online handle I use across maker accounts. It became the obvious umbrella because the subject matter changes, but the process usually does not: make it, test it, improve it, share the useful bits.

More than project files

The technical build journal covers what happened on the bench. Journeys covers some of what happens behind it — creativity, ADHD, lessons learned and why certain ideas keep getting pulled.

Read: Finding ADHD at Nearly 40 →

And yes, there’s an AI riding shotgun.

A lot of these projects start as half-formed ideas bouncing around my head. MakerMouse, my AI assistant, helps me grab one of those threads, turn it into something I can actually test, and remember why we changed something three versions ago.

I’m still the bloke printing the parts, breaking the parts, burning the occasional finger and deciding what works. The AI just makes it possible to follow more of the ideas far enough to become real things instead of letting them disappear into the spiderweb.