Work
Real projects and self-owned demonstrations, written the same way: problem, constraints, engineering logic, system, validation, result. Nothing here is invented, and client work appears only with written permission.
Published work
Fabrication Generator: cones, cylinders and clamps with a second implementation that checks the first
A portable Windows application that produces cutting DXF, real DWG drawings, PDF and a job record for rolled and press-brake parts — and refuses to invent the numbers it cannot know.
Result 1,078 checks across four independent methods; one datum difference with common calculators found and documented rather than hidden.
Read the case study →A fabrication geometry core and six public tools, verified three ways
The engine behind the free tools on this site: developments for cones, hoppers, profiles, bends, bolt circles and pipe cuts, exported as deterministic DXF and checked by software that had no part in writing it.
Result Every exported file audited by an independent DXF library; hand-derived golden cases; accepted in real CAD.
Read the case study →An Autodesk Inventor add-in that turns a hopper configuration into a verified release package
A parametric rectangular-transition-hopper generator for Autodesk Inventor 2026: eleven inputs become part models, an assembly, drawings, flat-pattern DXF, PDF and a bill of materials — then the package is validated and refused if any check fails.
Result 64 engine rules across eight families, with a second implementation that agrees on all seven reference sizes; flat patterns read back within the 2.5% validation gate (about 1.2% on the nominal hopper); 111 automated tests pass and every release carries a SHA-256 manifest.
Read the case study →How client work is published
Client and employer material is confidential by default. A project is published only with the client's separate written permission, and only to the level granted — an anonymous description, the industry, the company name, screenshots, metrics, or a quote. Anything not explicitly granted is not shown. Owning the code written for a client does not mean owning their drawings or business data.
Self-owned demonstrations are built on Ruthen's own time, hardware and licences, from generic inputs. They exist because the same problems recur in every shop and a demonstration can show the method without showing anyone's drawings.
Have a job worth automating?
Send one example — a drawing, a spreadsheet, or a plain description of what you keep redoing. You will get a direct answer on whether it is worth automating, including when the answer is no.