Solomon Lee
Founder & Chief Software Architect of Tekhx
I don’t have design patterns. I have systems that survived their fifth year.
It starts with how the business runs, not with a schema. One manifest in, a whole module out, and nothing reaches production that a suite has not tried to break.
- Discover: the business, first
- Manifest: one file declares it
- Generate: schema, API, UI, tests
- Guardrails: 15 gates before push
- CI: migrations, parity
- Deploy: staging, then production
- Memory: what shipped, carried into the next manifest
Systems of record
Where a wrong number is a legal problem, not a bug ticket.
- Nine companies consolidated onto one platform, sole architect
- Reversible postings and an append-only audit trail
- Optimistic locking, so one save can never silently erase another
Agentic engineering
AI is the tool. The harness is the work.
- Manifest-driven generation: every module identical by construction
- Guardrail suites that fail the push instead of the customer
- MCP servers and cross-session agent memory, built from scratch
Platform & infrastructure
The half of the job most portfolios never mention.
- 35+ services on owned hardware with no inbound port open
- Push to staging to production, behind a gate that can refuse
- Pooling, caching, backups, metrics, and deploys that are boring
Scale & performance
Measured, not claimed.
- Payroll computation: several days down to ~5 seconds
- Page loads: 10-15s down to 1-3s across a portfolio of sites
- Blueprint validation: ~100x faster than walking the site
Stone age to high tech is not a figure of speech here. Filing cabinets to audited systems. Desktop software on one machine to nine companies running on one platform, with one author.
I have watched a business run on something I wrote alone. That does not get old, and it does not get invoiced.
Most of what I replace already works. That is the harder job. It is also the one I get.
ABL Solutions. 35+ services on hardware I own. Still the person who gets called.
“If you’re not going to do your best, you’re just spending time. I don’t spend time.”
INTJ
Systems thinker, long horizon
Efficiency-obsessed
Days to seconds, and I measured it
Family-first
Work to live, not live to work
Remote-native
Deep work, async by default
By the numbers
Scale and outcomes, not job titles