Who builds this
I am Mykola Hera , and I run Ruthen Systems from Canada, working remotely with manufacturers across the country. I turn the design rules a shop already applies by hand into software that produces the models, drawings, cut files and bills of materials — the same way every time, checked before it ships, and handed over with the source and the tests.
Background
CAD and fabrication practice on one side: sheet metal, weldments and plate work, the drawings and cut files that go to a laser or a brake, and the questions a shop has to answer before cutting — which face was that diameter measured on, was it rolled or bump-formed, whose K-factor is this. Software on the other: Autodesk Inventor, iLogic and the Inventor API, C# for desktop tools, TypeScript and Python for geometry, verification and data work.
The tools on this site come out of that combination. So does the habit of writing the expected answer down before running the code, and of reading a generated file back with software that did not write it.
How I work
- Acceptance cases before code. Your own past jobs, with their known-good outputs, are the test suite.
- Every output checked. A wrong flat pattern is not a bug report; it is wasted plate, wasted machine time and a part that does not fit.
- Assumptions written down. Where a value depends on your tooling — springback, bend allowance, seam — it is labelled as yours to set, never quietly assumed.
- Handed over. Source, tests, documentation and training, so the system does not need me attached to it.
- Direct. You deal with the person doing the work. If the honest answer is that automating your task is not worth the effort, you get that answer.
What this is not
Ruthen Systems is a design-automation and technical-systems practice, not a licensed professional engineering practice. Engineering decisions belong to the responsible engineer on your side; I build the software and the technical work product, verify it and document it so that person can review it. The full statement of where responsibility sits is on the Approach page.
Get in touch
The useful first message is one concrete example of the job you keep repeating — a drawing, a spreadsheet, or a plain description.
[email protected] — Usually replies within two business days.