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
Approximate model. Drag to rotate. Scroll or pinch to 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
Handyman side: drywall, doors, fixtures, decks, assembly, hauling. 135 job requests in the 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
Quoting bot reads real job requests, prices them, replies. Unattended. 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
Whole-PC diagnostic built to suppress false alarms, and a field audit that found paid tools 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 proposing anything, I check whether you already pay for the capability unused. That was the finding on my own field business.
A passing test is a claim, not a result
I inspect build output against the source. I have shipped a clean compile that contained none of the changes.
Both halves, one contractor
The person who scopes the work performs it. No subcontracting. No handoff.
An honest negative is a deliverable
If nothing is worth automating, that is the finding. Same terms as any other report.
The assumptions are stated
If a recommendation rests on something I could not verify, that limit is named in the document.
Work record
6 active, 11 delivered, drawn from the same record as the projects index so the two cannot disagree.