K&R is simply a brilliant programming text. It might just be the right learning model for me, and maybe others can learn as well from other books, but I'd read a dozen C programming books (all much thicker than K&R, but much less valuable) before K&R, and it never really took until K&R.
I did not write much of interest using Amiga E, and that booklet was nowhere near as useful as K&R.
I think it's primary reason for popularity was that it was so easy to use the Amiga GUI elements and other special features of the Amiga OS and hardware. I always had a hard time making stuff work in C, but could build a UI in no time in E.
Machines that I had at the time were a Trash80 something or other mostly running basic and an AT&T machine running some for of Unix...oh yeah.
But, I fought my way through K&R, multiple c compilers, assembler, etc. to actually learn something on these machines.
An interesting comment from an earlier discussion mentioned "this code (in C) is much cleaner than any C++ I have seen!". The truth is, if you know C, have a good style and discipline, you pretty much can produce more readable/reusable code than your normal c++ person.
A decade ago I thought the book "C Programming : A Modern Approach" by K.N. King was a good starter text--I don't know if there's a better recommendation that's more recent.
In terms of after the fact reading, if you like the terse style of K&R you might pick up something but if you got bored I suspect that means you don't like the style. I suspect the time might be better spent reading some code instead.
By contrast, I did Perl work for years, and went to script something in it recently. Quickly decided it would be easier to learn Python from scratch than to get my Perl chops back.
Read it. Maybe couple of times (say only chapters 1-3) in the beginning. Understand the basic mechanism first rather than try out a program copied from somewhere else.
Start testing out simple things.
I'm lucky to not have fallen for all the blog posts/tutorials on openGL where they spit out a C file and say to compile and run it.
1. Buy K&R.
2. Read it. Maybe 2 or 3 times during the process of reading it, I would go write a program to try what I had just learned. This was was around 1980, so trying a program meant walking across campus to a terminal. I could either head to the computing center and use a public terminal, or to the high energy physics building (where I had just started a work-study job programming and it required C). The former would mean competing for a free terminal--and annoying people if I was spending my time at the terminal mostly reading K&R instead of typing. The later meant sitting at a terminal next to a noisy minicomputer in a cold room.
When I got to the end of K&R, I was a C programmer in theory.
3. Start doing real work, using K&R as a reference.
Very quickly theory became aligned with reality, and I was then a C programmer in practice.
Nowadays, most programming books I find assume that I'm sitting eagerly at a computer as I read, and that I want to stop every three paragraphs and type in some code and run it, and then the book discusses what that code did with the author writing under the assumption that I have the output of the code on my screen.
I like the K&R way better.