In Game Design, one of the greatest achievements is to get your player to enter flow. They need to be able to work in a problem space that they know how to navigate, that is somewhat defined, but leaves a bit of an opening for their (usually previously learned) expertise to solve the problems posed in a creative way with the means given.

In my youth I was able to consistently enter flow at will during multiple activities, but especially making games, and increasingly so as I was getting better at it.

That eroded away with time, and these days it's extremely rare I find myself on the other side of a flow state. I think it's because I have much more on my mind these days, so I don't allow myself to really fully commit to something for a longer while. So I feel you on the having to defend it aspect, but for me it wasn't really LLMs that prompted it. It's more growing up and extraneous circumstances.

Basically as soon as I got a real job in tech, and the business aspects trumped every other consideration, creativity went out the window, and there's only the occasional mildly interesting problem to solve. In contract work you are rarely incentivized for doing the best possible job. Doing a middle of the road job yields more billable hours. And that's just not an interesting problem to me.

So I find flow elsewhere in my spare time, as rare as it may be. But it may be high time for me to condition myself a bit to allow myself enter flow more often again.

(Btw. the colophon on your website has a typo. The font is called Inter.)

Really couldn't say it better. My experience is less LLM related and I rarely use them. When I do use LLMs it makes me stressed because things move so quickly and I know I'm just glancing over text/details rather than initiating the thought myself. One of the parts of professional software development I love the most is flow state. I'm mostly doing PM work now and there's rarely any flow state - or if there is it's short lived like maybe half an hour. Thanks for the share.