Earlier quoted context omitted.
I firmly believe that every programmer should be able to read and write C to some extent, and to learn it one must read K&R. So, yes, I agree that it is also one of the books that every programmer should read.
Curious why you think that? Every programmer? What does learning C provide that other programming languages (majority of which have some basis in C) don't teach you? Memory management (allocation, pointers, etc)? Pipes and buffers? They are present in other languages, and one could argue with memory management why 'every' programmer must learn those techniques even if they are never really applicable to them. I'm rea…
You can sit in front a CAD and FEM package all day - but if you don't appreciate how the things will actually be built you aren't going to be a really good engineer.