News for hackers. Stuff that matters.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by ucyo on Saturday November 14, 2026 @02:31AM (#50494876)
Do you have recommendations for this? Ideally books
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by filipn on Saturday November 14, 2026 @03:14AM (#50495119)
If people knew what is worthwhile building, they wouldn't write a book about it. It's like writing a book on how to make money in the stock market.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by phtrivier on Saturday November 14, 2026 @05:38AM (#50495878)
Arguably, a lot of books are written about that, by two different kind of people who did made money on the market : those that made a lucky bet, beat the market, and are trying to explain how to become a young billionaire yourself (I don't have exemple in mind, because those are not worth much any way - see below); and those that just invested cautiously enough to _follow_ the market, not make anything dumb, and make enough money to be an old millionaire yourself (Charlie Munger, Mr Money mustache, etc...)

The former are fun but irreproducible ; the latter are boring (index funds, sobriety, compound interest, don't be stupid, and some luck to avoid the bad timing of the crashes) unless the author adds some snark (again, Munger)

Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by jodrellblank on Saturday November 14, 2026 @05:49AM (#50495932)
The latter are the former just on a longer timescale. You say "some luck to avoid bad timing" but ask yourself how many people in the 1950s - 2020s were doing what Buffet and Munger were doing, namely reading a lot of company balance sheets and announcements, trying to stick to decent and well-run companies with good business models, buying when cheap opportunities present, and waiting a lot.

I expect it will be more than 2 people trying that, and almost all of them didn't become multi-billionaires.

Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by phtrivier on Saturday November 14, 2026 @06:48AM (#50496254)
What I meant is that, if you you don't need to withdraw a lot from your savings exactly at the time of a crash, than "just following the market" works. And, crashes happen regularly, but scarcely enough that you may very well retire in between them.

So it's the difference between "depending on things being average" and "depending on things being exceptional".

Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by neomantra on Saturday November 14, 2026 @04:04AM (#50495350)
It is quite dated (1994), but just this week I was feeling very thankful to the authors of Taligent's Guide to Designing Programs [1], a book I read and lived. It comes from an era when software architect and programmer were different jobs (things seemed to change soon after?), which parallels modern LLM use. The C++ version there is quite old, but the concepts are timeless.

[1] https://root.cern.ch/TaligentDocs/TaligentOnline/DocumentRoo...

Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by fulafel on Saturday November 14, 2026 @05:37AM (#50495873)
For those unfamiliar, Taligent was (among other things) a very well funded C++ app platform that never shipped, and its failures have been much analysed.
Re:Jonathan Blow – If AI Solved Coding, Why Is My Software S... by neomantra on Saturday November 14, 2026 @07:29AM (#50496503)
Yeah, it was weird that I was reading so much about designing software in a system I could never touch. It might be part of why OSS and access to computing is important to me; we had to buy our C++ compilers then.

It was my first years of being a "software engineer", versus the solo hacker kid who liked making art of over phone lines. So I devoured books which would teach me how to make software with other people and for other people.

Books like the "BeOS Filesystem book" (Practice File System Design) was another classic from the era [1]. It was like today's LLM white papers, learning how a company did something unique, except companies seldom published them because it was a time of IP hoarding.

Unfortunately the books that eventually became the most practical were those by Sutters and Meyers; compendiums on the warts and jewels of C++ that you needed to know to be good at programming in it. Such nitty gritty, much of which was eventually fixed by language design. I really don't miss having to know all that, freeing my mind to consider architecture, design, and delivery.

[1] https://www.nobius.org/dbg/practical-file-system-design.pdf