Thanks for the video, Mario. It generally reflects my experience with ChatGPT and Arduino coding. It's not always perfect perhaps, but still very helpful and impressive. It has a vast, if not unlimited, knowledge base. It can be particularly helpful as a learning tool with apparently unlimited patience. If I don't understand a function, I can keep asking questions about each element of the function until it's clear to me. You pointed out one aspect that I like about Chat's code is the detailed commenting. It also is generally good at creating good variable names - better than many online Arduino code tutorials (and yours, I'm afraid, as well). For example, in the shift register sketch, I find "dataPin", "latchPin" and "clockPin" more understandable for me and other people who my look at my code than "DS1_Pin", "STCP1_Pin" and "SHCP1_Pin".
Fully agree ... we ae sust humans. But this is a point noted that working on my next project maybe it is a good idea to step back and look at the naming. There is still time to adjust it before I start to hit record and edit. There is an idea for you. After compleating the code run it through chatGPT to ask to correct the naming. If you proide comments chatGPT would have a full understanding of the constatnt and variables and will, I am sure, propose consistant naming convention.
Thanks for the video, Mario. It generally reflects my experience with ChatGPT and Arduino coding. It's not always perfect perhaps, but still very helpful and impressive. It has a vast, if not unlimited, knowledge base. It can be particularly helpful as a learning tool with apparently unlimited patience. If I don't understand a function, I can keep asking questions about each element of the function until it's clear to me.
You pointed out one aspect that I like about Chat's code is the detailed commenting. It also is generally good at creating good variable names - better than many online Arduino code tutorials (and yours, I'm afraid, as well). For example, in the shift register sketch, I find "dataPin", "latchPin" and "clockPin" more understandable for me and other people who my look at my code than "DS1_Pin", "STCP1_Pin" and "SHCP1_Pin".
Fully agree ... we ae sust humans. But this is a point noted that working on my next project maybe it is a good idea to step back and look at the naming. There is still time to adjust it before I start to hit record and edit. There is an idea for you. After compleating the code run it through chatGPT to ask to correct the naming. If you proide comments chatGPT would have a full understanding of the constatnt and variables and will, I am sure, propose consistant naming convention.
Intro was fantastic! 😀
Thanks! 😁
Very interesting and instructive video, thanks Mario’s , !! Ciao Stefano
Glad you liked it!
maybe gpt can reverse scan the program from the microcontroller?
and write how the program works
maybe you can test it?
Have you tried asking ChatGPT to animate the fractals by zooming in?
No I have not
Thats insane!
mandebrot set koch curve i have no clue i think julia set like this and this XD