Remix.run Logo
▲ renehsz 6 hours ago

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.

▲tekacs 5 hours ago | parent | next [-]

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...

▲bre1010 an hour ago | parent | next [-]

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.

▲Witoso 28 minutes ago | parent | prev | next [-]

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

▲mfrw 7 minutes ago | parent [-]

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.

▲imeanwhatdoikno 4 hours ago | parent | prev | next [-]

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

▲grilledchickenw 4 hours ago | parent | prev [-]

181 GBP?! Now that is ridiculous.

▲EagnaIonat 3 hours ago | parent [-]

Looks like a typo or money laundering. Here is a cheaper one.

https://www.amazon.com/New-Turing-Omnibus-Sixty-Six-Excursio...

▲philipwhiuk 2 hours ago | parent [-]

Naive pricing bots is a more likely reason. See stuff like this https://www.youtube.com/watch?v=sseSi0k3Ecg

▲pmontra 5 hours ago | parent | prev | next [-]

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.

▲xbmcuser 5 hours ago | parent | prev | next [-]

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.

▲WillAdams a minute ago | parent | next [-]

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.

▲sureglymop 5 hours ago | parent | prev [-]

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.

▲magicalhippo 5 hours ago | parent | next [-]

> I think it's interesting because LLMs (at least if used in the terminal) quickly create their own scripts to do a certain task.

Let me just write a small Python script to decompile a section of this DLL so I can verify the constants for this function matches what the reference said.

With the images, I'll write a small Python script to compute the motion error using the Lucas-Kanade method[1].

Almost literally what Claude (Opus) casually has written as it chipped away at a couple of my problems.

[1]: https://en.wikipedia.org/wiki/Lucas%E2%80%93Kanade_method

▲xpct 5 hours ago | parent | prev [-]

It's also because the LLM training loop is too short-lived to give them feedback on how well repurposed their code can be. I imagine the labs are working on this to make it better, but it's fundamentally a much more expensive environment than training on few-script rollouts.

▲qalmakka 2 hours ago | parent | prev | next [-]

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

▲kapep 2 hours ago | parent | next [-]

I'm so sure about that. LLMs seem to have that tendency when people ask them to solve a certain issue, but they are just as good for providing an overview of a topic - or even better, because details don't matter as much.

▲alex_smart 2 hours ago | parent | prev [-]

Isn’t the LLM already better at broadly knowing everything that exists than any human could ever hope to be?

▲PaulRobinson 42 minutes ago | parent | next [-]

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.

▲qalmakka 2 hours ago | parent | prev | next [-]

yep, but it's not better at picking strong, long term decisions in my experience. The LLM most of the time is like a very knowledgeable employee that just does what it's told, and if the boss doesn't understand that you can do something, will often not ask for it to begin with.

for instance, if you use a shitty library X in a project, and you ask your frontier model "please change A -> B" the model will just do that, it will not tell you "well maybe you could also swap the whole thing with Y" because that's not its job - it's job it to change A to B.

▲skeptic_ai an hour ago | parent | next [-]

That’s why you just ask: do you think this is a good idea? Correct me if I’m wrong

▲wolttam an hour ago | parent | prev [-]

So all it takes is asking broad “hey LLM, is there any obviously better approach to what we’re doing?” Questions once in a while.

(I agree, they may not be good at making strong long-term decision still, but that may also be an issue of inadequate context a lot of the time)

▲roveo an hour ago | parent | prev [-]

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.

▲CobrastanJorji 4 hours ago | parent | prev | next [-]

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.

▲lordnacho 5 hours ago | parent | prev | next [-]

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.

▲kqr 4 hours ago | parent [-]

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.

▲maccard an hour ago | parent [-]

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.

▲Darmani 3 hours ago | parent | prev | next [-]

> 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.

▲teiferer 32 minutes ago | parent | prev | next [-]

> 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.)

▲dofm 4 hours ago | parent | prev | next [-]

Indeed, this is the kind of course that would be useful on any CS degree, because it places the specialism in a wider context.

▲rq1 2 hours ago | parent | prev | next [-]

Yes. An index is always useful.

▲baxtr an hour ago | parent | prev | next [-]

In my experience people are disappointed whenever their expectations are not met.

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

▲mihaaly 2 hours ago | parent | prev | next [-]

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.

▲LoganDark 5 hours ago | parent | prev [-]

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.

▲teraflop 4 hours ago | parent [-]

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.