Code Complete (1993) (edit title/settings)

Ridiculously Simplified Synopsis edit see section history

show spoilers

Characters/People edit see section history

• Barry Boehm: Add a description of this character.
• Addison-wesley
• Beck
• Mcconnell
• Gilb
• Scott Meyers
• Basili
• Gerald Weinberg
• Edsger Dijkstra
• Steve
• Myers
• Donald Knuth
• Demarco
• Grady
• Curtis
• Tom
• Fred Brooks
• Mildred
• Fagan
• Shull
• Mavis
• Martin
• Yourdon
• Maguire
• Fowler
• Perl
• John Wiley
• Parnas
• Plauger
• Larman
• Callicles
• Andy Hunt
• Val
• Ismene
• Jon Bentley
• Perricone
• Mcgarry
• Thomas
• Bloch
• Beizer
• Gigatron
• Sedgewick

Quotes edit see section history

• “Their egos keep them from being great programmers”

• “The more humble you are, the faster you'll improve”

• “The more you learn to compensate for your small brain, the better a programmer you'll be”

• “The people who are best at programming are the people who realize how small their brains are”

• Popular Highlights from Kindle Customers

• In incremental development, you first make the simplest possible version of the system that will run.

  Highlighted by 43 Kindle customers

• Requirements describe in detail what a software system is supposed to do, and they are the first step toward a solution.

  Highlighted by 33 Kindle customers

• In programming, if your requirements are contaminated, they contaminate the architecture, and the architecture in turn contaminates construction. This leads to grumpy, malnourished programmers and radioactive, polluted software that's riddled with defects.

  Highlighted by 33 Kindle customers

• If you can't explain something to a six-year-old, you really don't understand it yourself. — Albert Einstein

  Highlighted by 31 Kindle customers

• There are two ways of constructing a software design: one way is to make it so simple that there are obviously no deficiencies, and the other is to make it so complicated that there are no obvious deficiencies.

  Highlighted by 30 Kindle customers

• A plan to follow the requirements rigidly is actually a plan not to respond to your customer.

  Highlighted by 29 Kindle customers

• The first prerequisite you need to fulfill before beginning construction is a clear statement of the problem that the system is supposed to solve.

  Highlighted by 29 Kindle customers

• When art critics get together they talk about Form and Structure and Meaning. When artists get together they talk about where you can buy cheap turpentine. — Pablo Picasso

  Highlighted by 29 Kindle customers

• Get into the habit of asking 'What should I hide?' You'll be surprised at how many difficult design issues dissolve before your eyes.

  Highlighted by 28 Kindle customers

• Classes and routines are first and foremost intellectual tools for reducing complexity. If they're not making your job simpler, they're not doing their jobs.

  Highlighted by 21 Kindle customers

Setting & Locations edit see section history

• Boston
• New York
• Redmond
• Englewood Cliffs
• England
• Modula
• Visual Basic
• Oman
• Los Alamitos
• Riel
• Wokingham
• Project Size

First Sentence edit see section history

Series & Lists edit see section history

Authors & Contributors edit see section history

1. Steve McConnell (Author)

First Edition edit see section history

Classification edit see section history

• Library of Congress: QA76.76 D3 M39
• Dewey: 005.1

Subjects edit see section history

• Books › Computers & Internet › Programming › Software Design, Testing & Engineering › Software Development
• Books › Computers & Internet › Programming › Languages & Tools
• Books › Computers & Internet › Computer Science › Software Engineering
• Books › Computers & Internet › Software › Business
• Books › Reference

More Books Like This edit see section history