HERO
Software and field engineering · East Tennessee
Scores are a self-assessment and should be read as one. The evidence beneath each is not: every line names work that exists and can be checked.
Capture
A lightweight approximate operator model. Drag with a mouse or finger to rotate it; scroll or pinch to use the controlled zoom.
Disciplines
Eight capabilities across four areas. Four of them involve no computer at all.
Field work
The half of the business that arrives with tools
The handyman side of zedTECH: drywall, doors, fixtures, decks, assembly, hauling and clear-outs. 135 job requests came through the account in its first five weeks.
Carpentry and welded steel, and a 30-page build plan carrying a dimensioned drawing at every step with two routes through it.
Software
The half that runs once everyone has gone home
A quoting bot that reads real job requests, prices them and replies — running unattended, behind 178 automated tests.
Six languages in regular use. Desktop applications, browser games written with no engine underneath, and command-line tooling.
Diagnosis
Establishing what is actually wrong before anything is touched
A whole-PC diagnostic built around suppressing false alarms rather than maximising test count, and a field-operations audit that found the tools were already paid for and switched off.
Inspecting the binary a build produced instead of trusting its exit code, and mutation-testing suites to find the tests that cannot fail.
Client work
The part that determines whether I am hired a second time
Real jobs priced off a rate card and quoted back the same day, with the number holding unless the scope moves.
One person from the quote to the last screw. No subcontracting, no handoff, and nobody else to explain the job to.
Equipment
What is in use on both sides of the business.
- ON THE VAN
- Welder · saws · router · drills · hand tools · ladders · truck and trailer
- TRADES
- Carpentry · steel · drywall · fixtures · assembly · hauling and site clearance
- LANGUAGES
- Python · PowerShell · JavaScript · GDScript · C++ · C#
- PLATFORMS
- Windows internals · WMI/CIM · Win32 · web · Godot 4
- AUTOMATION
- Make · Zapier · n8n · CRM and calendar APIs · webhooks
- INSTRUMENTS
- Profilers · test harnesses · mutation testing · DNS and mail tooling
Operating principles
How the work is conducted, stated so it can be held against me.
Existing tools are checked first
Before anything is proposed, I establish whether the capability is already present and unused in software you are paying for. On my own field business, that was the finding.
A passing test is a claim, not a result
Build output is inspected against the source that produced it. I have shipped a build that compiled cleanly, reported success, and silently contained none of the changes.
Both halves, one contractor
The person who scopes the work performs it. There is no subcontracting, no handover, and no second party to brief.
An honest negative is a deliverable
If there is nothing worth automating, that is the finding, and the report is delivered and charged for on the same terms as any other.
The assumptions are stated
Where a recommendation rests on something I could not verify, the limitation is named in the document rather than omitted from it.
Work record
6 active, 11 delivered, drawn from the same record as the projects index so the two cannot disagree.
Engage zedTECH
Both halves of the business reach the same number.
Call or text 419-617-5226zty@zed-tech.net