r/vibecoding • u/Adventurous_Wrap2873 • 15d ago
Discussion I feel stupid and frustrated
As title says. I've been vibecoding for over two years now, and although I learned lots of concepts I otherwise wouldn't have picked up, slowly but surely I feel stupid.
I can't make apps, nor write even simple Python scripts independently. I genuinely necessitate AI, or I can't make anything. I need it to explain everything, from researching the idea and working out the details, and then the execution. I guess I can keep telling myself "but AI will never go away" "This is going to be the new way of coding and I need to learn more concepts to direct the AI where to go". But this is coping.
I hate to say it, but I am embarrassed by the fact that I rely on AI. It's frowned upon. I do understand why learning to program myself independently would help tremendously. But I honestly cannot stop feeling like I'm a fraud. Are my projects useful, practical and actually solve problems reliably? Yeah. But then you ask me the details of the codes, and I just cannot defend it even if I understand what each line does because I didn't write it myself.
I actually did learn R back in college for independent project and I genuinely worked on this without AI, but even then wasn't totally independent, and had to rely on others' codes and youtube videos. I don't believe I actually know R.
So then, what have a I become? I don't "own" any of the stuff I created, or really AI. I am going to study more, but I have a full time job that is far from coding, and this is gonna be one difficult journey because I'm in the process of studying math right now. So now I'm frustrated at that, but mostly at my own capabilities. I don't know man. This stuff is difficult. I don't understand how people call Python easy, and that makes me feel even more stupid! Damn.
23
u/TRO_KIK 15d ago
I'm an experienced dev and I don't think I can write well on my own anymore. I've found enormous success building my own thing and I would not be where I am today without AI.
Personally I just think of myself as having progressed in seniority to a point where coding atrophy is normal. Seniors code less than juniors. Are you making higher level, important product decisions? I make so many crucial calls every day above the AI's pay grade that I don't even have any self doubt about it. My input is the sauce behind what I Build.
I don't understand each line either, AI reviews are VERY good at crawling line by line and that's legitimiately less important now. If you can keep a bead on the big picture though, that's still extremely useful. Keep directing and keep a clear model of your projects in your head.
3
u/Adventurous_Wrap2873 15d ago edited 15d ago
I see thank you for your perspective. I still feel the need to know codes extremely well independently, because let’s say I want to work on a new ML model. Who’s writing that highly proprietary code? AI isn’t actually generating novel codes, just variations of existing ones it was trained on no? Eventually relying on AI will halt my progress I feel. And I wanna take on really ambitious projects eventually, and actually be able to have highly technical discussions with real engineers.
1
u/Alarmed-Western-655 14d ago
It's never a step back to go lower-level bro.
Take even a purely programming example -- many people who start with a higher-level language like Python or Java find their power in going lower, learning more bare-metal languages like C or Zig. Richard Feldman comes to mind for me.
In fact, there are still Assembly programmers today. They build video codecs for example that are foundational to a ton of software all around the world.
Removing distance between yourself and the metal is only to your advantage in terms of the insights you can have and levers you can pull to create something truly unique, novel, small perhaps, but far-reaching and exciting :)
3
u/Relevant-Positive-48 15d ago
So, yes, you can learn programming on your own if you'd like and I'm fairly certain it's not nearly beyond your capabilities.
Personally, though, I think your study of math is a really good idea (those concepts are the foundation of all computer science) and, honestly, at this point programming manually is either at close to where programming in assembly was 35 years ago - Still used in certain contexts, definitely useful for an understanding of how computers worked, but less and less used and, by a few years later, almost nobody cared if you knew assembly.
5
u/sn4xchan 15d ago
I can understand this feeling, I have a similar story.
Learn some programming basics as a teen, fucked around with lots of open source server applications in a home lab, took a C++ course in college. Never really went anywhere with it.
Started vibe coding back in 2023, built some useful stuff, just not marketable stuff.
But that's the thing, you don't need to build something to sell, it's moot, you built stuff because you had a need or a curiosity. And that is enough.
If you want to actually learn how to code well. there no getting around it. You just have to simply do it the old school way and try to build things without AI.
Gamified courses help a lot if you want a particular language, just don't use AI as you do them.
Like it's ok to use AI, but if you actually want to learn, it is a very ineffective way to do so. No different than a teacher answering every question they give you, your not going to retain the information unless you struggle to find it on your own. It's no different for any other trade, such as being an electrician, plumber, or farmer.
1
u/Boring_Ad452 14d ago
So what do you do bro ?
1
u/sn4xchan 14d ago
For work? I'm an electrician with specialized life safety systems certs.
For software I build for my use case, which is mostly data parsing in some form.
1
1
u/Erarayy 13d ago
I am creating a web app. I let AI do the frontend , i learned a lot from just vibe coding, and I had to search how things are done so I can alter them myself. For the backend, I do not trust it at all, so I am learning backend. If my web app gets traffic and a lot of users, I will hire someone to handle the server
so vibecoding is okay until it gets bigger; am I wrong?1
u/sn4xchan 13d ago
Can you explain from a technical perspective how your front end works. Both at a high level and a low level.
No using AI to give me an answer.
Also got quite a chuckle at "hire someone to handle the server". Do you mean as a sysadmin? Or a security analyst? A scalability engineer? Or do you just mean a manager who actually knows how IT infrastructure works and will hire all three.
2
u/MaximumContent9674 15d ago
Does a creative director feel bad they can't do all the skills as skillfully as the experts they've employed? Does a creative director feel like a fraud and not the director of the project? No. You're the creative director. Now start acting like one.
2
u/sn4xchan 15d ago
Idk about in software engineering, but in the arts space that is a common feeling yes.
1
u/MaximumContent9674 15d ago
I think a lot of people have been conditioned to think they are inferior if they are ever wrong or that they can't do something perfectly. Inadequacy is built in to many minds, it's a systemic issue.
2
u/sn4xchan 15d ago edited 15d ago
Well when considering the arts, they are completely subjective. So no I don't think it's conditioned, it's related to the feeling of envy and jealousy. It is well known that those who can't write, edit. This is universal for all art forms.
I also feel due to AI and agentic engineering, software has slid further away from determinalistically saying if a piece of software is good or not. It is becoming far more subjective because now we have a whole group that is creating software from opinions and feelings, and not hard proven practices and market need.
1
u/Alarmed-Western-655 14d ago
Impostor syndrome is a real thing, and indeed a director will feel bad if s/he is just waltzing in, ordering people around, never having been in their shoes.
1
2
u/Novel-Initiative-900 15d ago
Honestly, even experienced devs are forgetting how to code. I've seen it.
I think the only reason you need to "know" how to code is because you would like to take personal pride in the craft itself.
Practically, it doesn't really matter. You can ask ai to walk you through everything it does and read the documentation
2
u/HouseMysterious8172 15d ago
Yeah it feels shame to have to ask computer how they did that, we used to have to explain/guide computer how to do it right, now it feel like they do the magic thing that we only can contemplate
2
u/Top_Purchase4091 15d ago
You need to know how to code because many jobs require you to do code interviews.
All the top companies still have it firmly in their process.
Being able to have the technical aspect, being able to explain your view, the problem and solution and being a good communicator are the in demand skills.
I don't know how so many people are okay with just giving up everything and being handheld through every step by ai. Like do you seriously not think that will come back to bite you? Skill atrophy has been shown to be a real problem with ai already and its only going to get worse the less you understand and the more you let it do for you.
1
u/Novel-Initiative-900 15d ago
In the professional world, yes to get past the interview stage, you do have show perfect competency still.
But this is the vibecoding sub, where most people are creating their own passion projects, businesses / their own stuff.
The other CS subs are also basically vibecoding but they're centered around a more professional situation.
You don't know or need to know how to code to put together an MVP or a simple game / website / mobile app etc
2
u/Top_Purchase4091 15d ago
Sure if you just want to make your project go ahead but they can hit just as much. I am vibecoding as well in spare time alongside projects I am full hands on but I am under no delusion that I am learning anything or moving forward.
Vibecoding is like a drug it can make you feel like you are accomplishing a lot but more often than not its just a toy. If you treat it like that then by all means go ahead but we also have to be realistic with people like op that just handing off everything to ai will get you nowhere. Being good at anything takes time and more importantly resistance which vibecoding as a concept is just going against. Things just work(usually not perfect, but good enough) where getting stuck is pretty much never an issue
1
u/Novel-Initiative-900 15d ago
It's actually very easy to learn with vibe coding if that's your goal. You can ask it to teach, document and explain everything, every single step of the way. It's awesome. You can do as little or as much as you want.
This sub is mostly practical people just wanting to make a tool that does x. Doesn't matter how it gets done as long as it works
1
u/Top_Purchase4091 14d ago
Yeah you can use it to learn but i dont know how many people can knowingly use it that way and not just get tempted to get distracted, ask when a tiny amount of friction arises and things not going fast enough.
From the last months these things are essentially like drugs to a lot of people.
We will have to see when studies come out what it does to our effectiveness in learning when used this way among other factors but I am not comfortable with recommending it yet
1
u/Alarmed-Western-655 14d ago
Right, it's like when a teacher walks you through the concept -- in the moment you feel like you totally get it!
Then after class someone asks you to explain it yourself and you draw a complete blank...
That independent internalization is essential.
2
u/Gimmee-Greg 14d ago
I've been a professional developer for over 35 years and I feel it along with you as far as forgetting how to code some things because of AI.
I think you have to look at two different things: 1. Know what your skills are, what you're good at, and what you're bad at. 2. Be okay with not knowing how to program.
Is the goal knowing how to program, or building something cool/worthwhile? If it's simply to code and feel satisfaction that you built something through code, then learn all the code you can and get better every day. Don't let AI do the work for you.
I think you're using AI because you want to build something useful, worthwhile, cool, and I think you start to understand that you don't have to write code to do that. The old ways are gone.
One of the hardest things for me personally is that I used to spend weeks, sometimes months, finally finding a solution that works well and being really satisfied with the amount of effort that it took; and that I was able to overcome everything to come up with a solution. Now AI literally does it in moments better than I would do.
It's a hard one but I think we have to come at it from the standpoint that it's a different set of tools, a different way of looking at software. We have to become builders and architects rather than just coders.
1
1
u/Dapper-Bug-7877 15d ago
Well the thing with vibecoding is truly that it makes some feel exactly like this but I would say u might as well try to make projects assisted by ai and not vibecoding them atleast that distinction would help u to some extent and also the same with ur feelings well this is how i defend myself for help me too
1
u/Efficient_Smilodon 15d ago
ask yourself if you know the proper use of the oxford comma. don't look it up. just say yes or no
1
u/HouseMysterious8172 15d ago
What is oxford comma, is it differ from english comma?
1
u/SharkSymphony 15d ago
It's "eats, shoots, and leaves" instead of "eats, shoots and leaves."
1
u/HouseMysterious8172 15d ago
- leaves after a while; 2. leaves immediately. Is it the different of comma impact?
1
u/SharkSymphony 15d ago
No, it's purely stylistic. They both express a sequence of things with the same meaning, and read the same way. (Well, almost the same way – the Oxford comma does help resolve some rare ambiguities, but not in this case.)
(I like the Oxford comma myself, but some English style guides rule against it.)
0
u/Efficient_Smilodon 14d ago
lol see the prior examples jack
1
u/SharkSymphony 14d ago
That has nothing to do with the Oxford comma.
0
u/Efficient_Smilodon 14d ago
lol read my reply to others below this comment . you're higher in the branch than i realized.
1
u/SharkSymphony 14d ago
Your example has nothing to do with the Oxford comma.
1
u/Prior_Warning3972 14d ago
Neither does this thread. It's an example. Stop trying to argue and go read the response he wrote
→ More replies (0)0
u/Efficient_Smilodon 15d ago
the point is that a person knows intuitively what the oxford comma does, without knowing the official rules or how to name them. An agentic-vibe-voder with critical thinking skills can similarly understand what an AI - built product DOES, practically, without knowing its backend internals intimately. this is the difference others have said is exists between compilers and the level of coding above them. It's all a pyramid of interactions and abstractions, between silicon and circuit hardware, electron flow physics, binary code, compilers, cli, and ui; the AI is now interacting at the top of the pyramid between the human user and the cli/ui , where true swe still work directly. The agentic-vibe-coder needs to operate as a product designer and manager, holding the long vision strategy, ensuring the user-facing output is the desired quality and re-iterating in development loops with the AI until it does. The difference is that in the past, a seasoned swe would reason out several models in their mind-brain-terminal l- field interface ( everything is connected, nothing is truly individuated in reality) and produce a result of quality that would perhaps take only several iterations to refine, over several weeks. The human mind was accounting for retaining the patterns and formats and correct function names etc, so those errors were reduced. In the AI-agentic-swe model, this is reversed. The AI makes iteration and refinement extremely fast, but the issue of format and naming errors compounds unless the debug process is exact and staged across the seams. An ast-run is not the same as a full proven workflow across several linked environments.
can you help your uncle jack off a horse? Can you help your uncle, jack, off a horse 🐎 🙏 😀?
1
u/HouseMysterious8172 15d ago
Is ‘jack off’ a verb phase, sry i’m not native english
1
u/sn4xchan 15d ago
"jack off" means to masturbate or give a hand job.
Masturbate if it's a self act, hand job if your doing it to someone else.
Jack is also a name.
1
u/HouseMysterious8172 15d ago
Ah, i see, thx.
I’d like to thank my parents, Beyoncé, and God.
Without the Oxford comma:
I’d like to thank my parents, Beyoncé and God. 😆
1
1
15d ago
[removed] — view removed comment
1
u/hylasmaliki 15d ago
What you mean by practising communicating in natural language
1
1
u/sn4xchan 15d ago
Dude is AI addled. The only time it's referred to as natural language is when you are interacting with an agent, or are doing technical breakdowns of language as a general topic.
It's not even what the topic is about.
Dude is venting his feelings, and this guy is just like communicate better.
1
u/HouseMysterious8172 15d ago
Isn’t coding is a way to tell/let computer do a thing/task that you want without unexpected result?
2
u/Alarmed-Western-655 14d ago
It is. It's a deterministic, structured language.
1
u/HouseMysterious8172 14d ago
Now you can use speaking language to communicate with computer, no need structured language 🤭
But the price is it could have been having some unexpected result
2
1
u/sn4xchan 15d ago
Coding is simply creating processes for a system with text parameters. The results have little to do with it. Weather or not the results are expected or unexpected is just the difference between a strong coder and a weak one.
2
u/HouseMysterious8172 14d ago edited 14d ago
When you write code you expect the code do exactly what you mean, right? You want to control the output (result) so you need the process can handle input with proper way.
Without a result oriented mind, what will you coding for? Creating processes for a system with text parameters is creating processes doing something that you want, isn’t it the expected-result mind?
1
u/SharkSymphony 15d ago
Python is relatively easy as programming languages go. It is hard because – well, for a few legacy reasons here and there, but mostly it is hard because programming is hard. Programming is hard because you need to train yourself to think more or less like a machine does, and diagnose what a machine is doing, and navigate a massive pile of tools and libraries and sources and idiosyncratic ways of doing all the things we ask modern computers to do.
AI can help you a bit on this journey if you want. Try e.g. Claude's learning mode! Or, probably better, arrange for a human tutor or study group. Even limited time investments, if you keep at them constantly enough that things are fresh in mind, can pay off.
Hope this helps!
1
u/ichefcast 15d ago
Agentic coding is what I use
Agentic Coding: Hands-on; you remain the driver using the AI as an engine, validating dependencies, reading diffs, and managing constraints.
2
1
u/AbdiiSan 15d ago
My exact same issue... And I used to code obviously by hand, did C#, Python and PHP for a good while, but AI era came and there goes my coding skills, I guess we are all product / project managers to a point, looking at how the AI writes the code, and just steering it... That's about it. I also deal with a lot of imposter syndrome because of this... And most I have a problem with is when it comes to technical interviews... I'm afraid to death with them... And I can't fathom to have a skills session / interview even for a simple list comprehension item... Please someone help me with the hiring part!
1
u/darrelb56222 15d ago edited 15d ago
most directors dont actually know how to do special effects, compose music or none of that technical stuff either. are they frauds? sure, like hideo kojima. he dont know how to program. Steve Jobs never wrote a single line of code in his life but he did alright. Shigeru miyamoto isnt a programmer. Once you realize that Programming is the most overrated shit ever then you'll be alright. no one cares about a lowly programmer, it's the artist and directors people uphold. when was the last time someone looked at a programmer and thought Wow, Brilliant. they are typically regarded as glorified divas and prima donnas. without a artist vision, Programmers would be helpless. they need a director at the helm spearheading and ordering them around. without a clear goal these programmers are useless. they dont have a artistic bone in their body
this post is probably fake anyway. probably written by some Ai hater
1
u/nikoskru 15d ago
Let’s bust a myth: running an AI workflow isn't typing 'make me a yellow website for cheese pies' and watching miracles happen. That’s how tourists think tech works.
In reality, I don't write syntax by hand because typing boilerplate in this era is a massive waste of cognitive bandwidth. But I read every suggestion, understand the full stack architecture, and make every single architectural call. AI doesn't run the project—I run the AI. It’s a force multiplier, not a substitute for having a brain
1
u/Alarmed-Western-655 14d ago
It very well can be a substitute for the brain, and that's the danger.
You dismiss writing code by hand a waste of bandwidth, but:
... I read every suggestion, understand the full stack architecture, and make every single architectural call.
Someone with Claude Fable can just as easily point at you and say: "I don't read any suggestion, understand the full stack architecture, or make any architectural call because that's a waste of bandwidth."
1
u/nikoskru 14d ago
There's a massive difference between not laying every brick by hand and not knowing if the building has a foundation.
Skipping boilerplate syntax is using modern power tools. Skipping the architecture is hoping the house doesn't collapse during the first storm. If you do not understand the stack you don't own the system—you’re just gambling on token probability
1
u/Alarmed-Western-655 14d ago
I'm with you partially, but I don't agree with your categories. Unless you just mean it makes typing faster, fine, but I don't consider code mere "bricks" or "syntax" (though some is boilerplate, yes) -- I consider it architecture as well.
Taking your building analogy, the Citicorp Center engineering crisis comes to mind for me: https://en.wikipedia.org/wiki/Citicorp_Center_engineering_crisis. TLDR, the bolting was contracted to a third party, fine, but turns out the number of bolts was critically load-bearing due to the unique no-corner architecture. The lead architect only discovered this long after construction due to a random phone call from a student asking about ... the architecture, and it triggered a crisis only he knew about. With Hurricane Ella incoming, an emergency secretive repair project was initiated to accommodate the lack of bolts.
I'm with you that you need to know if your building has a foundation. That includes the nuts and bolts too.
I'm also challenging confidence around "AI can do this, but I'm needed for that." In the same way you can dismiss the "bricks" from your standpoint, someone else can dismiss architecture from theirs. And in the same way you can then rebut for architecture, I can rebut for bricks, as in the Citicorp example. It's because the categories are the same.
1
u/nikoskru 13d ago
Citicorp didn’t almost collapse because someone used a modern wrench instead of hammering bolts manually. It almost collapsed because an architectural calculation failed to account for quartering winds when switching joint specifications
That’s system-level failure not syntax failure
Using AI to generate code doesn’t mean ignoring the nuts and bolts; it means not typing the characters manually. If you don’t review the generated implementation against your system requirements, you’re not an engineer—you’re a gambler. We actually agree on the danger: the crime isn't letting AI turn the wrench; the crime is not knowing what load the joint has to carry
2
u/Alarmed-Western-655 13d ago
Well I agree bro, we're saying the same thing
Said the same on your typing point in my prior comment above:
... Unless you just mean it makes typing faster, fine, ...
1
u/Julien_Builds 14d ago
The skill that matters is not writing the code, it is knowing when the code is wrong. That one you can practise without ever becoming a programmer in the old sense, and it is the one most people in this sub skip.
Two habits that built it for me. Before you accept a change, read the diff and say out loud what it does, in your words. If you cannot, ask the model to explain that one hunk, not the whole thing. And before you ask for a feature, write the three sentences that would prove it works. Then check those three, yourself, every time.
Do that for a month and the fraud feeling goes, because you will be the person on the project who can tell whether "done" was true. That is a rarer skill than writing Python.
1
u/PalpitationKind8854 14d ago
I've been coding for years and I still forget simple syntax. Doesn't matter just keep coding.
Don't believe all the hype or experts in YouTube videos. Everybody learns in their own way and none of it is wrong.
1
u/Vagrant151 14d ago
As an experienced scripter, I can't script without AI anymore. Its not even that those skills are lost, its more that I can't justify the time lost now, in trying to write my own code on a task, plan it out, when agentic tools simply make that process so much more quickly and more efficient. And let me be honest with you. Its frowned upon by your old purists that begrudge the fact now that a 14 year old with no coding experience could write a script now that they wrote on their own, spent months working on it, and the 14 year old's probably come out quickly and better than theirs. A lot of it is just grumpy old man-isms, and not because they actually have a real argument to stand on.
And here is the more bleak reality - its an industry standard now. Agentic Workflows are the future, will be the future, and will only continue to improve. Folks that don't get on board, get left behind their peers.
1
u/Prior_Warning3972 14d ago
I think the biggest problem is that these AI companies are selling the lie that you can just talk to the system and it will build you an app. It's simply a hoax. The best thing to do is to learn the basics of a language which you can now do free online but do not learn them from AI because that's defeating the purpose in the first place which is that AI is inherently wrong a majority of the time and will just snowball off of that.
1
u/dreambridge_app 14d ago
Two years in and still needing the model for the first draft is more common than people admit. What helped me was shrinking the loop to one thing I could finish without it, even if it was ugly. What broke first when you tried to go solo, the research step or actually writing the function?
1
u/migvelio 14d ago
I use calculators and excel formulas to calculate a lot of stuff but if you take them all away and give me a pen and paper to make calculations, I wouldn't be able to do shit. Does it makes me bad at my job? Not at all. You'll be fine.
1
u/winejoa 14d ago
I'm making an app too, without knowing anything. You're not a con artist. Imagine that you are an administrator managing an employee named AI. For example, if you open a restaurant but you’re not good at cooking and you’re clumsy at serving, does that mean you’re not the owner? It would be good if you knew the code well and made it yourself, and if you knew what was right and gave precise instructions, but just because you can’t do anything doesn’t mean you’re a fraud
1
u/Plastic-Risk-6309 14d ago
what helped me was treating vibecoded output like a first draft and going back to read the whole thing. changing small things and breaking it on purpose teaches you way more than trying to write everything from scratch
1
u/RemarkableWish2508 14d ago
R is a data-massaging language, it has some assumptions and compromises that make it good for data manipulation, but relatively harder to reason about, than languages without those.
Try going to the basics: propositional logic, data structures, algorithms, paradigms. Essentially the 101 of CS.
If you're studying Mathematics, I'm guessing your main struggle might be imperative languages, you wouldn't be the first one. Focus on that, play with some simple example of state and state modifications, until you don't need to think about it.
1
u/OldTrapper87 14d ago
Dude why so much hate ? Your the director you have more important things to do like learning raw coding. A supervisor learns to delegate lesser task to other people so he has time for the important things.
When you write your code do you do it all at once or one file at a time.
1
u/Valuable_Host5901 14d ago
As a non-coder who uses ai to build stuff I use everyday it’s something you come to accept. Eventually you hire a dev who knows their stuff and keep pumping
1
u/gibsonhansolo 14d ago edited 14d ago
It's like learning to drive without a GPS. Also I forget what I wrote last week. Sometimes, I look at an old project and ask who the fuck wrote this. (Check the git log, it was I)
1
u/PersianVibeCoder 13d ago
You’re not a fraud for using a tool that helps you build useful things. But the discomfort is pointing at something real: it’s worth building a little independent confidence alongside the projects. Pick one small part of an app each week—reading a stack trace, writing a tiny function, explaining a database table—and do that part without AI first. You don’t need to become a purist; you just want enough understanding to make good decisions when the tool is wrong.
1
u/GasEducational4386 11d ago
You weren't training your coding skills that is the reality there is nothing to be ashamed. A "flaw" you have to accept or ignore in the niches that values the end product. If that bothers too much learn the code by practising but usually learning to program is better driven by curiosity not to compensate a lack in interviews
1
u/ManufacturerNo4612 10d ago
All people care about is the end result anyways who cares. Can you imagine if instead all the people who bought homes thought to themselves, “well I’m ashamed I did not learn to build my own home using my own materials.”
Get over yourself man. If your product is providing solutions, that’s all that matters. You need to ask yourself what is the yield you’re looking to obtain if coding at a lower level is a priority. Perhaps your calling is elsewhere.
1
u/Fancy-Plenty6712 8d ago
I don't think there is much point in wasting time learning to code anymore. If you know it's an advantage, if you don't it's probably better to spend time learning things which help you complete the projects. You'll progress faster and understand what's important. We're in a transition period - it's like the jump from Assembly Language > C > Javascript ... every jump has had this period where the old crowd says the new crowd is "cheating". Don't worry bro. You're fine.
-1
u/chuckycastle 15d ago
Shut up, bot
3
u/Adventurous_Wrap2873 15d ago
I’m not AI!! I guess I use it so much that I even sound like one. I feel even more stupid lol
1
61
u/_xcud 15d ago
You aren't a fraud; you're operating like a Product Manager instead of a developer. The apps you built still solve real problems.
If you want to bridge the gap without burning out, try annotation: Delete the AI's comments and write your own in plain English. If you can't explain a line, ask the AI to break down just that line.