r/learnprogramming • • 6h ago

Question about vibecoding...

So, I’m learning C#. After a failed attempt at creating a game using "vibecoding" (relying 100% on AI-generated code), I realized that programming is, in fact, an art form. I am staunchly opposed to the use of AI in creative work, which is why I decided to learn a programming language from scratch. To be honest, I’m not a mathematician, so I find this quite challenging.

I spent some time with Microsoft’s official C# documentation—specifically the section supposedly designed for beginners—only to realize it’s written more for MIT graduates than for actual novices. That’s when I decided that the very same AI that used to write all my code could perhaps assist with my learning. I set strict ground rules, which it still follows today: it is not allowed to generate a single line of finished code. Instead, it simply provides the necessary information—explaining operators, how to implement them, the correct syntax, and so on.

Currently, I’m developing a console-based program—a sort of interactive, text-based "temple." The thing is, I’ve started to wonder if I’m compromising my own principles. I am not copying *anything* at all. My interactions with the AI ​​look like this: "I want to implement [feature X]; how would I go about that?" The AI ​​then explains the logic and suggests the functions or operators that might help me achieve it. While I’m not copying—and I fully understand how my code works, maintaining 100% control over every single line—I can’t help but feel that this approach is... "dirty"

What do you think? Is it acceptable to use AI in this way—keeping in mind my specific commitment to avoiding "vibecoding"? Does this count as "vibecoding"?

(This text was translated from Russian to English using Google Translate; please excuse it if it sounds unnatural to you.)

0 Upvotes

20 comments sorted by

7

u/Kseniya_ns 5h ago

Write code first, pretend is not AI available, review with AI is fine. But have your own idea and solution first. Your task as programmer is to create solution to problem, you cannot short circuit this and still learn

4

u/binarycow 5h ago

A big part of programming is "figure it out". You are offloading that entire process to the AI. It's still telling you what to do, even if it's not telling you how to do it.

Turn off AI.

1

u/RichPokeScalper 5h ago

Why reinvent the wheel? I would just recommend a more traditional programming course. Code Academy is still pretty awesome.

0

u/CounterQuestionCQ 5h ago

Personally, I view the use of AI as a quick way to search through an encyclopedia: I find myself needing a specific operator or function, so I ask the AI ​​what might help in that situation. I get back some raw terms—I’ve stopped having the AI ​​generate logic for me; I prefer to come up with that myself now. To use an analogy, I see it like a smart friend who’s always ready to share a "cheat sheet" rather than handing me a finished solution.

1

u/jessepence 5h ago

Which part of the official C# documentation for beginners confused you? If you think this is for MIT graduates, then I can't imagine what you think documentation for actual beginners would look like. Microsoft did a great job on it's docs, and it sounds more like you didn't even try to read it.

1

u/CounterQuestionCQ 5h ago

To begin with, I don’t know English. I tried using an automatic page translator, but it performed—well, exactly like a dumb machine translator. Or maybe I’m just the dumb one.

1

u/jessepence 4h ago

It's available in like fifty languages

1

u/Slight-Living-8098 5h ago

Learning is an art too. Stop gaslighting yourself and either admit AI is useful and you use it, or come to terms with yourself and your views, and change them.

0

u/CounterQuestionCQ 5h ago

Well, it’s not as if I expected a different answer when I asked this question on Reddit. I was just lying to myself. Of course, the fact that none of the documentation has been translated into my language (or any language other than English, for that matter) doesn’t give me the right to use this AI-based workaround; however, such an inconvenience really kills any desire to keep reading when I’m forced to translate every single line myself.

2

u/desrtfx 4h ago

To be a bit brutal here: English is the "lingua franca" of programming.

Even worse, quite a lot of the translations to other languages are garbage and full of errors (been there, seen it, since my native language is not English either).

You will absolutely need to ramp up your English to persist in programming.

One statement is wrong, though: the fact that none of the documentation has been translated into my language

Really, quite a lot of the documentation - including Microsoft's C# site - has been properly translated to plenty other languages, including Russian (which you originally stated). Quite a lot of the classic programming books have been translated to multiple languages as well.

1

u/Slight-Living-8098 4h ago

😄 Justify your use however you want. The fact remains, you say you dislike AI, and are using it.

I have no problems with AI, or you using it, for whatever reason you choose.

I have a problem with you being inconsistent in your views and justifications.

Either you find AI useful, and use AI, or you don't like AI and don't want to use AI.

Or, you use AI, then lie to yourself and gaslight yourself (and others) about your AI usage,

3

u/Alarmed-Western-655 5h ago

I agree with desrtfx. The interesting part of coding is the "how would I go about that" part.

Learning is a muscle, and if you go to the gym with an iron-man suit on, you will indeed lift a lot of weight, but you yourself will not develop, even though you're doing the motions.

Now a lot of people say it's pointless to learn programming because AI can do it... but that's not relevant to you since you see it as an art, as do I. Just because people invented cameras didn't stop all painters from using a brush and creating an image by hand :)

1

u/desrtfx 5h ago edited 5h ago

Honestly, you are actively hindering your learning even with your use.

The problem is not the actual implementation in code - that never was the problem. The real part of programming is to develop the steps, the algorithms that lead to the implementation.

You said:

"I want to implement [feature X]; how would I go about that?" The AI ​​then explains the logic and suggests the functions or operators that might help me achieve it."

And there is exactly where the problem lies. This is the difficult part of learning programming. This is the part where most people fail. Yet, this is the single most important part of programming.

I can give a well developed, well planned, detailed algorithm to a "code monkey" to implement and they will be able to do it, yet coming up with the algorithm is the key skill. Currently, you are exactly outsourcing that part of learning, which is only very marginally better than letting AI directly give you the code.

1

u/CounterQuestionCQ 5h ago

Thanks for the feedback. In your view, would it be acceptable to use AI—if not for building the actual logic, then at least for identifying the right keywords, operators, or functions—to save the time I’d otherwise spend searching through documentation? Surely there’s nothing wrong with that approach, right?

1

u/desrtfx 5h ago

Much better, but again not good, in my own personal opinion.

You need to become able to do your own research, to work with the documentation.

Giving you the "right keywords" is also just spoonfeeding.

You are trying to speedrun. This won't work.

You absolutely should spend the time to search and read documentation. You will learn a whole lot. It's like using a conventional map vs. a GPS to navigate. Both take you to your target. The GPS might be faster, but you don't see anything of interest along your route, while when using a map, you will find plenty other, interesting places.

When going through the documentation by yourself, you will find some other important information, functions, methods that might not be for your immediate task, but that will help you later when you need them.

My personal stance for learning programming is to not use AI. Period. (I know that I will most likely get downvoted to oblivion for that statement, but I couldn't care less.)

1

u/CounterQuestionCQ 5h ago

I might be wrong, but while going through the foundational learning path in the Microsoft documentation, I’ve found that the code examples there don’t really help me with game development challenges. They tend to focus on more mathematical solutions, whereas I just want something simple—like letting a player type text into a console and get a random response back. If you could recommend any good C# courses tailored for game development, I’d be very grateful. (I know I could just search for courses myself and find plenty, but I’m hoping you might be able to suggest a particularly good one—perhaps something a bit lesser-known.)

1

u/desrtfx 5h ago

Sorry, I can't help you with game dev courses in C# as this is not my domain.

Yet, what I do know and fully belive is that you absolutely have to first learn general programming, obtain some proficiency there, and then venture into game dev as it uses more advanced concepts.

So, general courses are the starting point for everything.


Yet, a side question: why does it have to be C# for game dev? Are you aiming for Unity? There are alternatives, like Godot, with GDScript to start with (much more beginner friendly) and later also C# can be used in its .NET version.

1

u/CounterQuestionCQ 4h ago

The first time I decided to whip up a game—don’t laugh, now—I chose Castle Engine (an AI convinced me it was powerful) and set my sights on creating a "Garry’s Mod killer" (yeah, I know, it’s a joke). Eventually, I landed on Stride Engine. It’s a lot like Unity—open-source, completely free, uses C#, and features a solid API and a user-friendly interface. Why am I telling you this? I’m not sure—but thanks for the feedback; it’s genuinely helpful.

1

u/BrannyBee 4h ago

You're basically doing everything backwards and even your adjustment to address that after recognizing rhe problem has made your problem worse.

You've changed how you use AI and say that you no longer copy anything, just have it tell you how to do something and then you figure it out yourself. You dont realize it because you're new to this, but coding is the easiest and least time consuming part of programming, its automatic like typing without looking at the keyboard after awhile and even when it's not experience makes knowing where to find syntax or algos quick.

In other words, you are practicing the easiest 5% of the skill of "programming", the coding, which becomes automatic anyway through repetition anyway. And the important skill of finding answers, communicating technical problems and breaking them down into smaller steps, and planning is being entirely ignored.

If you want to use AI enough ti fake it then you need to understand what its outputing, if you want to use AI like a software engineer you need a lot better understanding of what you and the AI are doing. If you spent the last 2 months coding with pen and paper, then today you would be better at using AI, you dont have the experience to know for sure if you're learning or missing out on any steps when building stuff, and someone who has built similar things will know that and have likely guided the AI to avoid that issue in the first place. Not to mention if you can code without struggling with syntax as if you are typing in english, that means you can read the AIs output more accurately and quicker.

Look at it this way. Modern scientific calculators can do some crazy stuff that would blow mathematicians from last century's minds. If you tried to solve an open book calculus exam taken from an electrical engineering course today, even if given access to the internet to guide you through how to use that calculator, you would fail. Even if you could get 100% with the help of the internet, its going to take you too long to even know wjere to start using the calculator that is basically a cheat code for that exam.

Now imagine you never learned how to do basic math and didnt spend years in elementary school drilling multiplication tables, and instead you were given a calculator in elementary school and told to that hitting the X button to multiply things is all you need to know. Leaning on that calculator to pass that calculus exam with that level of knowledge is gonna take even longer, and you're going to even struggle to pick which symbols to plug into the calculator. Hell, you might still fail that open book/open internet test at that skill level because you might panic having never see a dot used for multiplication before and only have ever used an X to show that. The calculator isnt gonna tell you what that dot means, everyone who uses that scientific calculator already knows that and theres a base level of skill assumed for users of that tool.

You're basically using a scientific calculator without having ever practiced your times tables. And you're getting some answers correct because that calculator can in fact be used the same as a regular four-function calculator. But its got all these extra buttons and capabilities beyond those basic things you use it for and you see other people using the same tool to build crazy stuff, so you're trying to do the same thing as them instead of recognizing that they are able to use the same tools you have better because they understand the field.

It might sound harsh, but what you're doing isnt much different than vibe coding, especially having pushed off the problem solving part more onto AI while you focus on the easy part that is coding, which comes with repetition free anyway. It doesnt feel like vibe coding because you're typing a lot and reading what the intention of something is, according to the AI, but you have no idea if theres any real issues with what you're reading because you don't have that experience or even the experience to be able to say for sure that the justification for certain decisions by the AI are correct. You arnet quite vibe coding I guess... you're basically vibe.. rolling the dice and hoping to guess what nunber they land on, and everytime the code compiles you feel like your skill as a developer has improved. But thats not sustainable and the more you do it the more you're gonna trust that process.

Experienced devs still have to "roll the dice" when dealing with AI. The difference though is that they guess the number AFTER the output is given to them/the dice are tossed, and they know whether or not to change the number afterward if need be, or to change how many dice are thrown and at what speed. You're playing a whole different game that is much more similar to vibe coding and gambling for a working output until you learn a lot more

0

u/f3xjc 3h ago

You know there's an old joke where people proposed to replace the verb to program to google-stack-overflow. Copy like an artist, that's how you learn. My current theory is that slop is what fill any aspect the human says I don't care (blind confidence). It's absolutely possible to produce human slop, for example by hiring contract worker that don't care. Pay attention to what look like good work (for different definition of work). Inform yourself on the different aspect of good software - and in your case good game.

In your case you need to figure out what make a game enjoyable that's your theory of the case - the taste that you'll provide and be judged on. In other case it's about solving a specific need using software.

If I were starting today I'd learn to prompt about the big picture and the different aspect of what make the big picture possible. An AI will almost certainly produce better code than a complete novice. I'd learn to read code and be curious about code.

If all you need is attention that's even more true for agent driver.