News for hackers. Stuff that matters.
Re:How to Make Almost Anything by renehsz on Monday November 16, 2026 @02:12AM (#50514910)
[delayed]
Re:How to Make Almost Anything by pmontra on Monday November 16, 2026 @02:37AM (#50515053)
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.

Re:How to Make Almost Anything by xbmcuser on Monday November 16, 2026 @02:42AM (#50515083)
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.
Re:How to Make Almost Anything by sureglymop on Monday November 16, 2026 @02:47AM (#50515105)
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.

Re:How to Make Almost Anything by xpct on Monday November 16, 2026 @03:25AM (#50515306)
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.
Re:How to Make Almost Anything by magicalhippo on Monday November 16, 2026 @03:27AM (#50515315)
> 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

Re:How to Make Almost Anything by WillAdams on Monday November 16, 2026 @08:01AM (#50517157)
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.

Re:How to Make Almost Anything by wtetzner on Monday November 16, 2026 @09:05AM (#50517724)
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)?
Re:How to Make Almost Anything by WillAdams on Monday November 16, 2026 @10:41AM (#50518794)
When uploading to a server (Microsoft's via Copilot) I ran into upload limits, ~80--100 files per day last I was able to try.

When running locally, it took the LLM 405 seconds to process two files.

Re:How to Make Almost Anything by kaashif on Monday November 16, 2026 @10:49AM (#50518910)
To answer the question, we need to know something, anything about the tasks you automated.

If the task is filling in tax forms from a spreadsheet then yeah, you can ask an LLM to write a script for that.

If the task is proving thousands of math theorems or the task is translating specs into working software, then yeah, I guess you do need an LLM.

Re:How to Make Almost Anything by WillAdams on Monday November 16, 2026 @12:46PM (#50520440)
The task is to rename scanned files of a check overlaid on one or more invoices using the amount of the check and its date and a couple of the numbers from one fo the invoices using the prompt:

For each file which was uploaded create a move command in a .bat batch file which will rename the matching file using the current filename of the uploaded file and use the amount, and date of the check, the Invoice ID, PWS ID, and COMPANYNAME in all UPPERCASE run together with no spaces from the PWS population line using a filename like to:

    $<check amount>_<Account ID>_<date of check as YYYY-MM-DD>_<Invoice ID>_<PWS ID>_<COMPANYNAME>.pdf
Do not explain how this is to be done, open each file, examine it, and create the appropriate command, returning the contents of a .bat file with each command on a separate line which may be run on the files in that directory to rename the files from the name as uploaded to the generated filename with the command on its own line.
Re:How to Make Almost Anything by IX-103 on Monday November 16, 2026 @12:11PM (#50519974)
[delayed]
Re:How to Make Almost Anything by vjvjvjvjghv on Monday November 16, 2026 @11:35AM (#50519523)
[delayed]
Re:How to Make Almost Anything by LoganDark on Monday November 16, 2026 @02:48AM (#50515110)
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.
Re:How to Make Almost Anything by teraflop on Monday November 16, 2026 @03:45AM (#50515427)
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.
Re:How to Make Almost Anything by tekacs on Monday November 16, 2026 @02:49AM (#50515119)
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...

Re:How to Make Almost Anything by grilledchickenw on Monday November 16, 2026 @04:22AM (#50515630)
181 GBP?! Now that is ridiculous.
Re:How to Make Almost Anything by EagnaIonat on Monday November 16, 2026 @05:24AM (#50516019)
Looks like a typo or money laundering. Here is a cheaper one.

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

Re:How to Make Almost Anything by philipwhiuk on Monday November 16, 2026 @06:15AM (#50516314)
Naive pricing bots is a more likely reason. See stuff like this https://www.youtube.com/watch?v=sseSi0k3Ecg
Re:How to Make Almost Anything by imeanwhatdoikno on Monday November 16, 2026 @04:31AM (#50515692)
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

Re:How to Make Almost Anything by bre1010 on Monday November 16, 2026 @07:10AM (#50516723)
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.

Re:How to Make Almost Anything by Witoso on Monday November 16, 2026 @07:35AM (#50516939)
Anyone have a recommendation like this for electronics? Breadth-first, short chapters, “know these all exist” rather than a deep textbook.
Re:How to Make Almost Anything by mfrw on Monday November 16, 2026 @07:56AM (#50517109)
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.

Re:How to Make Almost Anything by skydhash on Monday November 16, 2026 @08:06AM (#50517203)
“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.

Re:How to Make Almost Anything by yepyoukno on Monday November 16, 2026 @09:28AM (#50517958)
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

Re:How to Make Almost Anything by javiramos on Monday November 16, 2026 @09:18AM (#50517843)
A little dated but fantastic book: https://artofelectronics.net/prehistory/
Re:How to Make Almost Anything by sstanie on Monday November 16, 2026 @11:41AM (#50519603)
The youtube series from Practical Electronics https://practicingelectronics.com/practical-electronics-cour... (https://www.youtube.com/watch?v=zDnhcsxwNAo&list=PLNx89373hp...) is maybe the best I've seen online. It assumes you have seen a basic circuits course, but that is much easier to fill in on the fly.

I got through most of Art of Electronics, and then found this, and wished I had just gone through this series the whole time. AoE is much more of a reference than a good learning-from-scratch resource.

Re:How to Make Almost Anything by georgecmu on Monday November 16, 2026 @11:59AM (#50519814)
For those who are curious: you can read it for free (but not download) on archive.org (requires an account):

https://archive.org/details/newturingomnibus0000dewd/page/n2...

Re:How to Make Almost Anything by warkdarrior on Monday November 16, 2026 @12:54PM (#50520558)
Re:How to Make Almost Anything by gavin_gee on Monday November 16, 2026 @12:25PM (#50520153)
brilliant primers for asking good questions to AI
Re:How to Make Almost Anything by lordnacho on Monday November 16, 2026 @02:52AM (#50515135)
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.
Re:How to Make Almost Anything by kqr on Monday November 16, 2026 @04:20AM (#50515625)
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.

Re:How to Make Almost Anything by maccard on Monday November 16, 2026 @07:07AM (#50516694)
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.
Re:How to Make Almost Anything by ivanjermakov on Monday November 16, 2026 @09:22AM (#50517884)
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.
Re:How to Make Almost Anything by CobrastanJorji on Monday November 16, 2026 @03:54AM (#50515484)
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.
Re:How to Make Almost Anything by dofm on Monday November 16, 2026 @04:19AM (#50515614)
Indeed, this is the kind of course that would be useful on any CS degree, because it places the specialism in a wider context.
Re:How to Make Almost Anything by Darmani on Monday November 16, 2026 @04:53AM (#50515830)
[delayed]
Re:How to Make Almost Anything by rq1 on Monday November 16, 2026 @05:45AM (#50516143)
Yes. An index is always useful.
Re:How to Make Almost Anything by qalmakka on Monday November 16, 2026 @06:11AM (#50516284)
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

Re:How to Make Almost Anything by kapep on Monday November 16, 2026 @06:17AM (#50516321)
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.
Re:How to Make Almost Anything by alex_smart on Monday November 16, 2026 @06:24AM (#50516366)
Isn’t the LLM already better at broadly knowing everything that exists than any human could ever hope to be?
Re:How to Make Almost Anything by qalmakka on Monday November 16, 2026 @06:28AM (#50516384)
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.

Re:How to Make Almost Anything by skeptic_ai on Monday November 16, 2026 @06:49AM (#50516550)
That’s why you just ask: do you think this is a good idea? Correct me if I’m wrong
Re:How to Make Almost Anything by wolttam on Monday November 16, 2026 @06:51AM (#50516573)
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)

Re:How to Make Almost Anything by roveo on Monday November 16, 2026 @06:40AM (#50516481)
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.

Re:How to Make Almost Anything by PaulRobinson on Monday November 16, 2026 @07:21AM (#50516829)
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.

Re:How to Make Almost Anything by epiccoleman on Monday November 16, 2026 @11:53AM (#50519737)
It's funny because - yes, it does seem like it should be that way. But I feel like a huge amount of the value I've gotten from LLMs has been specifically because I'm a generalist type and I can sort of quickly cut through the space of possibilities.

Just knowing what's possible, having been exposed to a bunch of ideas, libraries, tools, and, yes, reading too much Hacker News - seems like it's allowed me to ask good questions, propose interesting experiments, and drive my own knowledge forward faster with LLMs.

I don't know that it's a particularly unique skill, but from personal experience there seems to be a spectrum of ... creativity? Freedom of thought / expression? And people who are kinda stuck in their ways seem to get less out of LLMs than people who have some idea of what they want and even some direction in mind, but just need the details made frictionless.

I think I'm not doing the best job expressing what I'm on about, so here's an example - I have a little livecoding app[0], which I developed (vibe-coded) for a conference talk I gave in October[1]. It's been a lot of fun to play with and has formed a good surface for lots of different experiments that never made it into the codebase - just throwaway ideas, etc.

So when all the hype about Jev was going a month or two ago, my experiment was "can Jev sit in on the jam?" And what I did was hook it up to the app - not to the "musical context" information that other agents (agents in the Elixir sense, not really the 'llm agent' sense) in that app receive, but rather to the raw signal info that was coming out of the master audio node. And then Jev made a prediction about what note to play, and then that note was sent through WebMIDI to a VST on my machine so that Jev was almost like an outside "guy" soloing over the app's music.

(Jev was a pretty boring soloist, because playing the "most likely" note every time is not especially exciting, but that's beside the point here).

Maybe Claude / Codex could have come up with that idea without me - surely the models know about all of those different tools / options already. But I'd bet that if I hadn't known what to ask for, I'd have gotten something less fun.

So, idk. Does that mark me out as some kind of special generalist who will forever be ahead of the permanent underclass because he reads too much HN? Probably not. But it's at least a useful disposition in the LLM era.

[0]: https://github.com/epiccoleman/tripulator/ (AGPL, go nuts!)

[1]: https://epiccoleman.com/tripulator

Re:How to Make Almost Anything by poopingatwork on Monday November 16, 2026 @09:17AM (#50517836)
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.

Re:How to Make Almost Anything by erwincoumans on Monday November 16, 2026 @09:43AM (#50518116)
You may want T knowledge: deep vertical in one area and shallow horizontal in broad fields.
Re:How to Make Almost Anything by oscillonoscope on Monday November 16, 2026 @10:06AM (#50518374)
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.
Re:How to Make Almost Anything by gavin_gee on Monday November 16, 2026 @12:26PM (#50520168)
yeah I think T knowledge is dead. its all horizontal now
Re:How to Make Almost Anything by mihaaly on Monday November 16, 2026 @06:30AM (#50516396)
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.
Re:How to Make Almost Anything by baxtr on Monday November 16, 2026 @06:51AM (#50516572)
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.

Re:How to Make Almost Anything by teiferer on Monday November 16, 2026 @07:31AM (#50516912)
> 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.)

Re:How to Make Almost Anything by santoshalper on Monday November 16, 2026 @08:08AM (#50517227)
I don't know if people still use the term, but long ago, this was referred to as a "survey course".
Re:How to Make Almost Anything by laidoffamazon on Monday November 16, 2026 @12:38PM (#50520318)
The reason why it’s superficial is most of the students are already experts at at least one of these topics by the time they take the class, usually even before they attend undergrad at all.