This is an excellent article but starts out with the false dichotomy of vibe vs craft programming.

An alternate term is starting to appear, flow coding or agentic coding, where the tool is supervised and direced into coding precise areas under human architectural control, with all the programmer understanding that entails.

The author hints at this idea toward the end and likens it to a skilled builder who uses tools to make a precise part.

> The author hints at this idea toward the end and likens it to a skilled builder who uses tools to make a precise part.

Translation: "Please guys, I'm a real engineer too! Vibe coding is for kids, I'm an _Agentic_ coder, remember when flow state was a thing, coding with ai is _flow_ coding"

This is an interesting observation.

The difference between code completion, intellisense and AI coding, is that code completion merely gives you the name of a variable or a function, while AI coding thinks for you, which is really bad.

That's why I despise Copilot and other AI tools that are embedded in IDEs. I'm OK with ChatGPT because it is in a different window and I'm much inclined to use it -- and when I use it I try not to let ChatGPT think for me, but things like Copilot tries to get into my coding.