Honest Take — Before You Begin
The pattern library is going to land in a specific way: relief. "I have a name for this now" will be the dominant reaction across the patterns, and that relief is real and partly …
Build a pattern library of difficult-operator types and calibrated responses to each — diagnostic, primary response, escalation path — personalized with real examples from your own history. A pattern library is the engineering response to "every situation feels unique." It isn't unique. There are roughly ten patterns; you will encounter all of them over twenty years; calibrated responses are learnable. Same shape as a defensive-coding library — input validation, sanitization, rate limiting, escalation to a human reviewer when the input doesn't match any known-safe pattern. The ten patterns are the adversarial inputs; your response library is the validation logic; the escalation path is the route to higher authority when your handler doesn't resolve the case. And as with input handling: the most dangerous failure is misclassification, which is why the diagnostic line comes before the response line in every entry.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The pattern library is going to land in a specific way: relief. "I have a name for this now" will be the dominant reaction across the patterns, and that relief is real and partly …
Most "difficult people" advice is generic. This module makes it specific to engineering contexts and to patterns you will actually encounter — all of them, over a 20-year career. …
Approach: Essential
Approach: Essential
Approach: Essential
Approach: Important
1. Personal Pattern Library. For each of the ten patterns: (1) a two-sentence diagnostic ("you know you're dealing with this when…"); (2) primary response; (3) escalation if the p…
7 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.