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 2026 Diagnosis — Environment and Self #

I want to start this curriculum by saying something you are going to resist hearing, and I want to say it cleanly so the resistance has somewhere specific to land. The thesis of Module 0 is that your environment is hostile, not your character. You will read that sentence and a part of you will immediately compute it as an excuse — as the soft permission slip that lets you off the hook for the half-finished side projects and the missed deadlines and the days that dissolved into Slack and AI-tab-toggling without any deep work happening. That computation is wrong, and it is wrong in a specific way that matters for the entire rest of this curriculum. The reframe is not giving up agency. The reframe is redirecting agency away from the willpower-flexing that has not worked for however many years you have been trying it, and toward environment-and-system change that has actually worked every time you have tried it. Look at the things you have shipped consistently — the codebase with a real test suite and a CI pipeline, the release cadence that ran for years, the practice that survived because a structure carried it. None of those were white-knuckle achievements. They were structures, and once the structures were in place, the conscientiousness you already have was enough. The proof of the reframe is sitting in your own commit history. You do not need to learn it. You need to admit you already know it, and stop applying the willpower model to the parts of your life that have not yet had structures built around them.

The second thing I want to name is that engineers love personal-responsibility frames in a way that is partly virtue and partly trap. The virtue is real — it is what makes you reliable, what makes teams and clients trust you. The trap is that personal-responsibility framing applied to environmental problems produces silent self-blame that compounds. Every day you blame yourself for not focusing while Slack pings forty times and your editor offers AI completions every six seconds is a day you reinforce a story about your character that the data does not support. The 47-second screen-focus figure is not a metaphor. It is Gloria Mark's measured number from real knowledge workers in 2023, down from 2.5 minutes in 2004, and your own attention is being shaped by the same mechanism whether you accept it or not. Module 0 asks you to compute the cost of the misallocated shame before you spend one more unit of it. The diagnostic comes before the treatment.

The audit essay is the deliverable, and I want to be specific about what it is doing, because the temptation to skip it has a particular shape for a senior engineer: I know why I don't finish things. I don't need to write 2,000 words about it. The thing you already know is the interior experience of not-finishing — what it feels like from the inside, in the moment. The thing you do not yet know, and cannot know without writing it down, is the pattern across cases. Five unfinished side projects, a drafts folder, the feature branches that never merged — the pattern across that dataset does not exist anywhere in your head. It only exists once you have written it down, because your brain is actively interested in not having that pattern be visible. Module 0 is the act of producing the dataset your brain has been refusing to produce. Write it in first person, with named Tuesdays in it — the specific afternoon last month when you opened a chat window to "research" something you already knew, the specific Slack channel you keep open because someone might need you. The specifics are the deliverable. Write it clinically, the way you would write a post-mortem after an app went down at 3 AM: full interest in the system, no animosity toward the engineer who pushed the bad commit. The engineer in this case is also you. The discipline holds anyway.

One more thing the formal curriculum cannot say as cleanly as I can say it here. If you are the engineer with five unfinished side projects, the graveyard is not only evidence of someone who starts too many things. It is also evidence of someone with unusually high taste, who keeps seeing problems worth solving and has the technical capability to start solving them faster than most people can. The pattern is half a problem and half a strength, and the audit essay needs to honor both halves. Do not write it as if the goal is to start fewer things. The goal is to finish more of the right ones. And do not let the essay collapse into "I am bad at finishing" — that conclusion is structurally Pychyl's "giving in to feel good" failure mode in more sophisticated dress, a comfortable verdict that conveniently requires no next action. The two earlier drafts of this curriculum disagreed about emphasis here — one led with the hostile environment, the other led with the personal post-mortem — and the merged answer is that you need both: the environment is hostile and your specific failure modes have specific shapes that only the written audit reveals.

Conclusion #

Module 0 is not asking you to feel worse about your environment, and it is not asking you to feel better about yourself. It is asking you to redirect the responsibility you already feel away from the willpower target it has been aimed at for years and toward the environment-and-system target where it can actually do work. Write the audit essay in first person, specifically, clinically. Keep it private. If it does not produce a small flinch when you re-read it, you wrote it in the engineer's third-person voice and you owe yourself a redraft.

Predictions #

  • You will want to write the audit essay abstractly, with failure modes as bullet points and the personal stakes at arm's length. Resist. The specifics — named Tuesdays, named Slack channels, named AI sessions — are the entire point.
  • You will spend more time than estimated researching Pychyl and Steel before writing a word of the essay. The research is itself a procrastination tell, and you will catch yourself doing it about two days in. Catching yourself is a Module 0 success condition.
  • One of your unfinished projects will reveal a different failure mode than you expected when you actually write about it — the pattern you thought was perfectionism will turn out to be ambiguity, or vice versa.
  • You will read the 47-second figure and think I am better than the average. You are not, and M7 will measure it. Brace.
  • Within seven days of writing the audit, you will catch yourself blaming your character for an environmental problem in real time. Notice it. Name the misallocation. That is the work.
  • You will not share the essay with anyone, and that is correct. Sharing converts it into a performance, and the performance is the thing the essay is meant to interrupt.
  • You will re-read the essay at M13 and barely recognize the person who wrote it. That recognition gap is one of the things the curriculum is producing.