I bought SQL Antipatterns in the middle of an increasingly stressful project. Taking two days out to read it thoroughly and correct some of the patterns we were guilty of turned the project around for the better. We were able stop worrying about database design and concentrate on security issues.
For me, the best thing about the book is that it serves as a comprehensive reference of the benefits of doing things properly, and justification of the time this often requires.
It helped a lot, very fast.
My only constructive criticism is that I wish there was more content. Database good practices is a very expansive subject, and as I was reading the book I couldn't help but wish the author was "building up to the good stuff" as some other PragProg books do. This book is reasonably priced so it remains good value, but if it was $30+ I might have given it four stars instead of five for this reason.
2017: The Year of Golang
3 months ago