u/Delta_G_Robotics

I was having the opposite problem. I would ask Codex to fix something and it would sometimes misunderstand what I wanted and just run off and change a bunch of files without any real explanation for why. I found myself doing forensics to figure out what GPT had done. So I started putting language in my agents.md to tell it to always explain and ask first unless things were trivial. I find that this usually helps because there are often a lot of extra unnecessary things that GPT wants to do and I can help to control the scope of the changes a little better.

I wonder if you're just seeing the results of lots of people with old school coding skills telling GPT to slow down a step and let's talk about it before you run off writing ten thousand lines of code.

Although I can understand why this might be annoying to the "vibe coder" crowd who just want to tell it to make something and then see results.

One one thousand, two one thousand, three one thousand, four one thousand.

I think you missed the point of what I said. You're only as smart as your closest resource. If your closest resource is a dumb AI then that's how smart you are. If your closest resource is an exhaustive documentation of the language then that's how smart you are.

But I really think you're arguing something that isn't there. Nobody mentioned AI in this post. This person was talking about trying to memorize all the commands in python.

That 's the normal mammal leg. We humans are the odd ones out for having the heel joint down on the floor.

You need to define what you want the app to run on and what you want it to do first. Probably the biggest factor here is what platform you want it to run on. Want iPhone? Probably Swift. Want Android? Kotlin maybe? Cross platform? That's Java. Want to run on your PC? Python is easy.

And then what does the program need to do? Need to do a bunch of stuff real fast? C. Want to be flexible about how to do things? Python. Want to be easy to share with a friend and they can just run it on their machine? Maybe Java is better.

So it all depends on what you want. There is no one language that is "better". It all depends on what you want to do with it.

Step by step to "go learn recursion"...

1. Google recursion
2. Start reading.
3. If you understand recursion skip step 4 and stop.
4. go learn recursion.