91 comments

[ 4.4 ms ] story [ 46.5 ms ] thread
(poorly).

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.

Making things poorly is a lot more interesting than not making them at all. And then you know who to ask when you need part of it done well.
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.
Harsh? Hardly.

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.

Except it looks like these students are expected to create at least basic items. There's likely a lab component.
We don't have to agree, but I think your comment is quite harsh.

I think it's harsh because you've judged the course's output and impact as "poor" without understanding its purpose and history, or engaging with prior students' final projects and their motivations.[1] Even if you had, you seem to hold some beliefs about the Maker Movement and maker culture[2] (and higher education in general) that are incompatible with the course's aims. That makes your judgment harsh and unqualified.

I may be missing what an alternative would look like. Surely we shouldn't try to make digital manufacturing less accessible. Students pursuing degrees in industrial design, mechanical engineering, media arts, and other fields should get hands-on, cross-disciplinary exposure, shouldn't they? I'm struggling to imagine how we could take a different approach and achieve comparable outcomes.

[1]: Start here: https://pub.cba.mit.edu/863.26/site/file/prior.html

[2]: See: https://en.wikipedia.org/wiki/Maker_culture

You have to begin somewhere.

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.

> The use of lowercase throughout doesn't inspire much confidence either.

I'm still surprised that people hang up on that in the big old 2026

And it's not a new thing either, like even writers in the typewriter age used it as a deliberate stylistic choice

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.

> This is an 18 credit class, requiring ∼18 hours per week for lecture, design, training, prototyping, and documentation.

It might be "just one course", but that's a lot of work!

In a recent video on Adams Savage's "Tested" Youtube channel, he put forth that in 10 years or so, desktop CNC machines will be pervasive (ob. discl., I work for a company which makes and sells such machines).

The software has certainly gotten much better --- one of my early projects had me drawing up vectors in Macromedia Freehand/MX, exporting them to make a font, and to import into a CAM program (MakerCAM, it was a Flash file, really), and coordinating the output from that with using the font in F-Engrave to V-carve a dial.

File and image at: https://community.carbide3d.com/t/locking-register-calipers-...

These days of course one could directly make it in any number of free or affordable programs.

(with computers)
Yeah! Interesting to see how this course presents technical solutions to unnamed (or maybe irrelevant) problems. The question, why would you even need to make these things, is at least hard to find.

Also not included are topics like "How to talk to customers" or "How to get customer feedback". Also not included, for example, "How to write a good story", "How to do crochet"

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.
Can it though? I automated one aspect of my day job and promptly ran into upload limits.

When I found and configured a local LLM to handle files, it took 6 min. 45 seconds to process two files --- I need to handle almost 5,000 in Q4.

I don't get it. Were you uploading files to a server to process them? Couldn't you run a local process to do it (which is, I assume, how the LLM got around the upload issues)?
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.
This website is a syllabus and summary of a course, not the course itself. The actual course involves hands-on time in a lab, building things.
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...

Amazing book! I received it as a gift before going into CompSci in mid-90s and I kept it and referred back to it long after I got rid of all my uni textbooks.

P.S. As sibling noted, the new price in that Amazon link is completely insane. Getting it used for a few $/€/£ is well worth it though

I LOVE this book. I worked through it in 2012 the summer before I went to college and learned so much that my intro CS class didn't really introduce any concepts I hadn't seen in one of the chapters.

I remember that the book uses a basic or python-like pseudo code and that their neural network implementation has a couple of very subtle bugs which prevent a direct translation to python. The surrounding explanation was correct, but the code wasn't, and so it (presumably unintentionally) forced me to really understand what was happening in order to get it working. I forget the bug, something like a dropped negative.

The information density of the book is just so incredible. Each chapter is like 6 pages long and somehow that's enough to go from zero to a working single-layer neural network, or boolean logic circuits, or error-correcting codes, or 50 other things. I remember it being almost addicting to work through.

Anyone have a recommendation like this for electronics? Breadth-first, short chapters, “know these all exist” rather than a deep textbook.
I have two:

- Practical Electronics for Inventors.

- Electronics All In One For Dummies.

Hope folks would chime in with more, I would love more recommendations here.

“The secret life of circuits” is neat in that regard

https://nostarch.com/secret-life-of-circuits#content

And there’s “Practical electronics for inventors”

https://www.mheducation.com/highered/mhp/product/practical-e...

But electronics is not that large of a field and understanding the mathematical models is kinda required to design stuff as components can be rather fragile and not have a lot of room to play around.

Check out YouTube, there is a growing culture creating high quality shorts of DIY electronics.

This guy is great because he doesn’t talk, he just makes stuff:

https://youtu.be/_QAEILW-gCY

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.
This is true, but it surprised me, and I think many others don't know it either.

After primary and secondary education – which were very broad – I had expected to learn in depth about something narrow when I went to university. A few years into a computer science programme, I was at first a little disappointed when I realised I had still only taken what could reasonably be called introductory courses in various sub-studies of computer science.

But as I got out into the workforce, I've noticed it's been useful to have tried a bit of everything and to have the vocabulary to talk about the basics in each of the sub-studies.

I did competitive programming, and was terrible at it. (I liked it though). A few years after I graduated I noticed that I had a “tendency” to map problems that we had down to known algorithms that are just not intuitive. Prefix sum comes up all the time, like probably once a week in my work, and the code is quicker and just as easy to write as the naive version.
Not just university, all education is balance between "broad and shallow" and "narrow and deep". Learning is a funnel for becoming the only person in the world knowing something while having all foundational knowledge underneath.
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 the kind of course that would be useful on any CS degree, because it places the specialism in a wider context.
> 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.
A gut feeling I've been having since the start of the LLM era is that horizontal knowledge (aka, knowing that stuff exists, can be done in certain way, being able to understand the details without knowing them intimately and being able to do it with a wide array of things) will start getting more and more important the further we go in, because if you know that stuff exist you can point an LLM at it or get it to go in a specific way that it wouldn't take otherwise. LLM have a very strong tendency to just go from point A to point B, and they're often limited to what you can prompt.

This is basically the opposite of the last 50+ years where vertical knowledge (being a savant in a certain very specific field) was seen as the most important thing to have in a super specialised world.

This of course is just my perception, which needless to say, may be wildly off

Isn’t the LLM already better at broadly knowing everything that exists than any human could ever hope to be?
LLMs currently are a great demonstration of the wide difference between knowing things and applying them in practice. Knowledge contained in LLMs is vast, but latent.

Humans have a practically infinite "context window" (active memory), we make associations and vaguely remember that thing we heard about that might be useful here, let's explore this thread ("you're absolutely right!"). Agents, being powerful as they are, don't do that, they pattern-match on the task and use the obvious solution, but don't activate their latent knowledge until you point them in the right direction.

The obvious solution might be the best one in 80% of cases or if you don't really care to get the best results (and it's absolutely fine!), but if you do care in your particular case, you have to babysit your agents and really understand if they're doing what you had in mind.

I’d say a SOTA LLM today has median depth of expertise over many, many disciplines, and slightly better than median expertise in a few key areas. “Jack of all trades, master of none”, springs to mind, but I’d say in the last 6 months it’s got above the median in some key areas.

The sweet spot is a true expert in a domain driving the LLM and keeping it honest, whether that be via agents/skills or reviewing work. In software dev, there’s huge tranches of work at junior/mid level where LLMs can just go, and anything where there is a clearly testable goal it can iterate on faster than a human expert, for example recent progresses in maths proofs.

But, I don’t think there’s an LLM out there that is an expert at everything. At least, not yet.

It's all about how much crap you can fit in your head without going crazy.

Either you fill it with vertical knowledge (which sucks because now AI wipes out a lot of specialists), or you fill it with horizontal knowledge.

Vertical knowledge is the deep silo of learning that comes from doing more advanced techniques to deal with increasingly difficult problems.

Horizontal knowledge is knowledge about process and workflow: where does the thing created by vertical knowledge fit on the bigger picture? What systems are integrated from left to right to keep you successful?

It may be that a successful developer is now a specialist in general technology.

Silos between specialists were always talked about being broken down but the truth is breaking down a silo means asking your specialists to do more work. You don't get to be a developer anymore, you must also take on operations for successful devops.

It may be that AI finally allows broken silos to be successful because AI removes a lot of friction that occurs when context switching between silos of specialists.

Then the question becomes: who is still creating quality with all these new tools?

Because at the end of the day, everyone wants maximum quality for the cheapest cost.

You may want T knowledge: deep vertical in one area and shallow horizontal in broad fields: Jack of all trades, master of one.
T knowledge has been valuable for a while but I think it's moving more generalized than that. Something like triangle or sawtooth knowledge. In my career, it's been rare to see deep specialists adequately utilized when hired. Almost every time I see them in a company, they're assuaging the company's neuroses about direction more than needing to synthesize new knowledge.
Even in the ancient ages of no AI long long time ago, the benefit of university education was not in learning specific methods and approaches for specific use but in learning to learn specific methods and approaches for a specific use, including learning what the specific use entails.
In my experience people are disappointed when their expectations are not met.

Maybe the course promises more than it delivers. It can still be very valuable.

> But those subject matter experts typically gain their expertise on the job,

For some things, mainly practical applied skills, that is the case, but for a whole class of others it is definitely not. Theoretical foundations are one such area. Whatever you do not learn in college you will never pick up in the job. I have may colleagues who were weak on complexity theory or database theory or things like security fundamentals or number theory or even probability theory and they have never managed to bridge that knowledge gap compared to their colleagues who were strong in those things right out of the gate. Make sure to deep dive at uni, that is likely the only chance you get. (No, watching a bunch of youtube clips does not cut it.)

I don't know if people still use the term, but long ago, this was referred to as a "survey course".
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?
It's pretty hard to generalize the necessary knowledge in a way that's useful and actually teachable. You pretty much have to go through the process yourself a few times, and even then, different factories have different capabilities and procedures, so unless you're making the exact same thing you made before, there's always a lot to learn when bringing up a production line.

In my experience the hardest parts are mechanical DFM and automating verification/QA. Choosing the right factory helps with that, and pretty much everything else

In my university we had a major manufacturing engineering. Even that would probably not cover all, and my exposure to it is a decade old, but it is still highly relevant to my career and would be a great extension to TFA.
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.
How does one best navigate this? Work their way through the recitations as a start?
I took and later TA'd this course. The weekly pages that guide lectures are only part of the story; the best way to see what is actually taught is to peruse the sites students make to document their projects. Past experience varies, but in most cases folks come in with minimal knowledge of e.g. electronics, CAD, machining, programming, etc., or are perhaps specialists in just one of the disciplines. HTM(A)A is about the delta between the start and end of the semester for each individual, and is both a life-changing course and a massive time commitment for all involved.
> the best way to see what is actually taught is to peruse the sites students make to document their projects

are those linked/listed somewhere?

On the site itself; people > students
Thanks! I had only checked project presentation + prior years and assumed people -> teaching personnel
[flagged]
[delayed]
That was a great read, I appreciate the author has tried to hide their snark and have an open mind where they can, though it of course leaks through.

It reminds me of the famous one about colors (which is a primer for computer people about the world of lawyers), "What Colour are your bits?":

https://ansuz.sooke.bc.ca/entry/23

I would love to read a more up to date one, this seems to be from ~1993, so 30 years ago. Has the situation changed, and if so in what direction?

Where can I find good video lectures on this topic?
I think what ever you need to learn you need more then just watching tutorials, you need to practice and practice and practice until it becomes part of your autopilot skills then after that you will be able to become a someone who really knows that, what ever it was and you can work and sell it to people not have time to learn that specific skill.