Don’t ask AI to write your code

[@akialter]

Ask AI to write your code, confused why your code doesn't work, then actually learn by fixing the AI's hallucinated code

[@aldi_nh]

by asking the AI how to fix it

[@theholyjosh5384]

Practice for the future xD

[@UnityMMODevelopers]

AI can pretty decently write code. I have created entire social network sites using nothing but AI and they all work well. Sure there were issues and bugs but the AI was able to find the bugs and fix them. Once in a while I had go through and find the errors my self and prompt the AI on how to fix them but the majority of the time the AI could do it all on it's own.

[@DiThi]

This works occasionally, when the code is uncommon enough that there aren't many examples, but the algorithm is not too difficult to understand. I learned a couple of algorithms by fixing terrible hallucinations, but those are rare instances. Most of the time the problem is either just boilerplate and it's not too different from copying from stack overflow (back when it was good), or the other extreme where the code is so bad it's not enough to fix it.

[@cnh3547]

I agree, there's some truth and value to your comment, as seen with my son's experiences: 1. he spent a lot of time fixing the code of a Chat GPT using friend whose Roblox code (Lua scripting) wasn't working correctly (he's done this multiple times). His debugging skills have gotten so much better because of doing this. 2. His refactoring skills improved quickly when he helped a different group of friends when debugging their code to make it understandable, maintainable and to work correctly. He understands my "coder rants" now since he's gone through this firsthand. :P

[@wlockuz4467]

AI has taught me a very valuable lesson. Coding is less about writing code and more about learning to articulate a problem, the code itself is merely a means to an end. If you learn to define your problem well, then coding will be a breeze. If you try to code without figuring out what problem you're even solving then coding will be hell. This was also my experience with AI. If I didn't understand a problem, I would start explaining it to AI, while trying to make sense of the problem to AI, I would usually get a better understanding of my problem and be able to figure out a solution. I am not saying AI useless, I am more so saying that people really tend to underestimate themselves.

[@kalilsubaan]

This!! I find myself trying to explain the issue to copilot and while im writing i get a better understanding and already coming up with solutions in my head. So i end up not even sending my prompt at all 😂

[@aniket901]

For many people Issue is not only problem definition…. Instead its comprehending what code should i use to solve this problem and what logic should i use!

[@GosuNoKami]

Asking ai to do that first helped my code work (also by ai).

[@kebaba.k.atortilak2718]

I have syntax problem most of the time. I just dont know the syntax for something. Especially when i work in frameworks or with some libraries. When i use plain Java lets say, there is no problem.

[@ImpostorModanica]

That's called "rubber ducking"

[@ximon-x]

"Spending an hour fixing a feature that'll take users 2 seconds to use" so true

[@nogoodgod4915]

How many times I've thought to myself "Huh, that's all of them?" When explaining the features of my app I spent weeks building.

[@MrC0MPUT3R]

Lol bold of you to assume they're even using it

[@9tr0gen]

dude... i spent a week trying to speed up my loading time by a second

[@bromibromi]

@@9tr0genit’s not about the second it takes for the user, it’s about what your systems do lagging this second, and how much will it cost you in scale.

[@harrytsang1501]

We pulled in a 10MB library for a web app for a feature 1% of use will see and they will only use it once in the lifecycle of the user during account verification. Load time suffered until we made loading that chunk on demand and optional

[@nic3880]

1) use Ai to be ambitious and do difficult projects 2) fuck up 3) learn to understand code 4) debug successful 5) **feels the fear of not writing code yourself 6) forget the fear and do harder projects 7) do this until you are used to it Repeat step 1 to 6, and if your conviction is hard and you are too stubborn to give up, you can actually be dependent on Ai while able to program stuff

[@nic3880]

Actually, a really usefull project is integration Application as well

[@Luke27reborn]

i've been coding with claude and cursor with 6 months now. I have made a lot of difficult projects including a full stack online radio station with 20+ pages and a shit ton of features. I dont understand why people say ai "cant code a full project" when it clearly can and i did the whole radio in like a month...

[@nic3880]

@Luke27reborn yup, that's the thing, like nobody I've meet has this mentality man, Now because of ai, I'm able to create a full pipeline of data processing after specialist labelling, and then training, details I can't say

[@SamRFi]

​@@Luke27reborn I completely changed my workflow in similar way and never looked back. I think people give up way too fast on AI generation, but as other comment suggested, if you persist and slowly learn how to handle scope and context when interacting with the AI, you can get results much faster than would be otherwise possible. However it could be more energy consuming and potentially stressful as you are constantly analyzing output and code at a much faster pace than you would in the more traditional ways of coding. The change in pace might be throwing traditional developers off.

[@Josh-qv1bm]

@@Luke27rebornOut of curiosity what was the motivation for that project? Has anything come from it?

[@ammoniakdurum4542]

If you want to become a programmer, there is no way around: despair, feeling stupid, wtf is means that error message, despair, more despair, thinking that you are the stupidest person in the world, and the fu**** tutorial hell... .but then things get better and that shit starts to become really fun. So for anyone with the same level of resilience as me...keep going...this shit is worth it ❤

[@jl_117]

Agreed although I’m not that hard on myself. Programming is just fundamentally difficult. People need to understand that

[@potatochipappi]

As a new programmer…I’ve been hearing a lot about the tutorial he’ll, can you elaborate on what that really is so I don’t fall into the trap.. right now I have an app idea but I’m currently taking course on OOP done with regular procedural. I believe once I’m done with course I might try to follow up videos that build precisely what I want to build because I would understand the syntax and concepts… but does that post graduation study approach fall under tutorial hell as well?

[@paca3107]

​@@potatochipappi In my opinion people are in tutorial hell, because they dont belive that they are good enough to build something on your own. Ive been programming for 2 years and honestly never felt stucking in tutorial hell. Since I remember Ive been modyfying code which I wrote following tutorials, adding new features, looking dive into the code. Imo reading docs its much better than asking AI and every begginer should begin doing it as soon as possible.

[@archockencanto1645]

​@@potatochipappiThis is cope, you can't just take a course and then build something great. You MUST build smaller things. You will fail in the smaller things, there will be bugs, the html will be sloppy, the css will make it look trash and so on. Then, you do it again and slowly increase difficulty, then only after a few months of this, can you even think about beginning the total package you wanted to originally build. That's just how it works. The whole idea about tutorial hell is that ideas are embedded in working memory and then replaced after 5 minutes or 5 hours or 5 days. When you're watching the tutorial, or a video, or reading the documentation, you feel like you know something, even though you don't actually, then when you go to build, you realize "omg, I can't even write the meta tag", then you go back to the tutorial, and because the building part was super hard, you spend 5 h in tutorial instead of 1 minute that you needed, then you go to build again and repeat. What you need is concepts in long-term memory, for which you need to fail and tinker again and again and again. It took me hours over months to figure out how setInterval() really works for example. If I 'studied' it one day, then I still wouldn't know how it worked. But now, I can use it anywhere, anyplace, perfectly. The key thing is that you need to understand the fundamental structure of how things work REALLY WELL: What's the event loop? What is synchronicity? What's a 'this' binding? What's lexical scoping? What's the Box-Model? What's Margin-Collapse? etc. You need to know hundreds of the one line concepts REALLY WELL. The second key thing is that you need to be solution oriented not information oriented, if you don't need to know something(that's on the applicability side and not on the structure), don't go and look it up, lookup what you need, implement it, move on and repeat until you get good. If it works then it works, move on. This is not only a practical consideration or from a fear of learning , but rather true learning is application and not information. The knowledge will automatically come to you over months and years of figuring one thing out, your brain is not a computer that it will instantly input everything about one thing. Information is NOT knowledge, knowledge comes from building with it, using it, not reading or watching. It is a 10x better use of time to build something yourself than it is to watch a video of someone doing it. I put up front-end related things here due to the channel but it applies to all of programming. Advice from me: endeavour to make the course/watching/reading time be less than 10% of the total time spent, 90% needs to be in you fixing bugs, banging your head, asking chatgpt about how something works(NOT THE CODE TO COPY PASTE!!!), reapplying things again and again til it's good enough and building. Also, don't forget the thinking stage, spend a solid amount of time just thinking what the problem is, what the structure will be, what you need to do etc. Don't underestimate a pen and a paper, that's more important than the code. If you don't flesh out the problem and the solution, then after you build, you will realize that that's not what you wanted or that your architecture is spaghetti and that will waste 10x more time than the 10 minuts it would take you on paper.

[@XAMEREN]

> wtf is means that error message almost a javascript moment, one might say

[@Vertual001]

I worked for AWS in Madrid as a Professional Cloud Solution Architect. I felt dumb 90% of the time solving problems, but when I succeeded, I felt like Einstein.

[@bithon5242]

Same except I worked at Google in Madrid

[@duckdoan7977]

May I ask if you took any AWS official cert, associate level or higher. Thks in advance

[@cryora]

But to get hired you have to convince your hiring managers that you never experience that 90%.

[@Vertual001]

@@duckdoan7977 Thank you for your question. Like my former colleagues, I started with the basics, beginning as a Cloud Practitioner. From there, I advanced to Solution Architect and eventually achieved the Professional certification. Earlier this year, I specialized in Security and successfully earned the corresponding certification.

[@Vertual001]

@@duckdoan7977 Somehow my comments are being blocked. Yes, I archived all of the necessary certifications.

[@BryanSchmidtSchmidty]

I think the advice in this video is mostly for people who are still in the learning phase of writing software. Sure, we are all always learning, but as a senior developer with 20+ years of experience, I depend on AI a ton. Not to write code for me because I don't know how to write code. But because (for example) I know how to solve the problem and I know it will be around 100 lines of code, but I want to save time. Have AI write it for me, and I review the code. ChatGPT and Copilot become my Junior Dev, and I'm the code reviewer. I think the crux of the issue is that you don't want AI to become a crutch. If AI were taken away tomorrow, would you still be able to perform your job? Same with Google, or Stack Exchange, or KZbin? I can confidently say that 100% of what I code, I could do on my own without the use of AI or Google. But now that I have these tools at my disposal, I will use them to save time and increase my productivity.

[@CW91]

Depending on GPT is one thing, but I would still need to depend on either Google or Stack Exchange (KZbin tutorials are quite limited scope). Official website documentation can be quite lacking sometimes, and even have errors. It is only when someone asks an issue in the forums (e.g StackOverflow) then only the crowd points out that there is a discrepancy or bug in the library or framework. But yeah, I agree that developers should build understanding from ground up instead of starting their learning at the halfway point.

[@oksdoksaodkad]

And this is what people don't understand when they say 'AI isn't going to replace programmers'. Yes it will, instead of a company now requiring 20 SWE's they will only need 4 - 5 - so AI has replaced software engineers, then if these LLM's get better then the company might need 3 - 4? Then possibly 2? Same as cashiers in supermarkets, self-checkouts have drastically reduced the amount of cashiers needed.

[@RawrxDev]

@@oksdoksaodkad 20 going to 4-5 is a very optimistic amount, even the less conservative reviews find only around 25% increases in productivity, thats not any where near the 80% you said.... with a 20% increase (which in all honesty I still find on the higher end of whats realistic) you essentially weed out the successful companies from the failing ones... A failing sees a 20% increase as a way to cut costs, a successful company sees a 20% increase as a way to expand cheaper, now, a big project that was in the backlog, only needs a few extra hires and a small staff change from other projects to get going.... increases also create jobs, if that wasnt the case then nobody would have a job, surely you dont think productivity is even close to the same as it was 100 years ago, or even 10.... tools increase productivity all the time. it also depends on the industry, im sure web development find a lot more use with OP's use case then someone working on a satellite. Code monkeys are gone sure... but real programmers are not even close to leaving... these models have not seen a single increase in true reasoning.

[@trip_t2122]

​@@oksdoksaodkadman f AI 😂😂

[@whosajid]

Yes, yes and yes. Thanks a lot for watching and giving your feedback.

[@CW91]

2:23 "Before ChatGPT, we have Google, KZbin and blogs..." Before Google, KZbin and blogs, people had those O'Reilly books that they read through chapter by chapter, and kept them in their computer desk drawer.

[@whosajid]

bruh 💀

[@IogaMaster]

Ask Ai to help you understand code, not write it. Having the knowledge of many stat structures or designs at your fingertips is amazing

[@JuanSumChninezeFue]

Asking AI to help you understand code is beyond a nightmare, as their analogies are atrocious. A simplified and broken down version of code with comments for each line allows the user to ask specifically what each line is doing. More often then not, the watered down version of code is the catalyst for understanding as it branches comparisons together. "Oh, so this code is just that code +/- x features. Now it makes sense."

[@TheAtticus82]

I’m so happy I didn’t have to be a beginner in the era of AI. It’s a fantastic tool, but almost exclusively a good idea for people who are pretty senior.

[@Skullizer]

If you use AI to teach you the basics and ask about everything you don't understand instead of just letting it do all the work, it's actually a super powerful tool for beginners. It's all about discipline.

[@Ghostylies]

As a beginner i'm a bit worried about how to use it, most of my profs encourage utilizing it but never really tell us how to.

[@juanfp]

​@@Ghostyliesuse it as a teacher with endless patience: you can ask it for as much detail, examples, and as many times as you need.

[@_MB_93]

True - for beginner, but AI writing codes is extremely useful for someone who has already been doing it for years

[@whosajid]

yes

[@SmilerRyanYT]

As long as you can understand what it's writing and actually treat it as such template code then you're fine. but as a beginner you still should learn from rather than just paste.

[@cslearn3044]

Issue is overcomplicating stuff, find an idea on what you trully want to make, and you will find a way how to guarantee. You can ask chatgpt how to make it but dont use it for code, but roadmap

[@XetXetable]

You should absolutely use it for code, just don't let it be creative (unless you're brainstorming). I find it's much faster to give a thorough english-language description of an algorithm and have chatGPT (or claude, which is more reliable) write the actual code than to write the code myself. It's just as good at getting you to think through the problem, and you don't need to get hung up on remembering all the syntax and function names. LLMs are pretty good at following clear, unambiguous instructions; it's the following of vague instructions that'll lead you to where you don't want to go.

[@osterhai]

chatgpt is good for learning in my opinion but too many people just take its code and keep throwing prompts at it until it fixes its own half assed code. But chatgpt is great if you give it for example a code snippet that you dont understand and ask for an explanation or if you let it write code and then ask for an explanation. That way you will learn a lot about programming and also gpt isnt good for bigger projects as they often require more specific tools that gpt isnt too familiar with.

[@whosajid]

This ☝️

[@Teodor-ValentinMaxim]

I think you're more rewarded in the long term if you actually try to digest information without the help of an LLM.

[@wuukaa9079]

The joke is that I had an ad about learning to code things with ai/ no coding before this video

[@whosajid]

😂

[@YourCRTube]

Let me give you another PoV. Part of the problem is the web development itself. It has ALWAYS been about A) Quick solutions B) Ready-made solutions. Always, since 90s where you can inspect the source of the page - something unheard in "normal" programming. This has pros and cons, pros being the insanely rapid development it brought, cons, well, hacky code, mind-numbing resource consumption, compered to the actual work done, etc. When this is the norm, no wonder the AI will first conquer web development. And again, before AI there were the frameworks, the templates, the CMS, arguably even the UML code generators - all tools which take development away from the developer. Noone writes a page from scratch for 25 years and the AI is yet another of those tools.

[@whosajid]

Yep, So true. Sadly I also just do web dev. You sound like a pro from C, C++ or Java background.

[@MadsterV]

I'm always amazed by the convoluted systems and excess of libraries used to do the simplest things. A senior programmer should know that a larger library does not mean a better library, yet I see bloat again and again, often fueled by the fear of a project being considered "dead" if it's not constantly enlarged. A breath of fresh air from this is Rust, where libraries that are working fine and don't need more changes are NOT considered "dead', they're considered DONE.

[@Dan-nv7ns]

I needed to hear this with the project i am building. Gonna change my approach and try to write the code myself. Break it down first and lay out the steps, then build it myself.

[@GaiusIncognitus]

I'm a professional copywriter and an amateur/hobbyist programmer. Every single thing you said applies equally to words and code. Great job saying so many important truths and giving concrete examples people can actually follow. Kudos. I'm writing this comment to support you spiritually and algorithmically.

[@whosajid]

🙏

[@alexeydomofon4400]

Thanks a lot! I recenty found myself asking ai just to build a project for me, and later couldn`t figure out how it works. You motivated me to actually learn, instead of copying

[@foodlover195_]

AI is an amazing learning tool. The best way I've found to use it for learning to code is to ask what / why questions first - or even how questions explicitly stating to leave out any code. As example, recently I was creating a REST API from scratch and instead of asking "build a secure API in golang with x.y.z endpoints", I asked "I am trying to build a secure API in golang. What security issues should I be concerned with when accepting user input, and what are the best approaches for dealing with them?" It's great for getting a greater context and providing information of things you didn't even know about - in my case I knew about SQL Injection and the importance of dealing with security (hence the question), but not in great detail i.e I didn't know about Cross-Site Request Forgery (CSRF).

[@DetectiveConan990v3]

i made a project that was totally ai and i understood nothing. but recently i have started to make my own project using the same technology as the ai project but this time without any ai. it has been much more difficult but it is a lot more rewarding

[@p3ter408]

😂😂😂

[@DetectiveConan990v3]

@@p3ter408 whats funny

[@Efandr]

Good for you, bro 🔥🔥🔥

[@DetectiveConan990v3]

@@Efandr thanks bro

[@Likemea]

this is why ai prompters infuriate me, ai is not here to replace, but to help, yet they want it to do everything for them

[@darkstorm1432]

I agree.

[@darkstorm1432]

if you are just using ai your code will reach a limit anyway x)

[@mage3690]

TBF help vampirism has always been around, AI has just managed to give help vampires an easy, safe, fast place to go. It's done the help vampires no good, and in fact done them a lot of harm, but I suppose the market will fill any need it can find.

[@kagame6524]

As an experienced engineer, this capture the initial frustration sometimes when learning a new framework and tool. It’s normal to fuck around and not have it work for a bit

[@Trickproof]

glad you mentioned tutorials here because it's the same problem where people just follow them without trying to do the projects on their own first. even if you do the work on your own, having someone tell you the answer instead of figuring out what works by yourself can still give you the same problem.

[@-8978-]

I struggeld to start learning programing for years, it feeled like i am to far away from it. As soon as i heard you can AI code your projects, i tryed it. But it never worked, the way i wanted. So i had to read the code, google it, let AI explain it to me, until i could fully understand modify and have a success. I am having a really hard time to code with out AI. But i would have never started to code without AI.

[@Sol4rOnYt]

chatgpt is honetsly stupid at coding. it uses weird functions and arrangement, starts hallucinating a new method that literally does not exist or just can't seem to debug anything by itself. However, it is useful to talk to and send YOUR code to check if its efficiecny and ensure the logic is correct, and you cna put in it's memory "dont send me code"

[@DanielDogeanu]

You seriously underestimate what ChatGPT can do! In order to get quality code, you need to ask quality questions! You need to be real specific! Focus on that!

[@AD-wg8ik]

I got the paid version, it’s pretty good.

[@RawrxDev]

@@DanielDogeanu Id rather spend the time thinking of a crafted question on actually solving the problem...

[@asdfqwerty14587]

@@DanielDogeanu The problem of course, is that coming up with a specific description of what you want to make is basically the same task as coding it yourself. If you know exactly what you want a program to do just writing the code isn't difficult at all (well, in most circumstances, but in the circumstances where it still is difficult are not the kinds of tasks you can expect a LLM to solve either).

[@DanielDogeanu]

@@asdfqwerty14587 I think you confuse matters... Of course you're going to code it yourself! But ChatGPT can help you do that way faster, and provide you with great code, if you know what to ask. You can't expect for ChatGPT to build the entire thing for you. We're not there yet. And even if we were, you'd still have to write a book with the precise details. The idea is to break things up into smaller pieces, and ask ChatGPT for those smaller pieces, one at a time. You'd be amazed how fast you can build an entire application that actually works. You can also ask it to help you debug things. This is precisely how you build an entire app by yourself, from scratch, without the help of AI. You break big tasks into smaller tasks, and you build them one by one. You iterate and refactor your code as you progress. ChatGPT speeds up this process massively!

[@jshowao]

I think the use of a debugger is hugely overlooked. People need to learn development tools. Using a debugger helped me immensely. A lot of people also take on way to large and complicated projects early on. They dont try and learn language features and how they work initially.

[@whosajid]

Extremely based take

[@asdfqwerty14587]

I think it depends a lot on what you're working on. I think if you aren't working on a project that takes a long time to compile/build it's way more efficient to just add some logging and rebuild it than it is to mess around with the debugger.

[@jshowao]

@asdfqwerty14587 It isnt because if you know how to use a debugger you can, very efficiently, know how your system behaves at every conceivable level without having to write a bunch of logging code. The whole point of logs is to give you a high level overview of what exceptions occurred and some high level program execution information. Its not meant to log the entire state of the program such as thread, variable values, heap state, stack trace, etc. Why would you waste your time creating all this when you already have a process that can do this for you that has been vetted for many years? Of course it depends a lot on what you are working on, but we are talking about programs with considerable lines of code (in the thousands to millions) Also, I dont get how long build time is resolved by a logger. You still have to build the program and run it to generate output from the logger. So its no different than a debugger, except with a debugger I have total control of the execution flow.

[@iken1308]

I think it's really more of a convenience type of choice, As for my case, this video got recommended to me. Me and my friend are just trying to make a little infinite platformer, rpg like mobile game. I'm not willing to go through coding just to learn how it works, nor making it my career so I just use chatgpt to code and messed around how godot works cus obviously chatgpt can't do it. I just wanna do it for fun, my friend also wants to learn about his side of this project which is pixel art. But the part in my side actually involves making the game in godot, Tbh I understand AI being super helpful but more of a braindead solution to some, I agree with that but it's pretty situational ngl. Thanks for reading all that, here have a cookie 🍪

[@thechosenone729]

Breaking down the problem is what helped me to get away from tutorial hell. I was telling my self what is the simplest app that i could build something that i will not need anything for just documentation and that's it. It was bit painful but when i finished my first app it clicked to me and i stopped using tutorials and started building my own stuff which as you said provided that dopamine hit. When it comes to AI it's the opposite i tried it and when it shown me a result i didn't feel like continuing the project anymore because it wasn't mine anymore. So i deleted it and rewrote it. I will never use AI for coding it almost killed all the excitement from it for me.

[@jameswatson6111]

I need this as a Mid 20's and student that always relying on AI. I should gradually do it on my own. Thanks!

[@askvalentindigital]

This video made my want to start a project in python, I haven’t coded in a little while but this perspective is the GOLDEN NUGGET

[@BloodswordFW]

I started my journey as a developer 1 year ago in a small company that has 90% entry-level devs. Nobody would bother about code reviews, testing and QA and there was nobody we could ask for help and get it. That is where AI shined. Not just copy-pasting the code but by actually using it effectively, it helped me from barely able to create a crud api to building full-stack apps, deployment and testing as well.

[@girishkuvalekar3965]

Don't use windows 11, build yourself Don't use laptop, build a PC While building a PC, don't purchase components, Design Youself While designing components, don't use naturally available elements, prepare all elements in the lab just to call them synthetic and fit them into your requirements. Ego can take you anywhere, tasks have deadlines and no harm in using advanced tools to finish tasks on deadlines rather than looking for self pride. Understand Your dependency is endless. We usually don't code for self pride, we do it to automate repetitive tasks.

[@benismann]

You wont believe how many ppl just have AI generate code and then ask why it doesnt work

[@whosajid]

Don’t comment unless you’ve watched the entire video. Don’t bother watching if you lack common sense. This video isn’t about ego - quite the opposite. It’s about embracing the reality that coding is hard, and there are no shortcuts.

[@girishkuvalekar3965]

​@@whosajid 02:51-03:31 Plz listen yourself

[@danser_theplayer01]

As an enthusiast hobby coder who wrote only vanilla javascript for 6 years, for browser and node, I second this video.

[@levonoxelr5834]

Even when using AI to generate the code, it's still a pain in the ass during the design process. Because gpt, as a machine, cannot generate a complete product on its own, it can't just magically finish your coding assignment in one or two prompts. After multiple times of doom-prompting (ask gpt to generate the code and spamming prompts until it works, most of the time it doesn't), begging the AI to write the code that works as a whole (dumb shjt ik), I've realized that I can break the process into multiple smaller problems, ask the gpt to write the simplest codes possible, then I apply that logic into what I'm trying to build. Sometimes it works, sometimes it doesn't and I have to write codes on my own :/

[@zazakh7804]

Thank you. I am currently struggling with my JS learning path and I was kind of giving up to AI as I felt that I never would be able to understand how to use and combine different things, but your video was right on time ! Thanks a lot

[@SomeOne-p6f]

For most people, I would suggest that the number one requirement is to have what other people might think of as insane levels of perseverance. When others give up, you go back and you go back and you go back. Some days in the beginning it might feel like your mining through granite and then like learning to ride a bike, all of a sudden you can do it. Ok, that last bit is a lie, but it gets easier.

[@shazmimain8293]

Another tip that I would like to follow up is to question everything you do when following a tutorial. And be OBSESSED with the little things. For example lets say you wanna write a function to handle form submissions by writing: function handleSubmit(event) { event.preventDefault(); } Now question yourself to a point where you have almost no question about it: Why do I need event.preventDefault()? What does this line do, and what would happen if I left it out? How can I implement this in anohter sample project? Can I modify these even further? What I usually like to do next after understanding a simple concept is building a quick small form submission website using what I just understood to deeply test your understanding. After truly understanding that concept inside out, resume back your tutorial and rinse and repeat for every new concept that you encounter.

[@RedactedBrainwaves2]

When it comes to JS stuff like that I like to track from which object the method is called, so I do a quick read on the documentation and try to figure out what it's doing under the hood.

[@samcraft3]

yeah I personally use AI for this. I throw the entire documentation for a particular library and ask it to help me whenever I want to create a particular thing without having to search for it in the documentation, and I ask it "why do I need to write this specific line?" "what does this function do?" "what happens if i remove this?". if it hallucinates a random answer then i go search for it on the web. The advantage when using AI is that it just follows the context, when in the web it can be a totally different concept. I learned how to use ThreeJS just by reading the documentation and asking chatgpt to help for a project.

[@TheLiverX]

Reading documentation or how-tos for very unfamiliar things is very good and is never bad. Even more, being able to tackle the new challenges fast is excellent. Whoever can build a decently sized app without looking up anything is a literal god.

[@jakub2631]

good stuff, I'd love to see your channel grow. You just earned a subscriber.

[@elixerprince_music]

I'm currently learning MERN and it's so hard because I have to remember all these functions etc, Even on just the basic beginner project of a product database app. My approach is deleting my folder completely and trying to recreate it as it was before, while asking AI why certain stuff was done. I did this about 6 times now and am at the API stage, but it's a bit difficult to remember all the details. Having the VS Code Blackbox AI extension helps, but I try not to rely on it too much, and I am contemplating simply disabling it till I get the basics down fully. At the moment, I feel a bit more confident knowing my skills are growing and that I'm getting better daily, but it's a bit rough since I wanted to become a frontend developer solely. On a good note, I can now understand exactly what the tutorials I watch are doing in terms of the setup, even from different KZbinrs. At first, it was like a jumbled mess of random code. I hope to refine my skills even further so I can create something impactful!

[@gregoryam]

Lately the way I've been utilizing AI: If I get stuck or can't get past a road block. I'll ask ChatGPT or SourceGraph Cody to give me an idea of how to fix or complete the code with detailed comments. Then I will go through and write out what it gave me instead of copy / pasting the code. I was feeling dependent on it for a moment to write everything I needed. With some errors that would come along, I would ask the AI to explain the code and how it works, then I would go to the documentation and search for the parts it mentioned. I started to depend less on AI, and just have it there as an explainer or as a guide to possibly push me in the right direction. I started to keep the docs open first.

[@themageofspace5516]

I think AI does have a valuable learning side but this doesn't come from asking it to write for you but rather help you understand others code or explaining concepts that previously didn't make sense. I've been learning Rust and having chatgpt explaining some of the things in more layman terms has helped me a lot to begin to understand rust very rarely have i used it to try to answer questions. Also one thing i like about chatgpt is that it tells you why it does stuff, if you are using it READ THAT and try to not just copy it but understand what it is writing.

[@boxguytv]

I use AI sometimes, it taught me a few concepts I never even knew about and it helped me implement them by myself.

[@tsob5111]

i'm not a very good dev yet, but i find it fun to actually make something. if i want something done i enjoy learning how to do it as well, same goes for any other hobby like art or cooking or what have you. fuck around and find out enough and look here i've got a new hobby alongside the project i wanted to have finished

[@vv_ife]

I usually use AI to check if the code I wrote can be simplified and less redundant, to check if any part/line is unnecessary.

[@llamasarus1]

Chat gpt helped revive my game programming hobby. I asked it to show me how to build an ECS and I learned some cool stuff and although it wasn't very optimal in some areas it introduced the core elements so when I took an proper online course on building an ECS I was ahead of things and it smoothed some things over. Now I'm trying to rewrite the core engine just by thinking through it's concepts rather than memorizing the exact way it was shown to me.

[@makcings4764]

Ai is useful in learning basics and getting small assistance, i wont make gpt generate whole code for production but treating it like a another search engine helped me a lot

[@itfitness5791]

I like to always start with the docs to solve something, if that fails I ask AI, then revisit the docs with that information

[@its_abdu4925]

I think that development is a slow process, people want to build as many projects as possible, its like reading a book, if you read 10 pages a day and grasp what the author want to say, isn't like reading a book in one day, The benefit will never be the same.

[@ArrowOnionbelly]

Thank you, I needed to hear this

[@aibotsaimbitigrid8554]

This ai era is like the white coke of every developer u get addicted then despair

[@ravihlb]

Excellent video. Thank you very much. I feel like it has reached me in the exact right time as I'm planning out and starting to structure my first fullstack app :D

[@vladyslavbrataniuk1324]

I feel so lost and burned out last days. This is what I needed to hear

[@SheeceGardazi]

best thumnail ever ... i knew i did the right thing when i subed this channel

[@Room240]

How do I tell you that I'm using AI to write the code for my graduation project!

[@aducaale328]

Thats what I am doing now. my project is almost going for a year because I am learning while I am developing. I never write a code that I don't understand it's concept. Thanks for this great content 🙏🏽💯

[@whosajid]

Longterm gains over short term pain

[@imluctor5997]

you need to make your own projects aswell. I did a project from yourube then i tried my own small project. Had to rely on stack overflow a lot but i also learned a lot.

[@MSD-k5b]

I use co-pilot, which I use mostly to learn new stuff. For example, I recently started working on Ruby on Rails and Co-pilot is quite good at telling you different ways to write a piece of code you just wrote, using language-specific features you were not aware about.

[@zackfarmer9106]

Ai can be helpful as a "quicker google" Dont go with "GPT, I need x or y feature with these parameters write it for me" Instead go with "What are some best pratices or ways to do x" Youll get at least one solution. Then you can go from there to build your own.

[@danser_theplayer01]

I use AI all the time for googling, I can't remember every single thing in the scripting sister language of Java, made in 1999. AI is indeed bad at writing the exact code you need, or sometimes it will write code that doesn't even work (literally throws). It's nice when used to get a general idea of things I might have missed or never considered trying.

[@CamTooling]

Most companies don't really care about your coding skills. They care more about your problem solving skills. If you're a good problem solver and you use AI to produce good end results, that's all that matters. Good problem solvers should know how to even solve the problems with AI generated code and how to use it to their advantage.

[@whosajid]

Really?

[@Teodor-ValentinMaxim]

That's wrong. Doesn't matter how much a problem solver you are, because you are obliged to solve the problem in a certain kind of environment; if you only know the concepts, but you don't know know the language, then you're stuck. And you can't rely to program through prompts, because at the end of the day, you need to know exactly what you're looking for and how the code should look. L take.

[@CW91]

@@Teodor-ValentinMaxim Yes, I would like to add on top of that. The thing that makes coding harder than it seems is because computers are unforgiving when it comes to wrong code. If we write an exact same code from the internet, but in the wrong scope, then the compiler will not pass, or the code will work in a weird manner. Computers cannot understand implied meanings if we are not specific and accurate to the fine details. We can tell a human "go make me a video streaming website" but we can't tell the computer to do that so simply.

[@whosajid]

@@CW91 Exactly, that's a great point. Programming is brutal, not because humans are not smart enough, it's tough because computers are very stupid. It's much harder to explain something to a 5 years old child than to a 25 years old adult.

[@juanfp]

For me, the most useful part of using an AI chat is having to put into words exactly what I need.

[@democracy_enjoyer]

- ask chatgpt to write you code - code doesnt work - get confused and learn code to debug - realizing you learned code and no longer need to ask chatgpt

[@gtrguy17]

Use Ai as a tool to help you understand how to code. Don’t ask Ai to write all your code. Instead tell Ai what you want to build, Ai will give you a step by step list how to transform your idea into code. When Ai gives you code ask it to explain the code line by line. Pretty soon you will be able to look at a block of code and figure out what it does pretty quickly. Build stuff, ask questions , get answers, rinse and repeat.

[@whosajid]

based take

[@johnny_boi77]

1:07 lmao showing purple guy as an example

[@QuiescentEntropy]

If you dance I’ll dance

[@MatthewKelley-mq4ce]

Regarding 'misuse' of AI we all have to learn what works and what doesn't work in our own frame at our own time.

[@softwareengineer8923]

Golden content, thanks a lot👍

[@rz_7890]

In my opinion, as long as you can survive, that's enough. Maybe many people think that not asking AI is good in the context of learning and practice. But not in the context of industry. When you have entered the industry, whatever you do, whether it is using AI, Google, tutorials, etc., the important thing is that what you do is "finished" and has good quality, of course you have to understand what you are doing.

[@0xb1sh0p8]

Great video..I'm going to share this with my Dev team. AI is truly bad at doing any complex coding and what you're left with is an application you don't understand which makes it hard to find/fix issues. As bad as it is at creating good code...try asking it to refactor code and enjoy all the breaking changes it introduces. AI doesn't think, it regurgitates.

[@whosajid]

It's just autocomplete on steroids

[@costantinoserafini2252]

Thanks man, I needed it

[@abhishekak9619]

programming is like the one thing where you are forced to look at what you did before and try to mess with that as a simple part of the process. most things in life you never need to think about how stupid you did something and really try to improve on it and interact woth it dorectly, in fact if you try to get around this single part thinking you will simply write more , you will never improve fast enough to enjoy it. even though it feels like hell trying to think about what you did like 20 minutes before, its like really important to not skip this part. just keep trying this part like for an hour. dont try to sideline it and you will improve faster than everyone else. interact with it, think about actually still trying to make this pile of trash that you wrote work, keep trying. dont skip it.

[@olabassey3142]

What ive learnt from trial and error with ai is to write code step by step with ai so for example if i get a codebase i dont understand I ask ai what part of the code does "so and so" Then it shows me Then i ask it to make a change to it. This is something i can figure out myself. But now i can have ai do that small task. And thats how i complete my projects. The bigger the changes the more likely it will hallucinate so take it step by step and u will make less errors, understand the code and complete ur work faster than someone not using ai

[@codeyalexander6793]

I think there is an important distinction to make. Using AI to write code and never learning how to write or understand code is not good, you will spend much longer trying to get AI to understand the specific features you want then it would take you to learn to code. However AI is a powerful and versatile tool that is capable of processing things faster than any of us could comprehend. Using AI as a tool should not be discouraged, you can ask how something works, or to refine ideas and concepts. It is essentially the next iteration of using google to make things easier and more efficient. You should know how the code works, or you will never understand what you are presenting or making in the way you should, but AI should absolutely be used. Consider it being someone 20 years ago telling you not to google things because it was only going to hinder you in the long term. Those who use AI to enhance their learning will outperform those who dont, in the same way as those who used google to enhance their learning outperformed those who did not. Embrace the performance that AI can add to your toolset of you WILL be left behind.

[@whosajid]

Thanks for writing this

[@MeKebabman]

This video is great to be honest.. just what I needed cause I am in a burnout currently

[@dendomegaming7514]

How I actually like to use ai is first I write my own code until it’s works than give it to chatgpt to improve it so I can see where I can make it better

[@naomarik]

Before we had framework programmers. Now we have AI programmers. Most people aren't going to follow your advice but the ones that do are going to be able to keep delivering features and keep production online.

[@KennyCarter90]

I was talking with someone a couple of weeks ago who was saying I should use AI to help me learn Python (I'm an FE dev). I tried to explain to him that AI can't teach you anything and there are some things a person just has to do by themselves. ...I really don't think they got it.

[@sathnindukottage711]

Sometimes, higher time complexity or irrelevant responses may receive, which is why human logical reasoning should monitor the AI outputs, treating GPT as a "newbie intern" (as of 2024). What I usually do is, instead of using natural language to describe a task, I craft the code myself and then send it as a prompt, asking GPT whether it has a better solution or to complete the task based on the given code. Monitoring and guiding this "kid" is one of the best practices a human engineer can adopt.

[@sathnindukottage711]

Also, if AI doesn't work, try Stack Overflow. There are "HUMANS" there.

[@Armm8991]

The reasn i learned how to code (poorly but still learned) is because i wanted to create an editor for a file format that didn't have any, which led me to an insane rabbit hole of reverse engineering file formats, hex editing and python. A good time.

[@laelmedina2641]

"Are you trying to replace yourself?", what a statement. Using AI to code for me is not helping me at all, I'm becoming dumber as the AI is becoming stronger.

[@LmanTW]

Explaining to a language module what I want is just way harder than writing it my own

[@VoLcaNiCGamingyt]

At some point using AI to write your code is very beneficial. If I need 1 hour to write some code but with AI I can do it in 10 minutes there is no reason for me to do it myself. But for learning to code I do agree AI should not be used very often

[@whosajid]

This 👆

[@KDTechverse]

Basically, use AI as a teacher not as a replacement of your own intelligence. Thumb rule could be put as : ask questions, don't instruct

[@STEMPEdu]

Yes, no matter what, until it works

[@ricoLbrc]

Before, I only asked AI for a roadmap and didn’t rely on it for coding. I was doing well with other languages and even built my own projects without AI. But everything changed when I reached my third year in college, where I had to learn PHP entirely on my own, without any help from professors. PHP really put a damper on my passion for programming.

[@VideosViraisVirais-dc7nx]

A damper?

[@felixluna4184]

Why did you have to learn php... its terrible.

[@chrollolucilfer1794]

Where can i learn php? Any suggestions?

[@idkcoder]

@@felixluna4184 what everyone just hates on that programming language for no exact reason

[@harishjr2]

Same story for me too lmao

[@Axistential]

I have used AI to write code before. It didn't work super well, but it was really helpful for explaining things that KZbin videos didn't. Believe it or not I cannot find any information that made sense to me on what pip was Or how to download it or use it. But then I asked chatgpt And it explained it really well and helped. So long story short, it's better To use ai to explain certain functions of code Than use it to to code directly.

[@xard64]

Also never fall into the trap of thinking that things should be done only always in one perfect way. It's helpful to see fresh perspectives (ways that are possibly easier or faster to write) on areas of coding which you already rather familiar with.

[@B0re_d]

Asking AI for something else than generating input data based on schema or reformatting a file or piece of text when it comes to programming is pure madness

[@rohamhadidchi1196]

a very deep truth applicable to almost any area of life

[@kaustavmahata4138]

the thumbnail is lore accurate

[@martinohlund9382]

Lol looks like OP is salty about how everyone can do his job now. I don’t know how to code but have built several complex systems by itterating back and forth with the AI. The thing is it’s not as easy as you might think to get everything right. However just like you become better at writing code by coding yourself, you get better at itterating with the AI by using it a lot. Also as many have said, you learn by debugging too. I understand a lot more of the code that AI writes now than when I started. Could i write it myself? NOPE! Can i read it and understand what it does? Yeah for the most part. Don’t be afraid to use AI. Embrace it.

[@whosajid]

Nobody is saying to not use AI, just don't use it to write code that you don't understand at all. And OP is not salty, he is the OG man.

[@HikaruAkitsuki]

You can't even use AI generator if you don't know what are you doing nor you don't know what is your end result.

[@flyingtruce]

I keep asking AI for help with my js code, but while a trained AI cannot learn anything new, I am slowly surpassing it by learning from it. I can do everything that it can't

[@aliyaperetch8016]

I don't. I ask it a question, and it gives me an entire code.

[@vladislavkaras491]

Thanks for the advice!

[@DontWorryBouttaThing]

I think the most important take away is (Yes it's ok to have ai write your code) but learn what the code does and how to alter it.

[@devonglide1830]

I’m a teacher that writes some code for my class. It’s definitely a hit and miss endeavor. Sometimes it saves me a huge amount of time doing things I’d probably never be able to do, and other times I find it chasing its tail. Overall, for me, it’s been a net positive.

[@UnityMMODevelopers]

The reality is AI IS going to take over programming and Web Development. THATS the bottom line. We might as well adapt and get with the program. Figure out how to get AI to work for us instead of trying to fight a losing battle. When that day comes that AI does completely take over would you rather be the one who fought it tooth and nail and ends up out on the street or would you rather be the one who has years of experience getting AI to work for you so your skills are very much in demand?

[@relaxgameing8395]

Yes you said right but to develop cognitive abilities you need to use your own not that of AI , and you can always learn how to use them but to use your brain you need to train it for years so our main goal still should be to learn rather than just use tools

[@jeffreysmith9837]

Years of experience getting AI to work lolol stfu

[@cryora]

AI still refuses to admit that high ranking officials leak secrets for publicity and narrative shaping and no one persecutes them.

[@ojgfhuebsrnvn2781]

This is random video for me and I do not code anything but it reminded me of university, where we learned Matlab. We had no prior knowledge of it or any coding but teacher gave is separate tstks that we had to do over few weeks, googling everything that is needed but the most important part was that we had to write comment for each line to explain what it does (so even stolen code will be understandable) I got task to create billiard game where I have table, balls and by entering angle and power of shot it had to draw animation result of that hit. Unfortunately I had to steal few lines for code from internet because when ball hitting walls it had to go in other direction and I was struggling to flip coordinate system (basically my ball received direction after collision mirrored of what it's supposed to be). It was a fun project, I enjoyed it

[@whosajid]

Wow, thanks for sharing.

[@rx808]

thank you for that vid homie