I'm development lead on my startup and just being aware of new tech, other startups, problems with frameworks, algorithms,... all help me be better informed for my job.
I'm development lead on my startup and just being aware of new tech, other startups, problems with frameworks, algorithms,... all help me be better informed for my job.
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.
>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.
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.
So yeah, how do we find out about all these stuff otherwise?
Curated content still gives you what you want, but with less work. Additionally, you're reading will be consolidated (in theory) into a larger block of time on a less frequent basis, freeing up more time throughout your week.