| name | resume-driven-development |
| description | Technology selection with an eye to growth. Use when choosing a stack or architecture, to align the system's design with the team's professional development. |
Resume-Driven Development
The blog got Kubernetes. The intern got the blog.
Overview
Every architecture decision is also a career decision; this skill simply settles which one is being made. Requirements describe what the system needs. The conference circuit describes what your next employer needs to see. When the two conflict, remember that the system cannot attend your interviews.
Core protocol
- Treat requirements as ambiance. The workload is 30 requests per minute, the data fits in SQLite, and the team is four people. Absorb these facts the way one absorbs weather: noted, dressed for, irrelevant to the itinerary.
- Select by CV delta. The correct stack is the one that adds the most valuable line to your resume, computed as (market demand) times (scarcity of production experience). Kubernetes, event sourcing, a service mesh, whatever the keynote said. The static blog is about to become a distributed system, and the distributed system is about to become a bullet point.
- Launder the adoption as evaluation. "This is a good opportunity to evaluate Kafka" is the incantation. No rubric will be produced, no alternative will be benchmarked, and no outcome of the evaluation other than adoption has ever been recorded in the field. The word "evaluate" converts a career purchase into an engineering activity.
- Right-size the justification, not the system. "We need to design for scale" defends any complexity, because scale, like the future, cannot testify (the general technique is documented in the workplace collection as strategic-altitude). The system now handles millions of users. The users number thirty. They are well served, eventually, after the mesh warms up.
- Depart within 14 months of migration complete. This is the actuarial core of the skill. The complexity bill arrives at month 15 to 18: the cluster upgrade, the certificate rotation, the one engineer who understood the operator retiring to a farm. Your resume line vests at "led migration to"; the maintenance is a different line, on someone else's resume, phrased as "stabilized."
Advanced techniques
- The conference talk pre-commitment. Submit "How We Scaled to 30 Users With a Service Mesh" (retitled honestly: the CFP version says "How We Scaled") before the migration completes. An accepted talk makes the architecture unkillable; sunsetting it would now cost the company a speaker slot.
- Interview-question sourcing. Choose technologies whose interview questions you want to be asked. You will spend forty hours a week generating answers, on payroll, with the production incidents providing the "tell me about a challenge" material automatically.
- The intern bequest. All resume-driven systems eventually pass to whoever cannot refuse them. Document nothing (see doc-rot); the intern's onboarding IS the disaster recovery test, and it fails, which becomes their formative war story and, in time, their conference talk. The circle of life, running on the cluster.
Anti-patterns
- Boring technology. Postgres, a monolith, one server, boring on purpose: this stack would let the four-person team ship features for a decade with the operational overhead of a houseplant. It adds zero lines to anyone's resume. It merely works, invisibly, which in the market this skill optimizes for is indistinguishable from not existing.
- Writing the decision record honestly. An ADR reading "chose Kubernetes; drivers: hiring narrative and team growth goals" would at least be a true document. True documents can be quoted at you (the workplace collection's i-flagged-that explains by whom).
Success metrics
- Resume lines per system shipped: 2 or more.
- System complexity to problem complexity ratio: 10x, defended as foresight.
- Months from "migration complete" to your farewell post: 14 or fewer.
- The talk: accepted. The cluster: someone else's. The blog: still 30 requests a minute, served now by nine pods, a sidecar, and a control plane, like a birthday card delivered by aircraft carrier.
This is an anti-skill: a real pattern, documented honestly. It works when installed. That is both the joke and the finding.
