Structure and Intepretation of Computer Programs vs The Design of Everyday Things

This isn't a book you'll glean direct practical tidbits out of, an introduction to not only functional programming but how to think in a paradigm outside the usual way C*/Python/Ruby/Java/etc... are coded.

Even if you wind up never working in Scheme or any other primarily functional language, the tactics and thought processes you'll learn here will apply to any currently-evolving language to a greater or lesser degree. You'll be able to map your thought process into the paradigm that works best for your current situation and not just be forced into a limited set of idioms that causes unnecessary boilerplate and clunky code mangling.

Like closures and encapsulation without language support of objects.

This book gives a great insight about immutable and mutable state (with pros and cons), typisation, FP, OOP, and many other things in a very beginner-friendly manner

This book isn't focused on recent trends or properties specific to a certain field, and thus applies to all design. It provides a broad view and allows focusing on the fundamental goals of the user experience, rather than being limited in scope.

Whatever that's being designed, for whatever purpose, it always has the same goal of being used by someone. This book is focused on that interaction and on why users make mistakes. These principles still apply directly to web design, when design leads users to make mistakes, it will ultimately drive users away.