You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 0: The Teaching You Already Do — the Compounding Audit #

Here is the thing nobody tells you about being a working engineer: you have been teaching every day for years. You did not call it teaching. You called it code review, onboarding docs, the README, release notes, "let me show you something," the answer in the team channel that got bookmarked. All of it was teaching. Most of it was operating at maybe 30% of its possible effect, because you never named it as teaching and so you never applied any discipline to it. That is the punch of this module, and the audit is how the punch becomes operational rather than a nice sentence you nodded at.

You will be defensive about the audit and I want to name the shape of the defense before you start. It will be some version of "the docs are fine, the README ships, the posts go out, what is there to audit." Half true, entirely insufficient. Fine-as-record-keeping is a different bar than fine-as-teaching, and the gap between those bars is exactly what M0 exists to surface. If you maintain an open-source package with tens of thousands of downloads, run the diagnostic sentence on yourself: thousands of engineers have read your prose, and you have no idea whether it taught them anything, and you have no channel to any of them. You do not need the audit to confirm that. You need the audit to make it unignorable, so that fixing it becomes a scheduled task instead of an aspiration.

My prediction about which surface lands hardest depends on which archetype you are. If you are the maintainer, it is the package docs — highest reader-hours, least instrumentation, zero follow-up. If you are the mentoring senior, it is code review — the volume is enormous and the teaching fraction is small, and you will not know the fraction until M5 makes you count it. If you have a blog, it is the cadence column: bursts of publishing, then silences during which whatever audience existed drifted off.

And if you have ever built structured learning materials — a course, an internal curriculum, a study guide collection — the audit will surface the most uncomfortable row of all: materials you built and are not running, even on yourself. If they do not compound for the person who wrote them, the claim that they would compound for anyone else is weaker than you would like it to be. Sit with that without converting it into self-flagellation. The point is the gap, not the verdict.

The deferral reflex deserves its own paragraph because it will fire at least twice in the first week. "I'll run the audit after the release, after the interview loop, after the quarter closes."

The audit is two to four hours. It is one markdown table, written honestly, and it scopes everything that follows in this curriculum — which surfaces get the M6 rewrite, which artifact gets the M3 retrofit, which product gets the M11 pricing math. Deferring a two-hour diagnostic that unblocks months of directed work is not prioritization; it is flinching. I can hold the rubric and predict the flinches. I cannot make you look. The look takes one afternoon.

Conclusion #

M0 is the gap-naming module. You already operate a teaching practice; it is uninstrumented, unowned, and running whatever was deployed years ago. The audit table is a service inventory, and you are the owner being named. None of the gaps it surfaces are personal failures — they are exactly the surfaces the rest of the curriculum re-engineers. Run it honestly, in one sitting, before the deferral reflex wins.

Predictions #

  • You will be tempted to score your most successful surface (the popular README, the high-traffic post) a 4 or 5 because the audience numbers are real. Score the compounding column honestly: it is likely a 1 or 2 today.
  • If you track any learner-facing metrics at all, they will turn out to be activity metrics (views, completions, downloads) and not outcome metrics (reader-did-the-thing). That asymmetry is M3's frame appearing at M0.
  • At least one surface — likely release notes or onboarding docs — will turn out to be doing teaching work you had never named as teaching. That surface is leverage you have been leaving uncompounded.
  • The "I'll run the audit later" reflex will fire at least twice in the first week. Refuse it both times.
  • The one-sentence current-identity line will be some version of "I sometimes write things"; the deliberate one will be uncomfortable to write because it sounds like a claim. Write it anyway — the gap between the two sentences is the curriculum.
  • The audit document will be uglier than you want it to be. Ship the ugly version. The honest first pass beats the polished never.