That’s cool. It doesn’t sound like you are vibe coding because you don’t expect a working code, rather using LLM to learn more about coding in general. Is there any technique you learned to make it go faster or work better thru that process?
I would describe myself as close to the person you replied to in terms of skill level, and have been using llm’s in a similar fashion to the one they described, and get great results. I think the key thing is to know enough to understand what is happening, and see where the llm’s limitations are, and use it as a learning resource to actively improve while using it. Then be as specific as possible when asking questions.
Not only is it great in terms of getting working code, I have found chatgpt to be the best teacher I have ever had! (Because of availability etc). I think they must have trained the llm’s I have used on a lot of computer and coding sources.
I think the key is to learn at least the basics of coding first.There are scores of 5 to 25 hour long courses on most major programming languages on sites like udemy. Coding can definitely be hard to get your head around at first, but stick with it and do as many of those as it takes, or a night class or something.
If someone isn’t prepared to invest a week or two (in truth I spent a lot longer than that studying coding but I wan’t particularly time-efficient in my prior learning), then treat the llm as a learning resource, then good luck! I would guess the llm will be able to come up with any idea they can anyway soon enough!
That’s cool and I would say I mostly agree, I am also going to add a couple specific pointers that I consider practical: use ChatGPT on a desktop in a browser, use VS Code and extensions, keep ChatGPT instructions OFF the CLI so you don’t end up in a loop of running CLI codes and reporting back to your SupervisorGPT, make deals with ChatGPT in terms of complete code files and check every line, run midnight commander in a separate terminal and pay attention to permissions and ownership, force ChatGPT into lock down checklist mode and force it to go step by step, focus on the BIG picture with ChatGPT and don’t let it runoff to the next shiny object before you completed and tested everything that you wanted to do and hardened before you listen to the next bullshit suggestion prior to project completion. It’s not all bad and it does help you learn and punch above your weight class, but it can be downright infuriating and is by no means a turnkey solution: my two cents. Nobody going nowhere doing nothing.
That’s cool. It doesn’t sound like you are vibe coding because you don’t expect a working code, rather using LLM to learn more about coding in general. Is there any technique you learned to make it go faster or work better thru that process?
I would describe myself as close to the person you replied to in terms of skill level, and have been using llm’s in a similar fashion to the one they described, and get great results. I think the key thing is to know enough to understand what is happening, and see where the llm’s limitations are, and use it as a learning resource to actively improve while using it. Then be as specific as possible when asking questions.
Not only is it great in terms of getting working code, I have found chatgpt to be the best teacher I have ever had! (Because of availability etc). I think they must have trained the llm’s I have used on a lot of computer and coding sources.
I think the key is to learn at least the basics of coding first.There are scores of 5 to 25 hour long courses on most major programming languages on sites like udemy. Coding can definitely be hard to get your head around at first, but stick with it and do as many of those as it takes, or a night class or something.
If someone isn’t prepared to invest a week or two (in truth I spent a lot longer than that studying coding but I wan’t particularly time-efficient in my prior learning), then treat the llm as a learning resource, then good luck! I would guess the llm will be able to come up with any idea they can anyway soon enough!
That’s cool and I would say I mostly agree, I am also going to add a couple specific pointers that I consider practical: use ChatGPT on a desktop in a browser, use VS Code and extensions, keep ChatGPT instructions OFF the CLI so you don’t end up in a loop of running CLI codes and reporting back to your SupervisorGPT, make deals with ChatGPT in terms of complete code files and check every line, run midnight commander in a separate terminal and pay attention to permissions and ownership, force ChatGPT into lock down checklist mode and force it to go step by step, focus on the BIG picture with ChatGPT and don’t let it runoff to the next shiny object before you completed and tested everything that you wanted to do and hardened before you listen to the next bullshit suggestion prior to project completion. It’s not all bad and it does help you learn and punch above your weight class, but it can be downright infuriating and is by no means a turnkey solution: my two cents. Nobody going nowhere doing nothing.