big lol at the the title of this course. 1.5 hrs in length at least it's not 20 hrs. But I can make it even more concise:
1.) have some idea about the language/framework you want to ask it to write you code in. Chatgpt has scanned all of githubs' public (and probably private) repos and thus knows all kinds of sh*t up until 2021 when it's training data was cut off. I expect it to improve in this regard soon.
2.) each session you do is a discursion between you and your chatgpt friend. This means that you can show it examples you want it to use as a base, ask it to explain something better, or in simpler terms, etc. it will (try to) do it. It usually does it well enough for you to understand the topic better.
3.) it will give you an answer even if it cannot find a proper statistically probable answer to your question. This means that sometimes its answers will be bad, like real bad. It can eff' up a simple python code that just wants to calculate fibonacci series e.g. (=really simple). This also entails that you have to be somewhat knowledgeable in the topic (see #1) - if not the code will probably still run but will not do what you think it should. If you spot the mistakes and tell chatgpt it will try to fix it (by pulling an other example from its myriad of samples, one will fit sooner or later for sure), but just keep this in mind, do not rely on it without double or triple checking its code, not even simpler ones. You can and should use it as a base a skeleton of something, to start and you will build upon it by using more questions / google searches / stack overflow answers / own trial and errors.
There, I saved you watching 1.5 hrs of someone talking about his flutter adentures in chatgpt. How I hate that now even books started to appear regarding this. Only after like 2-3 months of public availability. For fucks' sake...
. God Bless 
![[CodeWithMosh] Spring Boot Mastering REST API Development](/data/resource_icons/11/11110.jpg?1745040366){kind=icon}
