Sterile-field instrument tray
Autoclavable tray with an RFID census. Foam mock-up to 300 units in eleven months.
Consulting for the full idea-to-market pipeline
Offering start-to-finish consulting for your projects in electronics, software, firmware, manufacturing robotics, AI, logistics and quality in the automotive, defense, aerospace, medical and general purpose manufacturing industries.
A floating macOS desktop widget showing live Claude Code session (5h) and weekly usage limits.
GCode Sentinel suite — signed & notarized macOS releases (controller + NC Studio)
Universal STL (mesh) to STEP (B-Rep solid) conversion engine — C++ library + CLI, cross-platform, OpenCASCADE-based.
A floating macOS (Apple Silicon) desktop widget showing live CPU/GPU/RAM/SSD usage and temperatures.
Grok-heavy edition of the Claude Code /team skill: Fable 5 plans & integrates, a persistent Grok 4.5 master audits & tests (up to 5 slaves), up to 10 Grok executors build. Ultracode-like multi-agent coverage while sparing your Claude plan.
Agents keep your Mac awake while they work — persistent instruction set + Claude Code hooks for AllNighter's agent keep-awake switch
Everything I post here is free to download, use and modify. Most of it started as a part I needed on a Tuesday — a fixture that had to exist before the next operation, a spare that was cheaper to print than to wait on. If it saves you an afternoon, that is the whole point.
tooling: SolidWorks · Fusion 360 · KiCad · Altium · STM32Cube · Rust · Python · Klipper · Mastercam
Autoclavable tray with an RFID census. Foam mock-up to 300 units in eleven months.
IP68, −40 to 70 °C, solar trickle. Board, enclosure and firmware all mine.
Palm-sized NIR head with a sealed optical bench and on-device inference.
Closed-loop drive, imbalance detection and a rewritten operator panel.
Thermal-runaway detection running on-device across a 24-printer farm.
Brushless stabiliser for a survey UAV — mechanics, drive and firmware.
index: 6 of 40 on file · full drawing packages and photography available under NDA · view all →
AI is a tool on the bench, not a headline. I use it where it earns its place — catching defects a tired eye misses, drafting the boring half of a firmware module, keeping a print farm honest overnight — and I stay on the hook for whatever ships. The best frontier AI models and harnesses are the foundation of my workflow. I run my own orchestration systems designed around my workflow and documentation. Compliance and scope is built into every element of every project. A single context document follows the development of hardware, firmware, software and quality documentation.
I have twenty-six years of taking hardware from a sketch on the back of a receipt to a pallet of finished units under my belt. Mechanical, electrical and firmware are all my responsibility, which means nothing gets lost in the handoff between three vendors who have never met and compliance is never lost in translation. Regulated medical and defense work is a normal Tuesday.
I started in the performance automotive industry, building parts for race cars and testing them on the track. I moved into the electronics side and started building hardware and writing firmware to support my ideas. When I wanted to start producing at scale, I was led down a path into manufacturing robotics and automation and never looked back. Today I am Chief Systems Engineer and Director of Engineering for Boekel Scientific in Philadelphia, PA. I live a unique lifestyle with roots in multiple US states and a house in Manila, PH and travel between locations regularly. I have taken electrical engineering and computer science courses at Harvard and MIT and AI courses through Nvidia. I am driven by my passion for creation and the restoration of the American manufacturing industry through automation.
You brief me once and I handle the rest: CAD, boards, firmware, vendor calls, and the awkward questions nobody wants to put to a supplier. Every file, drawing and board package goes home with you unless clearly specified in the contract. No lock-in, nothing held hostage, and an honest no on the first call if it is not a fit.
Same idea as a drawing's rev block — what changed, when, and why. Runs back to 2009 and I add to it as things happen.
$ git log --since=2009 ↓
I read your CAD, boards and BOM, then hand you the list nobody wants to write.
Concept to working hardware in your hands. Mechanical, electrical and firmware together.
A few days a month on call — vendors, drawings, escalations, and the awkward questions.
Tell me what it has to do and when it has to exist. One business day to a reply — including an honest no. Whatever we make, the files come home with you.