The air in Conference Room 43 smells like ozone and stagnant espresso. Ben T.J. stands by the floor-to-ceiling window, his reflection ghostly against the gray city skyline, watching a team of 13 engineers debate the merits of a specific naming convention for a database column that hasn’t been created yet. They have been in this room for three hours. This project has been ‘in development’ for 163 days. They have yet to deploy a single line of production code. It is a masterclass in the art of the perpetual start, a ballet of busywork where everyone is sweating and nobody is moving. Ben T.J. has seen this in exactly 33 different companies this year alone. He calls it the ‘Activity Narcotic.’
I cleared my browser cache four times this morning before starting this. I did it because I felt stuck, and clearing the cache felt like doing something. It was a digital purgative, a way to convince myself that the reason the words weren’t flowing was a technical glitch rather than a creative block. We do this in our careers constantly. We clear the cache instead of writing the code. We re-organize the Trello board instead of finishing the task. We mistake the sensation of friction for the reality of progress.
The team Ben is currently observing is objectively brilliant. They have PhDs, they have
