Building a technical-talent pipeline that can outlast its builders
A public case study in connecting selection, contribution, mentorship, public products, measurement, shared ownership, and succession.
Read the case study →
Ideas in progress
RSS feed
Working Notes
Short essays about AI systems, problem solving, mentorship, and technical education—written to clarify what I am learning while the work is still alive.
Latest notes
Anatomy of a reliable contest release
A release-safe field guide to specifications, independent solutions, adversarial submissions, generated data, automation, and human sign-off.
Use the release field guide →A technical leadership playbook
Concrete mechanisms for decision clarity, early risk communication, apprenticeship, sponsorship, recognition, and organizational memory.
Use the playbook →Increment All Divisors
An annotated AtCoder solution: reverse the divisibility order, express every operation count as an affine function, and intersect the resulting bounds.
Open the notebook →A public-safe framework for production decisions
Turn an ambiguous technical question into a reviewable choice across quality, cost, risk, delivery time, and reversibility.
Use the decision framework →How to end a technical system responsibly
A practical closeout checklist for infrastructure, cost, access, ownership, retained knowledge, and final operating state.
Use the closeout checklist →What fifteen years in the ICPC changed about how I solve problems
Reflections across competing, coaching, judging, organizing, and teaching—and what those roles reveal about the real work of problem solving.
Read the note →How to build a sustainable university competitive-programming community
An entry ramp, durable weekly rituals, leadership succession, and institutional memory matter more than one exceptional team.
Read the note →How I review an ICPC contest with a team
The scoreboard records outcomes. A useful review reconstructs decisions, failure modes, and team interactions.
Read the note →Coaching without taking ownership away from the team
A coach should make reasoning visible and feedback precise—not become the hidden fourth contestant.
Read the note →How to choose problems for deliberate practice
A four-stage sequence for isolating weaknesses, varying ideas, testing transfer, and finally adding pressure.
Read the note →From reading an editorial to owning the technique
Turn an explanation into reconstructed reasoning, independent implementation, and evidence of transfer.
Read the note →Reliable voice agents are systems problems
The model matters, but the user experiences the entire system: latency, interruptions, tools, state, evaluation, and recovery.
Read the note →Practice that compounds
A useful practice session should change how you approach the next problem, not merely add one more accepted solution to a profile.
Read the note →Mentorship is leverage, not a shortcut
Good mentorship improves the quality and timing of feedback while leaving ownership of the work with the person being mentored.
Read the note →Follow future notes
Follow new essays and book updates through the site’s RSS feed. No account, inbox signup, or tracking required.