If SICP is so great

then where are the UML diagrams? Where is the the encapsulation and use cases? How is this code going to be reused? How will people know the class heirarchy? I've read this book back to front, cover to cover, and it smacks of poor software engineering. There was not a single UML valid diagram describing the plan before coding began. Indeed, there are very few diagrams at all. The book is mostly just text! Not only does it fail to use one of the standard languages for introductory texts, Java or Python, but it insists on using an implementation that the authors themselves made. They also refuse to actually teach the syntax, probably in a dishonest plan to drive students to purchase the specification for the language they wrote. It teaches students bad habits that have no doubt caused untold horrors to happen when these students actually get out into the real world and try to write real code. The book also keeps insisting that education should be fun, and assigns tiny programs that do nothing. No where in the book is there anything said about file IO, graphics, object orientation, web services, revision control, binary numbers, or even modularity. Shame on you Mr. Abelson and Mr. Sussman, you've ruined coding for a great number of people. These poor students, after a class taught with this horrible book, will stumble into their future jobs or classes without having a clue as to how code is really made.

You are confused. SICP is not a book about software engineering, SICP is about computer science or more specifically, the magic of spirits who live inside the computer. UML diagrams, encapsulation, classes, objects are not important parts of computer science so it's not taught in SICP. Scheme is used because it is easily taught.