A central theme in Laffra’s philosophy is that engineers should treat documentation and emails with the same rigor they treat their code.
Laffra emphasizes that an engineer’s day is spent roughly 80% communicating (reading specs, writing docs, attending meetings) and only 20% actually typing code. Therefore, optimizing your communication skills yields a higher return on investment than optimizing your typing speed or learning a new syntax. communication for engineers chris laffra pdf hot
Engineers who adopt Laffra’s model stop "venting" and start "logging." A bad day at work becomes a structured post-mortem. A fight with a partner becomes a request for reproducible steps. This sounds robotic, but early adopters report the opposite: clarity reduces anxiety. A central theme in Laffra’s philosophy is that
Take Maya, a backend engineer in Austin who discovered Laffra’s notes in 2022. "I used to come home and say, ‘Work was awful.’ Now I say, ‘The build pipeline failed three times due to a race condition. I felt frustrated because my fix was rejected without a clear error message.’ My husband, a designer, actually understood." Laffra emphasizes that an engineer’s day is spent
The lifestyle shift here is from emotional diffusion to actionable vulnerability. Laffra’s engineers don’t just communicate better at work; they audit their friendships, their family dynamics, and even their own self-talk. The result? Fewer misunderstandings, more intentional downtime, and a surprising rise in what one might call "nerdy emotional intelligence."
Laffra advocates for a specific "style" of communication that mirrors good coding practices: