This seems overly harsh. Poor development environments, documentation that takes too long to find anything, annoying code practices, etc. are all ways to snap yourself out of of flow.
The point of the article is that you should examine what keeps you in flow and what knocks you out, and optimize for the former.
The point of the article is that you should examine what keeps you in flow and what knocks you out, and optimize for the former.