>>105742653
>you basically first need to understand the mechanics of programming and technology to phrase it in digestible steps to take and by doing so
Not true, see this:
>>105740768
>you "reduce" the ai to autocomplete and dumb yourself down along the way
It's not an autocomplete, it's like having a competent junior do most of the tasks for you. You don't trust him unconditionally, but he saves you a lot of time once you provide him with a proper structure to follow.
>The ai is effectively bottlenecked by you and produces no original thought or understanding.
True. That's why point 1 is so important. It's garbage in, garbage out. AI isn't here to provide you with 'original' thoughts, but can you really say that your idea is original when you break it down into small pieces? Humans are like that too. Most of the time, we're simply reusing things made by people before us.
>Why do I need an IDE or see code at all? Why do I need the concept of a CI/CD pipeline? Why is a background in programming needed? Doesn't that miss the mark? You literally dig yourself into a hole whenever you rely on something external, time and time again.
Why do I need tools for my job? To make things easier for me. I could carve wood with my bare hands, but I would be a hundred times more efficient if I used electric tools for that. It's the same concept here. You're not programming for the sake of programming (unless you're a hobbyist), but rather to deliver a product. If you can reduce the time it takes to deliver that product, your company will be more profitable. From a business viewpoint, it's a no-brainer to use the latest tool for the job.
