[cylentwolf]

I feel like most first intro classes in Computer Science is learn the coding language on your own. At first I was like why? Why don't they hold our hands while we do this. But since I have had some space to look back it really is a pretty good representation of our industry. You are going to need to learn new languages. So getting thrown in the deep end is a pretty good precursor for what work is going to look like.

[kenjackson]

This isn’t a bad idea, just not for the intro course. When I was an undergrad “programming language” was this course. You were given a brief introduction to brew languages and paradigms then expected to figure it out from there. But at this point you had a foundation of experience to build on.

[ghaff]

I don't totally disagree. On the other hand, based on the MOOC I took, had I been going in literally cold (as in college, new experiences, this is my chance to dive into CS and programming), I'd have been completely lost in a way that wouldn't have been the case in other engineering disciplines.

Now, I'm sure some would argue "tough." What are you doing at MIT then? And certainly, there are SO many opportunities these days to get some grounding in a way that may not be as readily possible with chemistry much less nuclear engineering for example. But it is something I think about now and then.

[somenameforme]

What makes you think this would not have been the case in other engineering disciplines?

I'm also a CS guy so I can't directly challenge this on the whole, but my experiences in some classes outside of this in other domains didn't feel like they were 'comfortably' paced at all. Without extensive out-of-class work I'd have been completely lost in no time. In fact one electrical engineering course I took was ironically considered a weed out course, for computer science, as it was required, and was probably the most brutal (and amazing) class I've ever taken in my life.

[ghaff]

Personal experience?

I had basically a machine shop course in mechanical engineering in college. OK, it was a bit more than that but I had no "shop" in high school.

Certainly nothing in high school anything that would have really prepared me for a civil engineering or or chemical engineering degree.

I had actually done a little bit of fiddling around with electronics (and maybe should have majored in that). But certainly college would have been a whole different level. (With a whole lot more math which was never my strong suit.)

So, yeah, these days I think there's a different baseline assumption for CS/programming than many other majors.

[griffzhowl]

Is the MOOC the same as the actual MIT course though? I went through one of the old Grimson Guttag Intro to CS courses on MIT OCW years ago, with zero programming background I found it a very gentle on-ramp with all the basics explained.

I think it was this one, unfortunately archived now. I don't know the new one

https://ocw.mit.edu/courses/6-00-introduction-to-computer-sc...

[ghaff]

No idea how similar it was to what's taught in the classroom. Of course you have access to TAs and other students IRL. And I have no doubt that assumptions about prior exposure and skills have changed over time.

I can only report that, had you dumped me into that content with those assignments, with no prior background I'd probably have been dropping that class.

The online version was more Grimson on the algorithms and Guttag (who wrote the Python book) on a bit of the programming. But the emphasis was more on the algorithms.