Maximizing Developer Effectiveness
Here I am, a productive developer eager to deliver maximum value to my customers and apply my innovation to company goals.<p>Open up JIRA and pick up a unit of work to produce today -- gotta stay faithful to those story points!<p>Somehow, a magic team of spherical devops in a vacuum created an environment where things are just green, predictable, and are never broken.<p>Another theoretical team of angels from a parallel universe has materialized into this one, updated all the docs, and beamed back into their universe of productivity and effectiveness.<p>Unit of work defined, I then proceed to produce it for a few hours completely uninterrupted, since if another human being were to make contact, I&#x27;d simply explode and format my hard drive, losing all my productivity.<p>It&#x27;s break time -- I ingest 2 story points of coffee and join a game of table tennis. The ball bounces back and forth without ever touching the ground. My movements are productive, and value-adding, just like my partner&#x27;s.<p>Back to producing units of work, only half a story point left (sike! no such thing as half a story point, and no such thing as &quot;left&quot;, as it&#x27;s a measure of effort, not time. Almost got you there!).<p>Git push! Automatic CI gains consciousness and validates that my work unit has no chance of causing a user to break our software. It gives me a thumbs up and discards its human shell to fade back into the ones and zeros. A QA engineer cries out in the distance.<p>A metric of my productivity is logged to the OKR database.<p>Nothing breaks, and nothing unexpected happens, as the universe is completely predictable.