Hacker News new | past | comments | ask | show | jobs | submit login

I'm sure there's an undercurrent reflective of a generalizable reality at work here.

Speed reading was desirable when lots of new exciting things were emerging in the late nineties. Note that simply "reading fast" didn't prevent the dot com bust.

Now, we have lots of new things, but they aren't exciting to us. In fact the prevailing wind is that of fatigue and overload. So now, going slow is perhaps perferable, whatever difference it might actually make.

In an economic sense, slow downs are viewed by go-getters as a reason to panic. "Oh no! I won't get my lunch at noon!" is how best to interpret that panic.

We actually have a lot of cool new things that magically appeared over the past thirty years, and as someone who has lived through it all, I feel like treadmill processes such as dependency hell and relentless up-versioning to bigger numbers robbed me of opportunities to deeply explore promising technologies.

But speed reading wasn't what was going to fix past problems, so why should slow reading fix current problems. It does seem to point to other facts though, if one chooses to look with those eyes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: