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)
Processes are not documented and reused by a set of individuals because they
lead to failure. Like design patterns, they are documented and reused because
they lead to success.
They are all put together by very talented people who have successfully used
them to develop software multiple times. For them the process is easy to use
and understand. The teams that have not used it have a steep learning curve
ahead of them. Just looking at the diagram of a pattern or process,
definitely will lead you to failure every time.
I have seen Waterfall, Spiral, RUP, OpenUP, and Scrum all fail ... (more)
Finally a book from an industry leader that has the guts to write about the
real world of Agile software development. If I had to pick one word to
describe this book, it would be 'truth'.
This book is going to raise the blood pressure of some of the Agilists out
there. If you think you may be one of those, do yourself a favor and keep at
the forefront of your mind that the author points out all the good in Agile
too. He is not telling a one sided story. When reading a strongly opinionated
book like this, we tend to only see the things the author is pointing out as
our flaws, or ... (more)
This review is for two books. It is for Android: How to Program (2nd Edition)
and Android for Programmers: An App-Driven Approach (2nd Edition) . Why?
Because Android: How to Program (2nd Edition) includes the entire Android for
Programmers: An App-Driven Approach (2nd Edition) book.
Android: How to Program (2nd Edition) is in black and white and it also
includes a Java language overview/reference. This book is great for the
programmer coming from another language. Having the Java reference included
as the second half of the book comes in really handy. Lately I have spent
most of... (more)
At the beginning of the book the authors say they created this book to be
used in a classroom setting. I agree that it is a great book for the
classroom, but I would also recommend it to anyone who wants to learn about
the current Agile methodologies. It does what the title of the book says it
does, and it introduces the reader to Agile methods.
It starts with a nice introduction to the Agile movement's history and then
covers all the traditional topics that fall within the Agile purview. I have
listed the chapters below to give you a high level view of the topics