Yes. Although this article isn't about "micromanagement" in my mind. Micro-management, in software, effectively turns the programmer into a secretary taking dictation.
It's someone caring about the details of the results along with the details of the implementation, and the process, and every other factor but then hiring someone else to actually press the keys and move the mouse. It turns the task of programming from problem-solving to satisfying effectively onerous checklists of ceremonial acrobatics. There's other ways to solve that problem.
The original post is talking about debilitating flow and a structure (stemming from a culture and engagement) that is fundamentally destructive.