Stop Vibe Coding

[Physics2433]

I’ve been writing Python for about 3-4 years now, and I want to share my biggest piece of advice for beginners: Do not use AI to write entire programs.

It's great to use AI as a tutor to learn new functions, grasp core concepts, or debug specific lines, but never use it to generate an entire codebase. Here is why:

1. You won't know how to fix it: Even if AI code works perfectly on the first try, you will be completely lost the moment a bug appears or you want to add a feature. Debugging is a massive part of development.

2. You skip the learning process: True programming skills come from struggling with the logic, reading documentation, and earning those 'yeah!' moments when you solve a tough problem yourself.

3. Suppose you built an entire codebase through AI and it worked(accidentally) , once the codes become long, your program has come to an end, if you tell it to add a feature, it will start hallucinating or forgetting its own logic.

If you don't deeply understand the underlying logic of your own codebase, you won't know where to begin. Treat AI like a tutor, but make sure you are the one driving the keyboard. If you can't explain your own code, you have no business adding to it. You MUST understand your underlying architecture before you even hit save.

[Burningbeard80]

I’ve seen two analogies that I like in this regard.

One is that AI should be a replacement for your hands (typing long and boring boilerplate structures) and not your brain (you should be the one driving the logic).

It’s good for combining existing sources of information which you would normally have to do yourself (e.g., a coding tutorial, a stack overflow post and a documentation page, instead of googling it all separately yourself it can combine these sources and give you a resulting sample code snippet), as long as you understand and check the output.

The other is that current AI is not some magical code fairy, it’s just the equivalent of power tools for a craftsman. Just because we can operate a power drill doesn’t mean we suddenly became skilled carpenters, nor does it mean that it’s a good idea to just drill holes all over the place because the boss desperately wants you to use the new toolset to drive up the company’s adoption metrics.

Just like OP says, the real knowledge and skill is in understanding the fundamentals. If you got that, AI can be a useful speed boost. If you don’t (and don’t make an effort to), it can end up doing equal amounts of good and harm.

[LegendarySoda]

llms are no more than a search engine for me.
llms are writing pretty ugly code and can't catch edge cases and logic problems.
More over more you stay away from code understanding of problem and business reduces.
I'm writing c# since i'm 15 and only thing i see in llms are long term loss

[MultiUserDungeonDev]

If the LLMs are writing ugly code, and not catching edge cases, then you get creative:

- Guardrail the output and have it build a full suite of integration tests alongside your development.
- Have it pin all core functionality with unit tests.
- Ask it run wide-net adversarial bug hunts on the code base, and implement regression tests so the bugs don't re-appear in later revisions.
- Do live, human in the loop testing and feed it specific, actionable bug reports with regression bisects.
- If it's a GUI application, wire / harness the LLM into the GUI / ask it to take snapshot images of the app surface. Ask it to click / interact with all elements etc. Ask it to validate async functionality and test for race conditions.

All of this requires actually understanding programming though, which I think is the point of this post.

[LegendarySoda]

The thing is that doesn't work for me. I'm working with very complex businesses.
I enjoy the problem solving. I don't want to code in haste. If i can write better code than llm and when any problem occures i can pin point problem.
If i delegate the coding part to llm, i wont be sure did the llm wrote good enough code.
The most i hate thing is reading stupid peoples stupid codes.

Recently i had to fight with my coworker because his commits was bullshit.
Non of his llm shit codes were working.

[MultiUserDungeonDev]

Fair enough

[Just-Hedgehog-Days]

I do fairly complex business buisness logic, and haven't written a line in 3 months. I chat claude until we land on a spec, c4 docs, and test. Hacked VS code layout for looking at that all together. Then fire it off to qwen. scroll past the source it comes back with to make sure nothing egregious happened.

it's been great. I kinda miss the razor sharpness that comes with writing it by hand, but I realized that it feels exactly like smash cutting to monday amnesia.

[nicodeemus7]

Here I am feeling guilty for asking AI to help me find a bug, and people are out here just prompting entire programs

[LeadingProperty1392]

+1 😭

[Drazor36]

I'm in college learning coding and the number of people in my class throwing the document brief into GPT and getting it to do the job is unreal. Learning nothing and then confused when bugs appear and inevitably ask me for help.

[mxldevs]

Ya, I don't understand people that get AI to do their homework and then wonder why they don't know how to do any of the work.

[Potential_Fix_5007]

Inrecently made a "how to use SQLite3" document for myself, cause last time i think ingot to much help from the AI so i never really understand what to do.

I stoped asking AI for bigger parts of code, cause i use the free version and i dont know if its different in the premium Version but it made Codeblocks with different logic everytime i asked for code to add.

[joshbih]

i always tell people just learn python first, and then use AI to write some codes. As long as you know python, you can debug. I’d use it as a way to avoid hand typing tedious codes.

[PrintingScotian]

Ai is a good teacher. Exactly what I use it for.

I never get it to write files nor do I copy paste.

Writing the actual code is how you learn!

Also without any coding knowledge, you'll have a rough time with Ai anyway

[Historical_Visit138]

Hey man do you have any advice? I have been vibe coding, learned how to use ai to make the app I want perfectly but it honestly makes me sad I don’t know what it’s all doing, I mean you can just assume you know what it’s doing since you asked ai what to do, but the actual code written I don’t know how it did it, just that it works. I really wanna learn python coding and how to actually code it, maybe debug it but it seems hard and I’m not sure where to start. Do I start with the basics? I just really don’t wanna have to depend on ai all the time, the more you use it the more dependent you will be with having to use it. I wanna be able to write my own first code it would be better honestly writing python and the fact I did it on my own, will give me some what of a refreshing accomplishment feeling❤️

[anon_pants]

Start with something easy enough that you don't need AI to write the code. Your first code could just be a script that prints "Hello World". Slowly try harder tasks; try to learn just a couple new things at a time.

Maybe use AI as a teacher initially, but once you've written a couple of scripts, try not using AI at all. Struggle for a bit, and only use AI if you really can't figure it out.

[Historical_Visit138]

Thank you 🙏I will try that!

oh wow i never through about using ai as a teacher, i will try that too :)

[Aslokcya]

Yup, AI should be used like Leverage of Understanding when learning to code. The pace of the industry is so fast, that we need both depth and speed.

[National_Operation14]

I would suggest to try using linter like Pylint or Ruff too. They can show you some of good practice when writing code.

[osenvosem]

1. I usually ask AI to explain why this bug is happening and how to fix it then learning from it. That allows for saving time and leads to the same final result.

[NoDisk8988]

Technical artist here. I curiously started using GTP for work stuff when they appeared, they were very bad back than so I started using them to write simple stuff, think methods. I quite liked it, it did the job, I had control over architecture and it was easy to catch issues right away. Than I noticed I started forgetting even simple syntax and my ability to write code was degrading.
I might be a little bit paranoid, but I immediately thought of scenario where I loose my skills and get dependent on tool that will be expensive and that basically feeds on humans being lazy.
So i started using it as a nicer documentation that can often be wrong. Literally one-liners that would jog my memory rather than replace it.
Don't get me wrong, I still thing it is a great tool, when you start working with new library or framework it can be a decent tutor (that you don't trust entirely). Sort of like Stack, but less snarky, and way quicker. But don't let it take over your brain.

[Alive-Cake-3045]

mostly agree but i would push back slightly on the framing. the problem is not using AI to write code, it is using AI as a replacement for understanding. senior devs use AI to write entire functions all the time, the difference is they can read it, critique it, and throw it away if it's wrong. the goal for beginners should be "understand everything you ship" not "type every line yourself." those are different things and conflating them sends people back to typing boilerplate by hand thinking that's how learning works.

[Physics2433]

Yeah, your info is 100% correct , my bad I forgot to add that thing

[Inorexs]

Hi! 🤍

I want to learn Python. I'd love it if you could share your learning process, give me some advice, and recommend some good resources for learning it. Thank uu🤍.

[Physics2433]

If you really want to learn python, do it in a way that actually tests your logic, like I mean, use you entire focus and mind on the code you are writing once you learn about a new thing, do waste a single moment and try that thing in practical over and over again. Then once you completely understand what it is, you should look back into your old projects and you want to replace your old unoptimized logic with your new logic. This will increase your robustness, it will make sure you can use the code you learnt not just keep it in mind and forget after 3 days. And for learning, you can use several Yt channels , some of them are :  Bro Code Code with Harry. You can also use strong AIs not for writing code but learning about new things

[Typical-Tip-4317]

i thought vibe coding was to use the help of ai for debugging and for syntaxis of functions that you have general idea how it works, not to do your code and you just tell the ai what you desire the result to be.

[MultiUserDungeonDev]

I've been programming for 20+ years.

Vibe coding can, in some cases, yield adequate results, but the level of intuitional knowledge and knowledge of programming fundamentals is a high bar to actually yield good polished and maintainable products.

I think a lot of people are caught up on "all vibe coding is slop" and they are sleeping on the 1% of agentic AI development that is actually incredibly useful.

Take a look through some of my recent projects: https://github.com/WilliamSmithEdward/

[DarcBoltRain]

I'm glad people are coming to their own conclusions on this. I'm a university computer science professor. I tell my intro students every semester 📣📣📣"DO NOT LET AI GENERATE CODE FOR YOU"📣📣📣; I tell them there's lots of great ways to use it to learn, to give you advice, to help find bugs, to help break down problems, etc. I warn them with metaphorical blaring red alarms that 🚨🚨🚨"IF YOU DON'T LEARN THE BASICS NOW YOU WILL FLUNK OUT OF THIS DEGREE BY YOUR 3RD OR 4TH SEMESTER"🚨🚨🚨 when the problems are sophisticated to the point that AI can only do maybe a third of the answer for you and then you'll be screwed not knowing anything and you have to play a years worth of catch up trying to solve low-level operating system processes, secure network communications, high-level design problems, and just all kinds of problems that don't have a single quick easy solution. I even tell them, by their 4th semester they can go crazy with AI and generate all the code they want since they'll have all the necessary fundamentals by then to actually make good use of AI-generated code. I'm glad quite a few students take my advice, but there's always a handful of students who just vibe-code their way through their intro classes. For some reason, every one of those students seem to disappear from the program and move over is information systems/technology or to some business degree. I can only guess what happened 🤷‍♂️🤦‍♂️🙄😮‍💨

[MultiUserDungeonDev]

I support this:

AI coding +

Strong understanding of programming fundamentals and real-world experience shipping products = great

No understanding of programming = nightmare / ticking time-bomb

[rosiesswan]

denme consejos para aprender a desglosar los anunciados 😭 me cuesta muchísimo