|
|
|
|
|
|
by eatonphil
1261 days ago
|
|
|
Reading books is great! And curating a list is useful and fun. But you have to be pretty careful when you say things are a "must" since that's... pretty hard to prove (and can just make people feel bad). And the proof has already been pointed out as not true in this thread. Unless we all want to start evaluating eachother's programming ability virtually. Again, lists and reading is great! And it's probably better to (try to) read any of these books than not. But for the folks who try the books and can't get through them (like me and SICP), I'd say don't worry about it. I have my own [0] list of books I think devs should read but I just try not to say "must read". [0] https://notes.eatonphil.com/books-developers-should-read.htm... |
|
|
I can not stand the dogmas: You "must" read this, you "have" to use this IDE/text editor, you will perish a slow painful death if you program in language X and not language Y.
Read what you want, use what you want, please share with me what you like and don't like but please do not tell me what I must do and I must use.