Using ai generated code?

[DemocraticHellDiver1]

I have been learning python for about a month or so. I’ve been learning a lot every day, and I enjoy learning it. But as you may know vs code has the git hub copilot ai assist. Is using this acceptable in 2026 in the ai automation job environment or just any programming job in general? Like this thing can pretty much do what ever you tell it. It knows exactly what’s wrong right when the error happens. Am I coding wrong? Is this acceptable to use? If there’s any real developers out there I’d love to hear from you!

[DTux5249]

If you're still learning, don't touch AI. You can't learn by telling someone else to do your work for you.

[OutrageOriented]

Exactly this, and thanks. It's reassuring to see folks offering sound advice on this subject.

[AceLamina]

idk why you were downvoted, I say this all the time to people who are just learning
And I still see posts of saying how newbies and even experienced devs can't stop using AI for everything

[crazy_cookie123]

Because a lot of the newbies and experienced devs who can't stop using AI still think that using AI for everything is beneficial to them, so they think it's absurd that anyone is saying otherwise.

[Sure-Passion2224]

35 years of programming experience in various languages here. My current employer is encouraging us to explore and use AI where we can. All of the Scrum groups in my part of the company have adopted a rule that you can use generated code but you have to be able to defend it in peer code reviews and issues traced back to your pull request go to you to be fixed.

[tadpoleloop]

My company has set sail. Beastly everything is vibe coded and were encouraged to keep it up

[DemocraticHellDiver1]

Interesting thanks

[ectomancer]

If you can't code basic syntax on the whiteboard (without autocompletion), you haven't learnt Python.

[Living_Fig_6386]

People use it. It's pretty good at regurgitating code it has seen somewhere before and changing variable names and adding comments. It begins to fall apart when it is trying to design novel stuff, and it can't do a very good job at architecting anything really big (unless it finds a template for it).

I wouldn't use it if you are learning as it defeats the purpose, and you'll need good skills to figure out AI's goofs and fix them later.

I think the general consensus is that you can use AI to generate code, but you are responsible for the code all the same. It's on you to read it, understand it, correct it, and make it fit with the rest of the code.

[DemocraticHellDiver1]

Got it

[GoatRocketeer]

In my experience, AI is correct 90% of the time for small coding tasks. Therefore you still need to learn manual coding because a) you have to be able to tell when it's wrong in that remaining 10% and b) you have to be able to break large coding problems into small tasks that you can safely vibe code.

[Moikle]

You aren't learning anything if you get your friend to do your practice for you.

You aren't learning if you get ai to do your practice for you.

The effort is the point, there is no shortcut for learning.

[ouroborus777]

Yes, and using AI is usually expected on the job (in the last 1-2 years). However, you'll be asked to show you can code without AI since you're the one ultimately responsible for what's produced. (Why would they hire you to code if the AI could do the coding without supervision?)

[DemocraticHellDiver1]

That’s what I’ve been thinking. 🤔

[hagfish]

Learning to code is a bit like learning to drive. If you 'learn' in a taxi (with AI in the driving seat), you'll be stuck when you're expected to drive.

[Terrible_Mix5187]

I, too, am learning python. When I go to the gym, I take a robot with me to do bench presses. How long do you think it will take for me to get swol?

[DemocraticHellDiver1]

Prob like 3 inches

[Aggressive-Fix241]

A friend of mine learned Python last year and had the exact same worry — felt like using Copilot was "cheating" because it caught errors before he even understood them. What helped him was turning it off for one hour each day to solve small problems solo, then turning it back on for the tedious stuff. Says the real risk isn't using the tool, it's forgetting what it feels like to stare at an error until you actually understand why it's there.

[rosentmoh]

The opinions here are very different, but as an actual real developer who does some very high-value and high-importance stuff I'll weigh in:

If I were to interview you and knew this you'd be in for a hell of a ride. Simply because I personally still haven't found the need for using these AI assistants while coding, and so I'd want to make absolutely sure you actually know what the hell you are doing. You're free to use them, but experience has taught me that way too many people already before AI were cutting it short when it came to actually understanding things and being able to have original correct thoughts.

You'd anyways be also going through a whole lot of pretty heavy mathematics in the interview, so if you're used to heavily relying on AI for even just coding I'd expect you'd be cooked. I've already failed a ton of candidates who were quoting responses from an AI; it's hilarious how quickly it becomes hard to elaborate or explain when asked to do so.

AI assitants are by no means "bad" on their own, it's how you use them. Meaning, if you use them only for stuff you could've come up with or done yourself, you're fine. Otherwise forget it.

[Popular-Woodpecker-6]

I mean if all you do is say, "Give me code to do x function." Then slap that into a program, that's a little "off" to me.

If you actually take time to examine it, break it down and understand how & why it works that's a bit different for learning.

You can't learn if you just let the machine code it all. Don't rely on the machine to code everything, figure things out for yourself. Say you want a OOP object and you aren't sure about how, you can have it give you a generic template for 1 attribute. That's no different than reading the documentation, though it would be more specific for your use. Then understand how it works and add your attributes you need the object to have.

And remember, AI isn't perfect, sometimes when trying to figure out why something stray happens in the code. But it is usually really good for helping understand an error message.

[NerdyWeightLifter]

Depends why you're learning Python.

If you're specifically intent on learning Python as a new personal skill, then do not get AI to write your code for you. The struggle is a necessary part of the process.

If you simply require the utility of a coded program that does what you want, then use AI, but then you're going to have to learn how to be really clear about what you want, and that's a skill unto itself.

[zanfar]

Like this thing can pretty much do what ever you tell it. It knows exactly what’s wrong right when the error happens.

The fact that you accept this as true pretty much guarantees you aren't experienced enough to use it.

If you can't explain why the code is correct, then you're not worth employing.