[codyb]

Call me crazy, but my guess is that that may not have been able to happen without the decade of experience it took you to get to the Staff level engineering position at a big tech company which has enabled you to gain the skills required to review the AI code you're producing properly.

[senordevnyc]

Totally true. But that's also a different point than "But I love using my knives!"

[BruceEel]

I thought it's interesting that GPT5's comments (on prompting it for feedback on the article) seem to overlap with some of the points you guys made:

   My [GPT5's -poster's note] take / Reflections
   
   I find the article a useful provocation: 
   it asks us to reflect on what we value in being programmers.
   
   It’s not anti-AI per se, but it is anti-losing-the-core craft.
   
   For someone in your position (in *redacted* / Europe) 
   it raises questions about what kind of programming work you want: 
   deep, challenging, craft-oriented, or more tool/AI mediated.
   
   It might also suggest you think about building skills 
   that are robust to automation: e.g., architecture, 
   critical thinking, complex problem solving, domain knowledge.
   
   The identity crisis is less about “will we have programmers” and 
   more “what shapes will programming roles take”.

[codyb]

Absolutely. But, what if the point of using the knives, is to be able to understand how to use the machines which can use knives for us, and if we're not replicating the learning part, where do we end up?