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.
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.
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.
I think it's interesting because LLMs (at least if used in the terminal) quickly create their own scripts to do a certain task.
The issue is then, that those scripts are probably discarded after one use by the user, partly because the LLM doesn't make them generalized enough and focuses on solving the one task at that time. Partly because, when the issue next arises, it seems cheap to the user to just have the LLM do it again.
I think these models could be trained/fine tuned in a way to anticipate future issues or create general enough solutions but it would imply lowering their own use... so there might not be an incentive for that.
That's just one course, not a full load. The pace of that course is insane. It's not clear how much of what they throw at students is intended to be used. The syllabus is huge but the actual projects aren't that complicated. They make students make their own PC board, but that's not all that hard if you have all the right tools. Which they probably do.
It's trying to do it in the kitchen sink that's miserable.
I was around for the glory days of TechShop, took about thirteen of their classes, and they covered most of the techniques listed. But making actual stuff took much longer than the classes on machine operation.
I miss having access to CNC mills, laser cutters, and a water jet cutter. The computer-controlled stuff is easy to learn for a programmer. Welding requires endless practice and most people never get very good at it.
Just back from Shenzhen. Realizing there is a big gap in higher education for how to understand at-scale industrial processes. From prototype to product, there is a lot of know-how. Anyone familiar with instructions along these lines?
People dedicate entire careers to things like CAD — yet they somehow crammed it all into part of one lecture which seems to be little more than an enumeration of 50 different CAD tools.
The use of lowercase throughout doesn't inspire much confidence either.
Going breadth-first instead of depth-first is a pedagogical choice and a good motivator which was less possible 20 year ago. Now, more than ever, being a generalist means you can actually make something end-to-end, and making doesn't mean you need a professional machinist, industrial designer, or firmware engineer. Finally, this is a practical, not a lecture-based course. Most of what's learned is in the lab where you're expected to work and problem-solve.
If you look at the student portfolios from over the years, I'd say this course has done a lot of good taking this approach.
A bit harsh. I don’t think anyone is expecting they can waltz out of this course ready for a career in CAD. It is intended for students coming from a wide range of backgrounds including non-technical, so a whirlwind tour of the fundamentals of many different fab and design tools is perfect. Cross-disciplinary awareness and curiosity is rarely a bad thing.
This is like taking a "tour the crayon factory" episode of Mr. Rogers and making a college-level course out of it, but through the eyes of open source evangelist MIT-types.
In fact they would probably learn more from those old PBS shows meant for children, minus some right to repair propaganda thrown in for good measure.
Check out solidcraft. I spent the weekend with multiple codex sessions watching it build 3d prints for me. What's nice is I can use the tool with it to make my own changes like fusion 360 and so it's like a built in helper. Pretty slick
I did it with Codex once. The model didn't even bother to chamfer the edges but if you have no experience building physical stuff it still could come as a miracle.
To be fair - they seem to focus on setting goals for learning, so that the student would have to learn it all on their own. It's like vibe coding. Teachers give prompts to students and students deliver on the learning work.
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.
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...
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.
The issue is then, that those scripts are probably discarded after one use by the user, partly because the LLM doesn't make them generalized enough and focuses on solving the one task at that time. Partly because, when the issue next arises, it seems cheap to the user to just have the LLM do it again.
I think these models could be trained/fine tuned in a way to anticipate future issues or create general enough solutions but it would imply lowering their own use... so there might not be an incentive for that.
I was around for the glory days of TechShop, took about thirteen of their classes, and they covered most of the techniques listed. But making actual stuff took much longer than the classes on machine operation.
I miss having access to CNC mills, laser cutters, and a water jet cutter. The computer-controlled stuff is easy to learn for a programmer. Welding requires endless practice and most people never get very good at it.
https://news.ycombinator.com/item?id=44775830
Title: 2.75 FUNdaMENTALs of Design
https://www.youtube.com/watch?v=wgMq7yha9wU&list=PLksE8LDXGX...
Gershenfeld is a low key genius, and this curriculum has been taught every year well before AI.
haters gonna hate.
People dedicate entire careers to things like CAD — yet they somehow crammed it all into part of one lecture which seems to be little more than an enumeration of 50 different CAD tools.
The use of lowercase throughout doesn't inspire much confidence either.
Going breadth-first instead of depth-first is a pedagogical choice and a good motivator which was less possible 20 year ago. Now, more than ever, being a generalist means you can actually make something end-to-end, and making doesn't mean you need a professional machinist, industrial designer, or firmware engineer. Finally, this is a practical, not a lecture-based course. Most of what's learned is in the lab where you're expected to work and problem-solve.
If you look at the student portfolios from over the years, I'd say this course has done a lot of good taking this approach.
This is like taking a "tour the crayon factory" episode of Mr. Rogers and making a college-level course out of it, but through the eyes of open source evangelist MIT-types.
In fact they would probably learn more from those old PBS shows meant for children, minus some right to repair propaganda thrown in for good measure.