I agree with your thinking. I don’t do a lot of coding but I need to know how the tech stack I work with functions. I use AI to write scripts that bridge gaps and server a broader purpose to the product/service I support. I liken AI with coding like a mechanic would replacing a part on a car. A mechanic needs to know how a transmission works and how to install a new one—they don’t need to know how to build a transmission though.
That's a good way of putting it. It also shows why it's good to break code into smaller, side-effect free functions. The more you can keep your code in digestible parts, the easier it is to hand them off to mechanics/LLMs
I agree with your thinking. I don’t do a lot of coding but I need to know how the tech stack I work with functions. I use AI to write scripts that bridge gaps and server a broader purpose to the product/service I support. I liken AI with coding like a mechanic would replacing a part on a car. A mechanic needs to know how a transmission works and how to install a new one—they don’t need to know how to build a transmission though.
That's a good way of putting it. It also shows why it's good to break code into smaller, side-effect free functions. The more you can keep your code in digestible parts, the easier it is to hand them off to mechanics/LLMs
Glad you agree. I’m still a novice but it works for me.