I've used Basic since I was about 16 - about 40 years. Loved the observation in the main article:
With "GOTO line-number" being one of the principal ways of flowing logic....The result was dreadful spaghetti code and, for many novices, a completely invalid idea of how programming was done. This aspect was succinctly captured, not without some hyperbole, by Edgar Dijkstra's famous observation:
"It is practically impossible to teach good programming to students that have had a prior exposure to BASIC: as potential programmers they are mentally mutilated beyond hope of regeneration."
I certainly found that when I tried another language - I forget which - later. And the later incarnations of BASIC have much better structures and I taught myself to avoid GOTOs. I'm still using it in the PICAXEs, and still loving it, though I do see its limitations for more professional stuff than I do. And much as I find it easy, I wouldn't recommend it to any new students - yougsters seem to pick up C in the same time it took me to learn BASIC, and that'll be much more use to them.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.