As an enterprise and software architect the one thing I hate most about my
job is documentation, yet the importance of doing documentation on sizable
projects is what I find myself preaching about the most.
One reason I understand the importance of documentation is that I came from
an electronic engineering background. As an electronic engineer 93% - 97% of
my time was consumed doing proof of concepts and documentation. Almost all of
that time was documentation.
It was just my luck that my boss was an English grammar teacher before moving
into engineering. My documents came back very bloody. He used a red pen to
mark up my documents. It took me 2 years, and a whole lot of tongue biting,
but I started getting papers through him without a red mark. I still remember
the first one. I walked outside to where the smokers took their breaks and
let out a screaming "YES, Fina... (more)
After reading Architecture Principles and Enterprise Architecture at Work I
decided I would also read this book and Enterprise Governance and Enterprise
Engineering as well. I am starting Enterprise Governance and Enterprise
Engineering now. This series is great!!! I recommend every Enterprise
Architect buy the series.
This book was the first of the series. It is only 145 pages long, but it is
packed full of valuable information.
This book puts Enterprise Architecture into context. It gives a complete
picture of Enterprise Architecture.
It starts with a great chapter on why Enterpr... (more)
I must admit I was mislead by the title of this book, but it was my own
fault. I was in the middle of developing an ASP.NET application that was
using a lot of the SharePoint web services and the SharePoint Server Object
Model. Although it used all SharePoint data, my application was completely
separate from the main SharePoint site and completely built with ASP.NET
outside of SharePoint and the SharePoint Designer. In my mind I wanted this
book to be all about that and I allowed the title to make me believe it would
Although the book was not what I expected it is still a gre... (more)
I purchased the OS X Lion: The Missing Manual to help me ramp up for my new
MacBook Pro. Although I had been a Mac user in the past, it was in the
distant past. It did a great job answering all the questions I had as I
familiarized myself with the Mac operating system. The author does a great
job of explaining things and he covers a ton of information.
As soon as the OS X Mountain Lion: The Missing Manual version was available I
wanted it. It is by far the best resource available for getting answers
quickly to any questions I have about the new OS X Mountain Lion operating
If I had to give this book a one word description, I would say it is
'balanced'. In the beginning of the book the author mentions that he does not
want to right one of those books that list a little code and then explains
the code, changes the code, explains those changes and so on and so on.
At first he scared me. I have read some insanely wordy programming and
engineering books. I have a much harder time getting through those than the
type the author described. I was afraid this book would be one of those that
I don't get anything out of except war stories from the author's caree... (more)