Is it best to start with C and to then learn C++, or should one focus on C++ and pick up C "on the way," as it were?
As I've mentioned on many an occasion, I am a hardware design engineer by trade -- I am in no way a paid-up member of the software cognoscenti -- so when it comes to creating code, I'm largely reduced to making things up as I go along (see also Coding tips & tricks for LED ring lighting effects).
The thing is that I seem to be doing more and more coding these days for projects like my BADASS Display and my Cunning Chronograph. I can’t tell you how many times I've devoted hours to wrestling a recalcitrant program into submission, ended up with something that looks like the software equivalent of a dog's dinner, and then had a more experienced programmer glance over my grizzly effort and replace my convoluted constructions with a few elegant and succinct lines of code that have left me awestruck and gasping in delight.
"Enough already!" I cry. It's time for me to send the butler out to fetch my programming trousers and, while I'm waiting for him to track them down, for me to take a C and/or C++ course. If I had a choice, I'd prefer to attend a live presentation because I personally learn a lot faster when I have someone to question about stuff. However, there's also the time and hassle associated with leaving my office and attending such a course, so I guess we're reduced to online training.
Continue reading the complete version of this column on EE Times’ sister site, Embedded.com.