Then when you come across a problem while building your product, you can say to yourself "Hey, this is what Mark Suster was talking about in that one blog post...how did he solve the problem?"
You've Probably Read Enough
11–20 of 78 posts
Re: You've Probably Read Enough
#12I've been "self-teaching" (mostly via O'Reilly books) since 2007 and I have completely changed my career. I grow as a programmer more and more every day, mostly thanks to reading.
Sure, I've read books like "Learn You A Haskell" without putting much into practice. But I feel I am much better off reading about new ideas even if I can't make every day use of them.
Re: You've Probably Read Enough
#13Re: You've Probably Read Enough
#14Re: You've Probably Read Enough
#15Re: You've Probably Read Enough
#16Though the time I spend here on HN is both enjoyable and educational, a few months ago I ran an interesting test. For each article I read, I wrote down a one line entry on a piece of paper noting the site and basic gist of the article. The next day, before I was "allowed" to read any more articles on HN, I sat down with the blank side of said piece of paper from yesterday, and wrote down the articles I remembered. I…
Re: You've Probably Read Enough
#17Re: You've Probably Read Enough
#18Though the time I spend here on HN is both enjoyable and educational, a few months ago I ran an interesting test. For each article I read, I wrote down a one line entry on a piece of paper noting the site and basic gist of the article. The next day, before I was "allowed" to read any more articles on HN, I sat down with the blank side of said piece of paper from yesterday, and wrote down the articles I remembered. I…
Re: You've Probably Read Enough
#19When I want to jump into a new interest, I usually spend a chunk of time at the beginning watching videos or grazing thru a manual. Even if I don't "get" everything yet -- knowing that Final Cut can do "X, Y, Z" and it's somewhere in the middle of the manual -- can be useful in removing some of the early frustration in the learning process.
I'll know something is possible, and vaguely know what the technique is called, and I will be able to incorporate that knowledge into my thinking.
Then whenever it is time to build stuff, there's a lot of very specific googling to lay down a strong foundation of a solution.
Re: You've Probably Read Enough
#20Though the time I spend here on HN is both enjoyable and educational, a few months ago I ran an interesting test. For each article I read, I wrote down a one line entry on a piece of paper noting the site and basic gist of the article. The next day, before I was "allowed" to read any more articles on HN, I sat down with the blank side of said piece of paper from yesterday, and wrote down the articles I remembered. I…
What keeps me coming back to HN is my ongoing curiosity of how technology is evolving. (And also a slight paranoia of another hacker publishing exactly one of my side projects before I do :) I enjoy being engaged with other like minded strangers. And I believe this place helps you better predict, even appreciate the direction of technology.
Just so long as you have balance and it doesn't keep you from actually getting things done. As for the article's point, I do agree. Doing something is immeasurably more beneficial for you than reading about it.