I'm particularly interested in these two books. My buying decision (vs. a book about how to grok a library I really want to grok) is that these books cover topi

I'm particularly interested in these two books. My buying decision (vs. a book about how to grok a library I really want to grok) is that these books cover topics that I can't simply learn by downloading the documentation for a code project. For better or worse, they will be dogmatic and not purely technical, so they won't age as quickly as a book about a new technology. Designed for Use: Create Usable Interfaces for Applications and the Web http://pragprog.com/book/lmuse/designed-for-use http://pragprog.com/book/lmuse/designed-for-use Lukas's blog posts (http://ignorethecode.net/blog/ http://ignorethecode.net/blog/) have appeared on HN many times, and I have made a mental note to buy his design book. Technical Blogging: Turn Your Expertise into a Remarkable Online Presence http://pragprog.com/book/actb/technical-blogging http://pragprog.com/book/actb/technical-blogging Antonio has also posted on HN. I've been on the fence about this book, not sure if I need it, and I decided to pull the trigger and buy it. So I am now the proud owner of these two books. [edit: I think I might also get SQL Antipatterns http://pragprog.com/book/bksqla/sql-antipatterns http://pragprog.com/book/bksqla/sql-antipatterns after recognizing one in my own code. And Web Development Recipes http://pragprog.com/book/wbdev/web-development-recipes http://pragprog.com/book/wbdev/web-development-recipes. Am I done buying yet? Great deal.]