11–20 of 63 posts
It reminds me of the blog post: "A Complete Understanding is No Longer Possible" [ http://prog21.dadgum.com/129.html ]
xv6 reflects this from an educational perspective: http://pdos.csail.mit.edu/6.828/2012/xv6.html
I am slightly disappointed by the list - for example C# threading is a book from 2003 and .NET has evolved a lot since then (Task, async, etc.). There are other, more recent books that represent current state of art in C#. Perhaps the reading list shouldnt state the year for which it is intended for?
A surprisingly low-quality, diluted, conformist list of mostly boring and outdated books. You can't expect much innovation to come from a team reading this. I scanned through the list 3 times looking for something of value, but nothing caught my eye. Disappointed by Intel.
A surprisingly low-quality, diluted, conformist list of mostly boring and outdated books. You can't expect much innovation to come from a team reading this. I scanned through the list 3 times looking for something of value, but nothing caught my eye. Disappointed by Intel.
What would you recommend instead?
/which is to say, books which most working in the field didn't read to get into the field, don't read during the actual job, and probably aren't going to read except maybe as a reference chapter here or there?
It turns out it's a pdf served at this address, along with another link to scribd in the brackets:
https://noggin.intel.com/sites/default/files/Intel-Recommend...
"I think the title should read [pdf] and [scribd]"
I am slightly disappointed by the list - for example C# threading is a book from 2003 and .NET has evolved a lot since then (Task, async, etc.). There are other, more recent books that represent current state of art in C#. Perhaps the reading list shouldnt state the year for which it is intended for?
The more current one is a free web resource http://www.albahari.com/threading/ . You maybe come across that already. I like it.