Not this again.

Social media is where one shares one's social life (it's in the name!).

Granted there is often crossover between technical discussion forums and social media (I'm thinking of a motorbike forum I frequent), but to suggest the likes of HN is social media is rather silly. Isn't it.

It is, but it is way harder to self-promote yourself and derive other than intellectual satisfaction. It was not purposely built as a platform for advertising and branding like social networks.

You don't even have the dopamine hit of counting your content upvotes.

oh no it's just as vapid lol, basically equivalent to LinkedIn and if you think otherwise you're deluding yourself

I left it open-ended because it would somewhat depend on the junior developer's previous knowledge and their focus (do they have a CS degree? what topics do they want to go deep on in their career?)

But here are some titles:

* Kleppmann, Designing Data-Intensive Applications

* Nand2Tetris. Computers from first principles, often fills in a lot of gaps. Possibly preceded by Code: The Hidden Language of Computer Hardware and Software if they need even more grounding.

* SICP if I think they'd be ready for it

* Crafting Interpreters

* If they're working with Python I'd give them Fluent Python by Luciano Ramalho. For whatever other language(s) pick a book that allows them to go from intermediate to advanced in that language and really understand it inside out.

* Ousterhout, A Philosophy of Software Design

* Data and Reality

* The Staff Engineer’s Path by Tanya Reilly to demystify the upper IC track. Or The Manager's Path by Camille Fournier.

The question was how to learn, the answer (one answer) was read a few specific known-good books.

"new devs don't read" is a non-sequitur imo.

If they want the info, they will, or not. The info is there. Take it, don't take it, what do we care either way?

You’re not wrong. But this also sounds like a “not my problem”.

You can bring a horse to water, can’t make it drink…

This website has always somewhat been about trends. Before AI it was the metaverse. Crypto before that. NoSQL before that. Rails before that. Arguably there's always the undercurrent of the cult of personality of PG. ...

I'm sure I've missed some things, I've taken more than one hiatus.

Nuance usually cannot be well conveyed in a blog post. Someone is always selling something. When something exists long enough the bullshit behind it is eventually revealed. Reality is messy and there's always bullshit hiding somewhere.

It doesn't mean HN is useless. I use it as a bellweather to see what other people are putting their attention on. I don't pay attention to AI other than what's on here. I mostly follow my interests, which outside my dayjob, is currently concurrency. But I don't write about it.

Ultimately the place to become a better programmer is behind a keyboard learning what works, what doesn't, where it does, where it doesn't, and why or why not. It's difficult to convey all the nuance in every decision which means most people never actually do it. Any post is dripping with assumptions. In my mind nearly any decision could be justified and would be surprised to find a place that actually attempts to teach these.

Rather than consuming media you're probably better off putting it out there and letting people tell you all the ways you're "wrong" (because they love to do that). Somewhat paradoxically I don't really follow my own advice, but that's humans for you.

I mean, the whole point of my post was to say that books are more useful than anything else, and it would certainly better to have access to 10 good books and no hacker news at all than the reverse. But I do think there is value in keeping an eye on trends. They shape our industry; you may wish they didn’t, I wish they didn’t sometimes, but they do. Obviously good fundamentals are more important, but I think it’s doing a disservice to juniors if you tell them to ignore the “commentariat” completely.