Why Engineers Resist Selling (and Why That Costs Them)

Articulate honestly the specific personal — not just professional — cost you have paid for refusing to learn how to sell yourself, and emerge with internal motivation strong enough that the next 10-14 months don't require willpower to sustain. This is the git blame step. Before any refactor, you read the commit history to understand why the code is the way it is. Same here: the rationalizations you carry — the work speaks for itself, selling is for bullshitters, I'd rather just build — are commits with messages like "WIP" and "fix later." They hide the real reason your behavior is shaped this way. Module 0 is the part where you read your own commit history, find the original feat: avoid selling from somewhere around your first job, and decide it's time for a major version bump. The whole curriculum is the refactor. The 1,500-word essay is the changelog entry that justifies the bump. There is a deeper analogy worth carrying. You have spent years learning to make Ruby code do exactly what you want, with passing tests, idempotent APIs, clean schemas. Selling is the same discipline applied to humans — you are designing a small interaction (a sentence, a pitch, a paragraph) so that a human reliably exits in the state you intended (curious, persuaded, willing to act). It is API design with one important difference: the human's response is not deterministic, so the discipline becomes one of expected value over many attempts rather than guaranteed correctness on each call. Same skill as designing a Sidekiq retry policy — you cannot guarantee the worker succeeds, but you can guarantee that across N attempts the system trends toward the correct state. Selling is that, applied to influence.