I'm a student at MIT, and we would never see a course like this in the course catalog. I still haven't decided whether this is a good or bad thing, but I believe we need to find a middle ground: Do we take a theoretical approach or an implementation approach?
I've been unimpressed by MIT's ability to teach "coding." In fact, no classes actually teach you the art; you find out by experimentation in problem sets. However, as a result, you adopt a lot of bad habits that will make you less marketable to any company; you're code probably sucks.
I know this is a bit off-topic, but I applaud UNH for teaching such a class. It is important to teach the "tools" and the "technology" rather than the theory; at least to the point so you know what applications are out there to help.
1.00, 6.00, IAP Matlab, IAP Python, I'm sure there are more, but those were just the options I considered when I was starting out (I went with 6.00).
Sure the catalog is very coding light, but they assume you can figure it out on your own if you need it or can apply what you've been taught in 6.00/1.00 to many scenarios and learn from that basis.
These classes are not required in EECS, but required for the other engineering majors (you can, of course, substitute 6.01 if you are ambitious).
"...but they assume you can figure it out on your own if you need it or can apply what you've been taught in 6.00/1.00 to many scenarios and learn from that basis."
But that is the problem. Most/all MIT students teach themselves how to code, but that doesn't mean their code is clean and legible. Many times, the code quality is very bad because they develop bad habits in the process of teaching themselves. MIT needs an actual course about coding.... maybe a required HASS about how it should be considered an artwork.
I've been unimpressed by MIT's ability to teach "coding." In fact, no classes actually teach you the art; you find out by experimentation in problem sets. However, as a result, you adopt a lot of bad habits that will make you less marketable to any company; you're code probably sucks.
I know this is a bit off-topic, but I applaud UNH for teaching such a class. It is important to teach the "tools" and the "technology" rather than the theory; at least to the point so you know what applications are out there to help.