Lampshading: A Developer’s Tool for Honest Momentum
Shawn’s recent post on lampshading borrows a TV storytelling trick and applies it to engineering teamwork. In a show, lampshading means directly acknowledging a weak plot point — saying, “yes, that’s implausible” — so the narrative can proceed without criticism. For developers, the parallel is openly telling your team or boss you don’t know a certain technology, thereby clearing the air and keeping the project moving.
This isn’t just polite; it’s a strategic move. Managers and higher-ups should lampshade anything they don’t understand, because their role centers on asking the right questions and ensuring clarity for customers and direct reports. Junior engineers, meanwhile, need the same admission to fuel their own growth.
That said, execution gets easier the further you are from the middle of the experience curve. A brand-new hire gets an automatic pass — people expect gaps. A seasoned, well-respected senior gets credit for humility, with their admission reading as relatable rather than deficient. The sweet spot in the middle is trickier, and while it would be ideal for everyone to use lampshading effectively, mid-level developers may find it harder to pull off without awkwardness.
