Foundations for Architecting Data Solutions: Managing Successful Data Projects 1st Edition

Very informative. Well organized. I was able to break out chapters and read independently. Each chapter callout concepts from previous chapters and provided a roadmap on what I needed to understand based upon me skipping around the book. Author's humor was transparent in many of the examples.

If you're an engineer who's looking for implementation details around the topics in this book, this isn't that book. It is a however a good guide at a 'high-level' topic details. It works as a good template to fact check on topics and points that would help you dig deeper into topics outside of the book from a data architecture perspective. In that respect it helped there and I'd say a 2nd edition of this book could be a 4.5 or higher in rating if the contents are more focused on a working example through out the book to demonstrate the principles via implementation.

A lot of this stuff is really good to know or think about when working on large scale data projects. Many data projects are cross functional, far reaching, and political. Having some guide lines to follow helps keep you and your teams honest.

It is a poorly written book, making it extremely difficult to read. I really pushed myself several times to keep reading but it does not provide anything to the reader.

I thought this book would help me understand how to do application projects, as it is one instance of a data project, and the book indeed lists it as such.Having skimmed through the whole book in about 30 minutes (which, in my experience, means that there is nothing very concrete in a book to think about; if the book packs a lot of ideas, it takes days of month to read and understand it), I concluded that this book is more like a checklist of high-level topics (such as "don't forget about authentification!", which, in my opinion, is quite obvious) that you should consider when doing aforementioned projects. And it doesn't give any concrete example of how you can do any of the points the author mentions, their drawbacks or anything like that.And I haven't found any example (maybe there are a few and I missed them), and it only exacerbates the problem of the lack of details.So, I was hoping for a much more practical book, rather than high-level rant.

This reads like a dictionary…Very hard to get grasp the concepts if I am struggling to stay awake.