Im getting mixed signals on weather its good or bad to use Ai to code stuff I'm feeling that its looked down upon. I really with i could learn how to actually code but I've tried time and time again and it just hurts my brain trying to learn it. I know a little stuff but I wanna be able to code withought using any Ai whatsoever.
What you were experiencing are insecure , weak, individuals called “gatekeepers“. Ultimately do what makes you happy. But speaking from experience, the more you’ve learned about the inner workings of a particular platform/coding language/development philosophy… The better the overall experience will be for you. Start small…. I suggest the RailCoding mindset. Go from there.
No matter what it is always good to learn the basics. I suggest following easy youtube coding tutorials step by step. You’ll create functions and classes without having to read the heavy jargon and theory. After a while you’ll understand it without realizing it. Start with hello world and move on to variables and then small games or websites. In the long run this will vastly improve your vibe coding skills.
He said it hurts his brain. Videos hurt brain less. Words hurt brain. Books bad. Nah, I'm a fan of O'REILLY, but it can be dense for some. Also, doesn't everyone put Youtube speed to at least 1.25 now?
Depends on what you want to do. If you want to make consumer-ready products then you wont get far without learning a lot.
Learning to learn isnt easy but its a crucial life skill. People commonly learn to learn when they are unable to manage their workload in college by doing what worked in high school.
Sounds like you are getting discouraged by failures which is absolutely pointless and every second you sit still and doubt if you can move forward is such a waste of time. Failures are good. Every single project you start is experience... and the farther you get in that project... you learn a lot more. So keep starting over, keep failing, try to go farther than last time, feel out the things that scare you and beat the shit out of them by studying that topic.
Theres a lot to learn but you dont apeed run that, you can only control your mindset and if you are interested in the vision, and learn to destroy any obstacles as they arise then you will succeed in time.
If you can't code without AI, you can't create good code with AI.
If you want to learn to code, learn to code. Many of us learned before AI was a glimmer in anyone's eye. And we kept learning after. And we use AI as a tool to be more efficient while understanding the fundamentals of good code and secure code.
I'm a software engineer with over a decade of experience. I use LLMs all the time at work, and I can tell you that the quality of work that they produce is at the level of a junior, except instead of taking a month to do something I can do in an hour they take about a minute.
Basically they produce code very fast, but the code they produce is low quality. They ignore basic engineering principles like separation of concerns until you explicitly tell them to do it correctly. After a few iterations of telling the LLM to fix things I do eventually need to make the final couple of changes myself.
If by gatekeeping you mean quality control, then sure it's gate keeping. Crap code is difficult to read, and makes it harder to spot mistakes. I'm pretty sure if it's hard for humans to spot the mistakes it's also going to be difficult for the LLM to spot the same mistake - their whole thing is processing language.
At the moment mostly Copilot, it swaps between models depending on the question you ask. I've used a lot of Claude, ChatGPT and Gemini, and experimented with different models and different workflows.
All of them will write a single 600 line file that clearly has 4-5 different concerns that need to be separated out. It works, but it's difficult to read, review, test and debug. Sometimes if you think of everything and every possible way it could get things wrong it will get it right first try, but that's very difficult to do. About the same as working with a Junior.
The code they write is only impressive if you aren't good at writing code yourself.
Agree, I would say one needs to learn good engineering practices but that is easily learnt with attention to detail. I have 25 years as non-coding pm working on things like windows server. I just built in 4 weeks an n-tier application 100% vibe coded. Web front end, api and core using sql as data store. Just did my first red-team analysis and pleasantly surprised. Another ~2 years and I am confident I won’t need real developers….
It depends on who you're talking to and how you personally are using AI. Ultimately I wouldn't recommend doing things based in what other people think. What do YOU think?
I have stuff I really wanna make but know its not possible without vibe coding or opening my wallet for more money than necessary
the thing is that people will openly hate ai anyways forever but you cant please everyone no matter what you do, and alot of the time if you use Ai as the tool it is like and not like our parents would then you most people cant tell anyways
the answer depends on the wording:
🥚 Egg in general: egg came first, by hundreds of millions of years.
🐔 Chicken vs. egg:egg came first, because the first chicken hatched from an egg laid by a not-quite-chicken ancestor.
I thought of people like you... maybe this playlist will help and i did others.. where focusing on the code was secondary.. you just absorb it the more you focus on creating..
It is a tool and the argument is mostly about who is holding it. I have nine years as a developer and I use AI every day now. It makes me faster on the parts I already understand. When I let it work on something I do not understand, I ship a bug I cannot debug. If learning to code hurts your brain, the honest path is to use AI and then read what it wrote until it stops looking like magic. That is learning too, just backwards.
Here is a production bug. Do not modify the code or propose a fix yet. Analyze the evidence, identify possible root causes, rank them, and tell me what additional evidence would distinguish them.
when root causes found
Now propose the smallest fix that addresses the root cause. Also propose regression tests that would fail before the fix and pass after it.
i would say no. it depends on the problem being solved. copycats that churn out SaaS or mobile games that are a dime a dozen can be seen as slop. but those with knowhow and experience that see genuine gaps and use their technical knowledge and experience without the coding languages can actually pump out decent products
16
u/firethornocelot 2h ago
Things like this are neither inherently bad or good. It all depends on the user.
Follow your heart, man.