3 ms·

Exactly. Even a better reason to read curated content. You need to get awareness with what's going on in the tech community without sinking massive amounts of t

Exactly. Even a better reason to read curated content. You need to get awareness with what's going on in the tech community without sinking massive amounts of time. Do you really need to know about some lisp-variant someone implemented in 20 lines of Ruby.

kenbellows 13y ago
This implies that the average reader is diving into every article. If my job (or interests or sideproject or...) happens to be Ruby or Lisp related, perhaps that's a useful article. Personally, I rarely-if-ever use either, so I tend to skip those. And that's really the point. Sure, reading (or even skimming) every last article is a waste of time, but I don't think most of us do; we jump to the stuff that interests us. At least I do. And if I'm reading only curated lists, all I get is what interests someone else. There's some overlap, but I'll end up mentally filtering by title anyway, and there's a good chance I'll miss quite a bit that would be of real interest and value to me.
idProQuo 13y ago
HN doesn't have that much content, I never feel overwhelmed. The front-page turnover rate is really slow, to the point that I pretty quickly get my "fix" and then leave. Over the course of a day I might sink an hour into it, 2 if there's something interesting going on. However, I usually read maybe 3 articles per day at most. >Do you really need to know about some lisp-variant someone implemented in 20 lines of Ruby. I find the recent "tiny JS app" craze to be kind of cool. It's neat that a language can be so expressive that you can throw together something so complicated in under a kilobyte. I guess I don't need that kind of stuff, but it usually ends with me learning something new and wastes 5 minutes of my day at most.
raverbashing 13y ago
I agree. But the problem is quality of curation. Another problem, and maybe one can call it FOMO (Fear of Missing Out) is that sometimes the best knowledge is deep inside the comments. They may or may not be there but you have to filter all the babble.

kenbellows 13y ago

This implies that the average reader is diving into every article. If my job (or interests or sideproject or...) happens to be Ruby or Lisp related, perhaps that's a useful article. Personally, I rarely-if-ever use either, so I tend to skip those. And that's really the point. Sure, reading (or even skimming) every last article is a waste of time, but I don't think most of us do; we jump to the stuff that interests us. At least I do. And if I'm reading only curated lists, all I get is what interests someone else. There's some overlap, but I'll end up mentally filtering by title anyway, and there's a good chance I'll miss quite a bit that would be of real interest and value to me.

idProQuo 13y ago

HN doesn't have that much content, I never feel overwhelmed. The front-page turnover rate is really slow, to the point that I pretty quickly get my "fix" and then leave. Over the course of a day I might sink an hour into it, 2 if there's something interesting going on. However, I usually read maybe 3 articles per day at most. >Do you really need to know about some lisp-variant someone implemented in 20 lines of Ruby. I find the recent "tiny JS app" craze to be kind of cool. It's neat that a language can be so expressive that you can throw together something so complicated in under a kilobyte. I guess I don't need that kind of stuff, but it usually ends with me learning something new and wastes 5 minutes of my day at most.

raverbashing 13y ago

I agree. But the problem is quality of curation. Another problem, and maybe one can call it FOMO (Fear of Missing Out) is that sometimes the best knowledge is deep inside the comments. They may or may not be there but you have to filter all the babble.