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.
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).