It seems some people aren't happy about the fact that this course only glosses over each topic, teaching students only superficial knowledge instead of doing a deeper dive on one or a few.
But let's not forget that an overview of what’s even possible is extremely valuable in its own right. When these students are later faced with a problem X, they'll remember that there was this thing called Y which might help. They won't know the details, but at least they'll know where to start looking.
This is especially important if you want to rise to managerial positions, and it might become more relevant now that AI agents are increasingly capable of implementing things: Solving problems is not all about how to do something, but also about knowing what can be done at all. Laypeople often have no idea what's possible, but engineers do, which lets them be creative with their tools.
All of this is not to downplay the value of true in-depth knowledge of a specific subject. But those subject matter experts typically gain their expertise on the job, or at a later stage in their academic life when they conduct proper research. An overview course like this one doesn't hurt even if many students will choose to specialize later on.
I fully agree and I add that this applies to every kind of job. I recently watched a plumber open and clean some pipes. I understood (at least at a superficial level) what he was doing and I've been able to complete the cleaning myself (he couldn't for a number of reasons that don't matter here.) Of course I've been clumsy and I took N times as long as he did but I finally got water again in my kitchen. Without watching him maybe I wouldn't have trusted myself to open some connections or I would have taken hours or days to reason about what was going on and probably do a lot of useless work.
Going back to CS and IT, I found myself talking many times along the years with good software developers coming from a totally different education path (graphics, philosophy, agricultural science, etc) and they had blind spots in areas that I had been exposed to at least a bit at university. Examples: SQL, one of them knew perfectly well how the ORM of the day worked (some JS one 12+ years ago) but not why; networking, one of them knew only to enter the SSID and password and everything else was magic.
This is the reason I think LLM are not being used to their full potential. A lot of busy office work can be automated if people knew they could get llm to make them scripts to do it. Where as currently a lot of people keep asking the llm to do things instead of asking the llm to build tools to do stuff.
This is why "T-shaped" knowledge is so valuable. You need depth in a given area. You should absolutely be an expert at the thing that you're most immediately doing most of the time. But you should also have a great breadth of knowledge, especially within your field, and the reason is so that you recognize situations where a particular solution to a problem you encounter may be relevant. That gives you the opportunity to learn more about that solution.
Indeed, this is what university actually IS. You won't be an expert in anything much at all when you graduate, but a broad survey will tell you how experts divide up the field, what concepts matter, and you will have a decent BS detector for your area of study.
> It seems some people aren't happy about the fact that this course only glosses over each topic, teaching students only superficial knowledge instead of doing a deeper dive on one or a few.
Then those people should be very happy to know that this course is the equivalent of multiple full time jobs. "I had 16 hours a week to spend on everything that's not this course" is something I've heard from multiple people who have taken it.
The "overview of what's possible" is instead instead provided by Intro to Making, the "baby" version of this course which I took.
Yes. An index is always useful.
Indeed, this is the kind of course that would be useful on any CS degree, because it places the specialism in a wider context.
I'm struggling to find prose. I just see lists of buzzwords. Am I reading it wrong? I struggle to see how this teaches superficial knowledge.
A book recommended to us when applying to Trinity College, Cambridge was 'The New Turing Omnibus' by A.K. Dewdney [1].
It's still to this day one of my favorite reads. By the time I read it, I knew about a lot of the possibilities within it already. But it does exactly this: it skims across the top of dozens of topics, and it makes you just aware enough of... all sorts of areas of CS.
If you're curious, you might dig deeper - at worst, you know these all exist.
[1]: https://www.amazon.com/New-Turing-Omnibus-Turning-Excursions...