Nice way of gatekeeping "flow state of programmers", considering I have been a software engineer for the past 2 decades. So I have experienced quite some flow states in my life, and this is no different.
Not gatekeeping, just pointing out that they're different activities with very different experiences. What you're talking about and what the article is talking about are different things.
When using ML tools you have no deep understanding of the behavior of the program, since you don't understand the generated code. If you bother to review the code, that is a huge context switch from anything you were doing previously. This doesn't happen during deeply focused programming sessions.
You may have been a software engineer for decades without ever experiencing the programming flow state. I'm not passing judgement.
imiric|6 months ago
When using ML tools you have no deep understanding of the behavior of the program, since you don't understand the generated code. If you bother to review the code, that is a huge context switch from anything you were doing previously. This doesn't happen during deeply focused programming sessions.
You may have been a software engineer for decades without ever experiencing the programming flow state. I'm not passing judgement.