I'm very much in favour of cutting down on pointless meetings and processes for processes' sake. However, I think that "just wanting to code" can be an organiz

I'm very much in favour of cutting down on pointless meetings and processes for processes' sake. However, I think that "just wanting to code" can be an organizational anti-pattern as well. Code doesn't exist in a vacuum. It's only by context that code is provided with value and meaning. If you're the only person working on the code and you know exactly what you want to achieve then just wanting to code might work. In almost any other case you have to communicate about what the code is actually supposed to do because otherwise you're likely to create wasteful instead of useful code.