Managing Humans: More Biting and Humorous Tales of a Software Engineering Manager

This is an essay collection, not a treatise: the four editions collect named situations Lopp wants a manager to recognize on sight, not a single system to apply step by step.

• The one-on-one sorts into three moods that call for a different manager response: the Update, mostly harmless but not what the meeting is actually for; the Vent, where the job is to listen without problem-solving, redirecting, or comforting until it runs out [1]; and the Disaster, an emotional break where the only correct move is to contribute nothing until it passes. Lopp is explicit that the format’s function is a strategic conversation, not a status report [2].
• The Twinge is Lopp’s name for a manager’s unstructured, experience-built gut sense that a status story doesn’t add up. He treats ignoring it as a management failure, not an excusable miss [2].
• For a highly technical report (“a nerd,” in his term), Lopp’s single piece of advice is to bring calm to their chaos [2]: they want a predictable environment, because unpredictability reads to them as a world they can’t model [2], and protected, uninterrupted focus time, because that’s where the real breakthroughs happen [2].
• A reorg takes roughly four times longer than anyone expects [2], and the paranoia it produces along the way is mostly the grapevine mutating a true fact into rumor as it passes from person to person [2]. The corrective is patience and independently confirming information, not more communication.

• When a one-on-one turns into a rehash of the status you already have from the bug tracker: Lopp’s Update/Vent/Disaster read tells you that’s a sign you’re succeeding at the wrong thing. A status-only one-on-one is not a productive one for Performance management; a manager who counts it as a win misses the actual conversation available in that half hour.
• When your gut says a status update doesn’t add up but you have no evidence yet: the instinct is to wait for something concrete before acting. Lopp’s Twinge says ignoring that unstructured signal is itself the failure: it’s a habit central to Making the squishy legible, where the whole competency is catching what the numbers haven’t surfaced yet.
• When your best engineer suddenly reads as rigid or precious about small things (office assignments, meeting interruptions, tool choices): without this book you read it as difficulty. Lopp’s read is that consistency and protected focus time are the thing that lets them do the work you hired them for, and an inconsistent call from you (not the small thing itself) is what set them off.
• When a reorg is announced and the hallway chatter turns paranoid within a day: the instinct is to over-communicate to calm people down. Lopp’s corrective is that the grapevine will out-mutate any single announcement and the process will take four times longer than stated, so the intervention is patience and confirming information independently, not more meetings.