Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Things I Should Have Known at 20

inoveryourhead.net

Post reply on HN
Print view View original

81–90 of 163 posts

Re: Things I Should Have Known at 20

#81

Post by pg »

yelsgib wrote: post #72
pg wrote: post #67

Any book worth reading is worth reading slowly.

What's the slowest book you've read?

There are several different types of reading slowly.

Math is slow because you have to work things out as you read it.

Books written very long ago are slow because I read them like a detective, looking not just at what the author means to say, but also at what he's saying implicitly about how things were at the time.

Other books I read slowly because they're so good I don't want them to end. I used to have to make a conscious effort to make Patrick O'Brian novels last, and I stopped reading them at about number 12, to save the rest for later. (I worry though that I wouldn't like them so much now.)

Re: Things I Should Have Known at 20

#83

Post by shin_lao »

These lists always miss the point.

For example, the list is most likely right about sleep. However, if you're not sleeping enough you'll most likely say "It's ok man, it's under control".

Only when experiencing personally the damages of sleep deprivation you'll say "I should sleep more". Not because you read it on a list or your friend tells you.

As for six packs, yes, it's important, because it will insulate you from 95% of back pain. But who's going to do stomach crunches after reading such list?

Céline said it better than me: Experience is a lantern that lights only the carrier (L'expérience est une lanterne qui n'éclaire que celui qui la porte).

Re: Things I Should Have Known at 20

#84

Post by reneherse »

pg wrote: post #81
yelsgib wrote: post #72

Earlier quoted context omitted.

What's the slowest book you've read?

There are several different types of reading slowly. Math is slow because you have to work things out as you read it. Books written very long ago are slow because I read them like a detective, looking not just at what the author means to say, but also at what he's saying implicitly about how things were at the time. Other books I read slowly because they're so good I don't want them to end. I used to have to make a c…

If I could do it over, I'd read O'Brian's novels with several months to a year between each one (perhaps one every winter and summer solstice). There's really something to be said about savoring such an authentically detailed, nuanced, and intellectual universe.

As it is, I find my recollections of the Aubrey-Maturin adventures muddled and vague, since I burned through the first 20 at an addict's pace. Not recommended.

Re: Things I Should Have Known at 20

#87

Post by nazgulnarsil »

shin_lao wrote: post #83

These lists always miss the point. For example, the list is most likely right about sleep. However, if you're not sleeping enough you'll most likely say "It's ok man, it's under control". Only when experiencing personally the damages of sleep deprivation you'll say "I should sleep more". Not because you read it on a list or your friend tells you. As for six packs, yes, it's important, because it will insulate you fro…

crunches have nothing to do with a six pack. follow the link he provided.

Re: Things I Should Have Known at 20

#88

Post by jarek »

dfc wrote: post #11
raldi wrote: post #3

#21: Floating navbars are an abomination and make your site incredibly frustrating to read on a mobile device -- especially in landscape mode. At least put an X button on that thing.

#21(b) X buttons will not save a floating navbar with a "digital clock font."

Fun fact: the technical term is "seven-segment display character representations."

Re: Things I Should Have Known at 20

#89

Post by charlieflowers »

tensor wrote: post #68

Number two is flat out wrong. The majority of knowledge that you need to know is not bleeding edge and does not become outdated by the time a curriculum is formed. In fact, you can't even understand the bleeding edge research without first understanding what came before it. If by institutions, we are talking about universities, then they are one of the best places to access vast amounts of information and experts on…

See, I read it differently. I think his point there is about being passive, as in, "I don't have to go out and get knowledge, because it is my school's job to install knowledge into me." He didn't explicitly use the word "passive", but he mentions "faith", and relying on the institution "to educate you."

Right on the money -- even if you're in forced schooling, you need to go out and get knowledge.

Plus, think about all the programming curricula out there. How many are just mediocre Java certification programs? If you want really outstanding programming skills, you're going to have to go get them ... possibly using a university along the way (possibly not).

So his point # 2 resonated strongly with me.

Post reply on HN