It all depends what books you read -- say if you just read programming books and no theory, which tends to be drier and less interesting because the pseudo-code examples, if the book even has them, won't compile directly.
Which is what university does. Picks the books. Then tests to see if you really read and understood the material. Plus you can go to lectures if you like to have the prof explain what's in the textbook with notes and examples on the blackboard.
I have a degree but low tolerance for the academic environment (nothing wrong with it, just doesn't suit my personality).
That said, I think I've met a few self-taught programmers during my career that read the wrong books, or more correctly never read the right books (since wrong books are just an opportunity cost). Some are great technicians but will never be engineers. Some have massive blindspots in their knowledge.
Some of the textbooks I read in university I would have never read on my own. So university forced me to read them via degree requirements. Not knowing some of that stuff would have been a handicap at times.
So there's university education for you in a nutshell: forcing you to read books you didn't want to so you'll know a few things you otherwise wouldn't have. Totally worth the four years and big bucks.