Dispatches from the 1Month experiment — posted on LinkedIn as it
happened, wins and dead ends included.
“The risk for a senior engineering leader isn’t falling behind on strategy.
It’s quietly losing touch with how the work actually gets done — and starting
to lead from nostalgia instead of fluency.”
So I built. Seven production apps in under six months, solo, with AI — across
iOS, Android, watchOS, macOS, and web.
“AI amplifies a sharp spec or a vague one at the same speed.
The spec is your real IP now.”
Part 1 of the manager’s AI playbook — set the foundation: explore before you
decide, make clarity the multiplier, keep architecture human.
“Take one model’s plan to a rival and make it poke holes.
‘Claude Code says do X’ is a hypothesis, not a verdict.”
Part 2 — run AI as a system: match the model to the task, pit models against
each other, run a token economy, layer your instructions.
“The scarce skill is no longer typing the code. It’s judging what came back.”
Part 3 — hold the quality line: raise the review bar, own hardening explicitly
(AI ships the happy path), and institutionalize audits — quality as a standing
ritual, not a one-time gate.
“A ranking is a decision. A list is not.”
Part 4, the finale — ship and decide: force-rank with AI, instrument and let
real usage set priorities, and lead the “no.” The whole playbook: four phases,
13 rules.
“I built my projects a brain. Its first act was calling me a liar.
(Technically, it called my documentation a liar.)”
How a 12-project solo portfolio got a shared, git-versioned memory — and immediately caught
confident falsehoods the docs had been telling for months. The rule that emerged: primary evidence
wins; docs are just claims.