3 ms·
I first started coding professionally in the early 90’s, just as “the web” started to take off. I found myself surrounded by people who talked about the networ
by commandlinefan 8y ago
I first started coding professionally in the early 90’s, just as “the web” started to take off. I found myself surrounded by people who talked about the network stack all the time; I put together that there was an important concept called “TCP/IP” in there. So I did what I thought was the most logical thing: I picked up a copy of Richard Steven’s “TCP/IP Illustrated” and read it cover to cover. Then a funny thing happened - I found out I actually knew WAY more about the network stack than all the people around me who were blathering about it non-stop as though they were experts (which I didn’t and still don’t consider myself). That experience has made me take other’s claims of expertise with a grain of salt.
- TeMPOraL 8y agoI think a corollary here is that reading a technical book cover to cover isn't really that hard. Personally I'm trying to make it my default approach for learning things - books over articles (where that makes sense; books on continuously changing software are a waste of paper).