How I work
One person does all of this. Method matters more than headcount. Three rules.
Three rules
I measure instead of guessing
Numbers here come from running the thing, not estimating. If I could not measure it, I say so.
I check what already exists first
Most problems are a setting in software you already pay for. Finding that takes an hour. Building a replacement takes weeks.
I test against reality, not against my own assumptions
A build that compiles is not a build that works. A passing test from a guess proves nothing. I check the finished artifact.
What I work in
Tools are means, not the point. You should know what I can reach for.
- 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
- Data & docs
- JSON/CSV pipelines · PDF and document generation · reporting
- Practice
- Automated test suites · mutation testing · profiling · DNS and mail configuration
- Trade
- Carpentry · repairs · installation · fabrication · hauling
What you get, in writing
Every engagement ends in a written document. Same shape every time. Five parts:
Findings
What I examined and what I found, including what was already working.
What is already paid for
Unused capability in software already on the bill, listed before anything new.
Recommendation, costed
What to do, in priority order, with cost and time on each item.
What I could not verify
Assumptions I could not test, named explicitly.
The immediate next step
One thing that can be started this week, whether or not you engage me to do it.
Call
Fifteen minutes. If nothing is worth chasing, I say so.
Call or text 419-617-5226zty@zed-tech.net