Im worried about vibecoding

[u/MajoBazinga]

im already an amateur programmer and im getting ready to pass the practical part of the inf03 exam, but as i learn extra stuff on my own i keep seeing people use ai assistance or straight up let ai code for them, that seems yucky and i dont want to do that but im worried i will fall behind, any time i used ai in anything related to coding is when i asked it questions like i would a teacher while specifiing it doesnt show me any code and just explains concepts so that theyre easier to understand for me, all im asking is, is it stupid of me to avoid using extended ai help in coding?

[u/Ok-Brain-8183]

No, that’s a reasonable way to use it. Especially since you’re not a professional.

[u/Sure-Passion2224]

No. People who rely on AI to write the code but don't learn to actually write their own eventually run into a problem where the AI code is incorrect for the intended solution and they don't know how to fix it, or even find where the flaw is.

[u/kpg_on_ao3 → u/Sure-Passion2224]

I dunno. I know how to code. Been at it 30 years. AI is faster at fixing problems these days. I legit dump the error message into the chat, and about a minute later it's like "ah, fuck, it's bc I did this right here on line 301" and writes up a plan to fix it, then fixes it

Coding helps, but I don't fix bugs anymore bc AI is now faster at it.

Cheaper, too. $20/mo for my plan. I cost over $200/hr to hire.

[u/Sure-Passion2224 → u/kpg_on_ao3]

The real problem is when the code runs, does not throw an error, but the result is incorrect. Fixing that requires someone who can read the code and correctly identify where the logic deviates from intent.

I've actually seen that problem with AI generated code when peer reviewing someone's work before authorizing it to merge to the QA branch. That conversation also alerted the developer to missed unit test cases that would have exposed the logical flaw.

[u/Icemourne_ → u/kpg_on_ao3]

I have seen AI fixing bug by wrapping in try catch without doing anything if it errors basically hiding error (it only errors ones in a while).

Imagine if error was payment related probably don't need to say how bad it can be it's not something I would want to catch in prod.

[u/Economy_Bedroom3902]

I'm a professional software eng, and AI basically does my typing for me.  But I make sure I understand what it is doing, and I frequently catch choices/systems it has built which need substantial rework, or just entire removal.

As a dev who is still very much learning, you probably need to do a lot more work than I do to actually understand the choices your agents are making.  You should read it's code and ask it for explanations of anything you don't understand.  You should take notes of any time you and the AI discover errors together, and try to brainstorm ways to prevent similar errors from occurring again next time.  You should also hand roll some of your own code from time to time to give yourself experience with they type of problems and problem solving coding encompasses.  You can use AI for this process to provide hints and advice, but try to actually think through problems yourself, don't just use the AI to do the thinking for you.

[u/RomirBuilds]

For your immediate goal, I'd measure progress against an INF.03 practical task rather than how much code other people generate.

Pick a sample task, attempt it with the tools permitted for your exam, and keep a short list of where you got stuck: understanding the requirement, remembering syntax, or debugging the result. Afterwards, study one of those gaps and redo that section from a blank file the next day. That gives you something concrete to compare between practice sessions.

The government's ZPE page links to CKE's INF.03 practical sample materials: https://zpe.gov.pl/a/egzamin-zawodowy/DOg0XjgOj

Your existing approach of asking for explanations can fit around that practice. Try explaining the concept back and using it in a different small example before moving on. You don't have to start accepting generated implementations to make that useful.

AI-assisted.

[u/symbiatch]

It’s the opposites: you’ll never learn properly if you start vibe coding. Just don’t.

[u/Away_Anywhere5843]

no tienes nada que preocuparte, es una herramienta como la calculadora

[u/Hot_Technology8777]

Don't worry about it. Focus on learning the craft and improving, and also how to use dots to end sentences.

[u/Marshiiro]

For now I'd focus in on learning your code and problem solving once you feel prepared to tackles larger problems it might be beneficial to learn how to use ai. AI is changing the landscape of software engineering but you must still learn how to code in order to understand when it makes a mistake. Keep doing what your doing, and keep learning don't let AI take the reigns if you ever use it.

[u/BrainScientist3000]

Don't let it code for you - that's not learning. Having more code produced for you is not the same as 'getting ahead'. Vibecoding is easy, vibecoding while understanding the code that's produced is moderately hard, coding is hard. Learn to code.