What should a developer know about networks and OS design?

Question

Computer networks

Something like Tanenbaum's books, only not 1000 but 100 pages.
It is unlikely that this will be a book, rather a series of articles?
Often this is bookmarked, or TODO lists, please share with someone at hand?
UPD: let's leave it necessary / not necessary, I myself worked without it, but now it took

Answer 1

I don't know anything about networks and wasps and feel great)

Answer 2

Yes, you don’t need all this to rivet sites. System programming is dead.

Answer 3

Yes, Wikipedia is enough for a general idea:
On networks
- OSI model
- TCP / IP stack
Further, after reading, you can walk around related articles and figure out how network addressing works, for example, etc. There is no need to learn headers for protocols. But how, let's say, a TCP connection is established is worth knowing, at least approximately. Well, the difference between TCP and UDP is not bad to realize.
As for operating systems: it all depends on what you want to know... It would be easier to read Tanembaum, the information would be perceived less fragmented, and boring chapters could be skipped and returned to them for clarification of some specific points.