I feel like this reveals some sampling error in the OP rant. When you see something negative get made that makes you think "nobody cares", you're not seeing the people who did care and left.
I had one of these as a kid, got it as a christmas present because my dad did the give one get one thing. It was a lot of fun and I remember messing around with Python on there because it came with an interpreter, I think.
I watched Lucifer Rising when I was a teenager because some of my Tumblr friends recommended it to me. While I can't say I took much away from it other than it looked cool, I'll always have some fond memories of that time associated with it.
2. Do you have any sort of guide or principles for note-taking? I'm always debating whether or not it's worth taking notes, and when I do take notes I'm debating what the best way to do it is. (Hierarchal/bulleted information like in your post, or summarizing things in paragraphs, or what) A lot of times it's unclear to me what information is worth writing and it frustrates me.
I think you if you have a particular goal with using the computer it gets easier to avoid hoarding. I'm trying to get better at writing code that's easy to read and change, which is admittedly too vague but it can still help me be real with myself and close tabs that don't have anything to do with it.
So that first one is about solving an advent of code problem cleverly. That second one makes some nice points about how code doesn't necessarily capture your intent or the reasons you wrote what you did. So if I had both of those open in my browser or in some queue for unread links, and I wanted to cut down, I'd delete the first one.
I also find it helpful to ask if a link has any information that isn't already covered by some other resource in more depth. So if my goal was to learn more about compilers I might be tempted to save the blog post OP links to about writing a brainfuck compiler in Go with LLVM but there's already resources like Crafting Interpreters out there, so I'd probably only give that blog post a skim and not bother saving the link. (But if it was my goal to specifically write a brainfuck compiler, or write a compiler in Go, or write a compiler that uses LLVM, or some combination, I'd be more likely to save that particular post.)