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

When I run across a problem like the above, surely it's worth a few hours of my time, at that time. If it becomes a habitual problem, I no longer have to spend a few hours of my time.

I think I did - 8 years ago. The problem isn't that I'm lazy, it's that if I have no reason to use something for a long enough period of time, I tend to forget it. Maybe you remember everything you read forever?

There's already a plethora of information that is worth a few hours of my time - the problem is there isn't enough hours in the day. I don't want to spend them on things I'll not use and soon forget.




I certainly don't remember things forever. But I generally find that the hard concepts stick around vestigially. Having read this (admittedly weighty) paper once, you'll find that going back in 4 years to check something isn't nearly so bad.

Really, read it. It's good for you. Like vegetables.


No. I already have a ton of other vegetables on my plate. Lambda calculus, compiler architecture, Haskell arrows.




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

Search: