[commanderjroc]

Yes, we do need to improve the curriculum. But, how would we do it?

When I took Intro to Comp Sci, we didn't even go over design patterns and what makes good code. We did get instilled into us the principle of Single Responsibility.

As for trick questions, I got them in my Math Major and the comp sci classes I took. So, idk, if having trick questions is necessarily a deterrent, especially for a course preparing you for college.

[emodendroket]

Why would you go over design patterns in "intro to computer science"? That's more properly the domain of software engineering, isn't it?

[mhh__]

I obviously have no way of knowing but I would imagine a combination of: To keep the course "vocational", and relatively straightforward e.g. Working through CLRS wouldn't exactly be a walk in the park.

There is also a - annoying - confusion between programming and computer science, which is probably unavoidable but still gives the wrong idea as to what computer science actually is (Or isn't)

[commanderjroc]

I am not saying a full lecture or something.

But maybe a required reading? People are taking it as a survey course, an introduction, so it would be nice to give a little teaser or something of stuff that is to come later on.

[scarejunba]

Design Patterns in an Intro course to CS? No, and not required reading either. That's a "Practice of Software Engineering" thing.

It's too early.

[emodendroket]

That's another good point; someone barely learning to program is not at the point where they can understand or see the value in design patterns; at best you're going to create a situation where they blindly create design pattern code without understanding why they're doing it.