appendixc.html

Thinking in c++ 2nd edition,c++编程思想（第2版）

<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Effective C++</B> (2<SUP>nd</SUP>
Edition, Addison-Wesley 1998) and <B>More Effective C++</B> (Addison-Wesley
1996), by <A NAME="Index2775"></A>Scott Meyers. The classic, must-have texts for
serious problem-solving and code design in C++. I&#8217;ve tried to capture and
express many of the concepts from these books in <I>Thinking in C++</I>, but I
don&#8217;t fool myself in thinking that I&#8217;ve succeeded. If you spend any
serious time with C++ you&#8217;ll end up with these books. Also available on CD
ROM. </FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Ruminations on C++</B>, by
<A NAME="Index2776"></A>Andrew Koenig and <A NAME="Index2777"></A>Barbara Moo
(Addison-Wesley, 1996). Andrew worked directly with Stroustrup on many aspects
of the C++ language and is an extremely reliable authority. I&#8217;ve also
found the incisiveness of his insights to be refreshing, and have learned much
from him, both in print and in person, over the years.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Large-Scale C++ Software Design</B>,
by <A NAME="Index2778"></A>John Lakos<B> </B>(Addison-Wesley, 1996). Covers
issues and answers questions you will encounter during the creation of big
projects, but often smaller ones as well.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>C++ Gems</B>, Stan Lippman, editor
(SIGS publications, 1996). A selection of articles from <I>The C++
Report</I>.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>The Design &amp; Evolution of C++</B>,
by <A NAME="Index2779"></A>Bjarne Stroustrup (Addison-Wesley 1994). Insights
from the inventor of C++ about why he made various design decisions. Not
essential, but interesting.</FONT><A NAME="_Toc472655073"></A><BR></P></DIV>
<A NAME="Heading492"></A><FONT FACE = "Verdana"><H2 ALIGN="LEFT">
Analysis &amp; design<BR><A NAME="Index2780"></A><A NAME="Index2781"></A></H2></FONT>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Extreme Programming Explained </B>by
<A NAME="Index2782"></A>Kent Beck (Addison-Wesley 2000). I <I>love</I> this
book. Yes, I tend to take a radical approach to things but I've always felt that
there could be a much different, much better program development process, and I
think XP comes pretty darn close. The only book that has had a similar impact on
me was <I>PeopleWare </I>(described below), which talks primarily about the
environment and dealing with corporate culture. <I>Extreme Programming
Explained</I> talks about programming, and turns most things, even recent
&#8220;findings,&#8221; on their ear. They even go so far as to say that
pictures are OK as long as you don&#8217;t spend too much time on them and are
willing to throw them away. (You&#8217;ll notice that this book does <I>not
</I>have the &#8220;UML stamp of approval&#8221; on its cover.) I could see
deciding whether to work for a company based solely on whether they used XP.
Small book, small chapters, effortless to read, exciting to think about. You
start imagining yourself working in such an atmosphere and it brings visions of
a whole new world.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><A NAME="Index2783"></A><A NAME="Index2784"></A><FONT FACE="Georgia"><B>UML
Distilled</B> by <A NAME="Index2785"></A>Martin Fowler (2<SUP>nd</SUP> edition,
Addison-Wesley, 2000). When you first encounter UML, it is daunting because
there are so many diagrams and details. According to Fowler, most of this stuff
is unnecessary so he cuts through to the essentials. For most projects, you only
need to know a few diagramming tools, and Fowler&#8217;s goal is to come up with
a good design rather than worry about all the artifacts of getting there. A
nice, thin, readable book; the first one you should get if you need to
understand UML.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>The Unified Software Development
Process</B> by <A NAME="Index2786"></A>Ivar Jacobsen, Grady
Booch<A NAME="Index2787"></A>, and <A NAME="Index2788"></A>James Rumbaugh
(Addison-Wesley 1999). I went in fully prepared to dislike this book. It seemed
to have all the makings of a boring college text. I was pleasantly surprised
&#8211; only pockets of the book contain explanations that seem as if those
concepts aren&#8217;t clear to the authors. The bulk of the book is not only
clear, but enjoyable. And best of all, the process makes a lot of practical
sense. It&#8217;s not Extreme Programming (and does not have their clarity about
testing) but it&#8217;s also part of the UML juggernaut &#8211; even if you
can&#8217;t get XP adopted, most people have climbed aboard the &#8220;UML is
good&#8221; bandwagon (regardless of their <I>actual</I> level of experience
with it) and so you can probably get it adopted. I think this book should be the
flagship of UML, and the one you can read after Fowler&#8217;s <I>UML
Distilled</I> when you want more detail.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">Before you choose any method, it&#8217;s
helpful to gain perspective from those who are not trying to sell one.
It&#8217;s easy to adopt a method without really understanding what you want out
of it or what it will do for you. Others are using it, which seems a compelling
reason. However, humans have a strange little psychological quirk: If they want
to believe something will solve their problems, they&#8217;ll try it. (This is
experimentation, which is good.) But if it doesn&#8217;t solve their problems,
they may redouble their efforts and begin to announce loudly what a great thing
they&#8217;ve discovered. (This is denial, which is not good.) The assumption
here may be that if you can get other people in the same boat, you won&#8217;t
be lonely, even if it&#8217;s going nowhere (or sinking).</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia">This is not to suggest that all
methodologies go nowhere, but that you should be armed to the teeth with mental
tools that help you stay in experimentation mode (&#8220;It&#8217;s not working;
let&#8217;s try something else&#8221;) and out of denial mode (&#8220;No,
that&#8217;s not really a problem. Everything&#8217;s wonderful, we don&#8217;t
need to change&#8221;). I think the following books, read <I>before</I> you
choose a method, will provide you with these tools.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Software Creativity</B>, by Robert
Glass<A NAME="Index2789"></A> (Prentice-Hall, 1995). This is the best book
I&#8217;ve seen that discusses <I>perspective</I> on the whole methodology
issue. It&#8217;s a collection of short essays and papers that Glass has written
and sometimes acquired (P.J. Plauger<A NAME="Index2790"></A> is one
contributor), reflecting his many years of thinking and study on the subject.
They&#8217;re entertaining and only long enough to say what&#8217;s necessary;
he doesn&#8217;t ramble and bore you. He&#8217;s not just blowing smoke, either;
there are hundreds of references to other papers and studies. All programmers
and managers should read this book before wading into the methodology
mire.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Software Runaways: Monumental Software
Disasters</B>, by Robert Glass (Prentice-Hall 1997). The great thing about this
book is that it brings to the forefront what we don&#8217;t talk about: how many
projects not only fail, but fail spectacularly. I find that most of us still
think &#8220;That can&#8217;t happen to me&#8221; (or &#8220;That can&#8217;t
happen <I>again</I>&#8221;) and I think this puts us at a disadvantage. By
keeping in mind that things can always go wrong, you&#8217;re in a much better
position to make them go right.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Object Lessons</B> by Tom
Love<A NAME="Index2791"></A> (SIGS Books, 1993). Another good
&#8220;perspective&#8221; book.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Peopleware</B>, by Tom
Demarco<A NAME="Index2792"></A> and Timothy Lister<A NAME="Index2793"></A>
(Dorset House, 2<SUP>nd</SUP> edition 1999). Although they have backgrounds in
software development, this book is about projects and teams in general. But the
focus is on the <I>people</I> and their needs rather than the technology and its
needs. They talk about creating an environment where people will be happy and
productive, rather than deciding what rules those people should follow to be
adequate components of a machine. This latter attitude, I think, is the biggest
contributor to programmers smiling and nodding when XYZ method is adopted and
then quietly doing whatever they&#8217;ve always done.</FONT><BR></P></DIV>
<DIV ALIGN="LEFT"><P><FONT FACE="Georgia"><B>Complexity</B>, by M. Mitchell
Waldrop<A NAME="Index2794"></A> (Simon &amp; Schuster, 1992). This chronicles
the coming together of a group of scientists from different disciplines in Santa
Fe, New Mexico, to discuss real problems that the individual disciplines
couldn&#8217;t solve (the stock market in economics, the initial formation of
life in biology, why people do what they do in sociology, etc.). By crossing
physics, economics, chemistry, math, computer science, sociology, and others, a
multidisciplinary approach to these problems is developing. But more
importantly, a different way of <I>thinking</I> about these ultra-complex
problems is emerging: Away from mathematical determinism and the illusion that
you can write an equation that predicts all behavior and toward first
<I>observing </I>and looking for a pattern and trying to emulate that pattern by
any means possible. (The book chronicles, for example, the emergence of genetic
algorithms.) This kind of thinking, I believe, is useful as we observe ways to
manage more and more complex software projects.</FONT><BR></P></DIV>
<DIV ALIGN="CENTER">
    <FONT FACE="Verdana" size = "-1">
     [ <a href="AppendixB.html">Previous Chapter</a> ] 
    [ <a href="Contents.html">Table of Contents</a> ] 
    [ <a href="DocIndex.html">Index</a> ]
    
    </FONT>
    <BR>
 Last Update:09/27/2001</P></DIV>

</BODY>

</HTML>