I think the article is overly broad, or at least poorly titled. I've wanted to "just code" in two scenarios: 1 - as the article describes, I've been shown an

I think the article is overly broad, or at least poorly titled. I've wanted to "just code" in two scenarios: 1 - as the article describes, I've been shown an environment that is hostile or apathetic to any of my ideas. 2. When I am with a team I trust to make well-considered, well-timed, well.communicared decisions. Sure, I participate more when in planned or unplanned meetings and my interest level/enthusiasm is high, but my main value-add is to code. If others are great at their jobs I'm free to try to be great at mine. Coders are problem solvers. If the biggest "problems" are my code, then that is where I will focus. It is worth noting that we've chosen a career about programming, most of us because we enjoy it. At the start of our careers we are constantly learning, feeling accomplished, and have a amount of time to focus on coding. Over time we start contributing in less direct ways - planning features, scheduling, mentoring. The projects get bigger and more complex. We learn the "easy" parts of the craft and start wrestling with the harder, more subtle, and more long-term aspects. All good stuff that enables more pushing of that Skinner button (coding)...but we get that sense of accomplishment less and less often even as the stakes involved increase. So we yearn for the earlier days and try to recapture that feeling. We use and write tools that allow for ever-increasing efficiencies. Humans in meetings? Relatively nothing has improved in decades...it is easy to have that feel like time in a meeting is a waste. We are solution discovering junkies - don't be surprised when we try and find the high.