What stops your Arduino project?

From some of the discussions on the Arduino forum that crop up, I think videos or other info teaching users how to structure their code design could help. Sometimes beginners use a hundred lines of code when they could have collapsed it all into a 5-line 'for' loop for instance, or creating functions. Also, how to troubleshoot code - from blinking an LED or two for status, to using a multimeter or 'scope to check activity on pin(s), and using the console for debug print statements.

Also, how to test algorithms using a PC, Pi etc., before placing that code into the Arduino IDE. Using #ifdefs, etc.

I think a lot of people could concentrate more on the end application if they can get through the coding basics, before working with the Arduino libraries.

Also, some example code structures/patterns, for instance how to accept user input, maybe debounce it, and also do some processing in the background, how that could be implemented with timers or interrupts or any other service provided by the Arduino system to achieve such real-time tasks.

From some of the discussions on the Arduino forum that crop up, I think videos or other info teaching users how to structure their code design could help. Sometimes beginners use a hundred lines of code when they could have collapsed it all into a 5-line 'for' loop for instance, or creating functions. Also, how to troubleshoot code - from blinking an LED or two for status, to using a multimeter or 'scope to check activity on pin(s), and using the console for debug print statements.

Also, how to test algorithms using a PC, Pi etc., before placing that code into the Arduino IDE. Using #ifdefs, etc.

I think a lot of people could concentrate more on the end application if they can get through the coding basics, before working with the Arduino libraries.

Also, some example code structures/patterns, for instance how to accept user input, maybe debounce it, and also do some processing in the background, how that could be implemented with timers or interrupts or any other service provided by the Arduino system to achieve such real-time tasks.

"...Sometimes beginners use a hundred lines of code when they could have collapsed it all into a 5-line 'for' loop for instance, or creating functions..."

I think that sometimes happens because beginners don't realise how quickly things tend to grow out of control. Also because they are often working from small snippets of example code from beginners guides and chaining it together into something a bit larger without always considering the overall program design. After several hours and once they get to a few 1,000 lines of something that appears to be working, it can be daunting to hack it all apart to try and tidy it up, with a good chance of breaking it in the process.

For a beginner it can also often be difficult to firstly identify well-written code and then secondly to understand it.

I think there is room for a more structured course based around Arduino as the platform. The official starter kit is great for getting people interested in Arduino but there ideally needs to be something that follows on from that which helps develop better programming and interfacing skills.

If anyone has seen David Beazley's Python Programming Language Live Lesson course, then a lot can be learned from that style. He starts with the basic way of doing stuff but then is always revealing a better way, whilst talking you through as to why it is better each time. He also adds context by using useful everyday examples where you can use these techniques. 

Perhaps slightly controversial, but another course worth mentioning is Atmel's Getting Started with AVR by Glen Nilsen. It uses the Atmel ATmega 328P Xplained/Atmel Studio instead of the Arduino Uno/IDE but it leverages the hardware side of the ATmega 328P. Most of the main program loop is empty as the on-chip peripherals have been set up to do all the heavy lifting in the initial setup routine.