Code complete a practical handbook of software construction
Code Complete - WikipediaThat being said I have read this book over and over again, chapters and sections at a time. Often refering to it for inspiration, understanding and often solutions to problems. Giving the reader plenty of resources to further their discipline. Irrespective of programming language and platform. The first part of the book is dedicated to laying the foundations for all software development projects. Providing tips, strategies and discussions for all the things software developers should do before putting hands and keyboards and churn out code.
Chapter 9. The Pseudocode Programming Process
This is one the best books for programmers and I think every programmer should read it. There are two reasons for this. Praftical you're a seasoned programmer, you may consider skipping it. I'm glad that there are technical books like O'Reilly's Head First series out there.
However, please sign up! View 2 comments. To see what your friends thought of this book, having conventions makes code easier to read and modify because a convention can communicate a lot without using much space or requiring much thinking. This section discusses how deep nesting of control structures tends to make code complex.
Putting These Ideas into Practice
Now this classic book has been fully updated and revised with leading-edge practices—and hundreds of new code samples—illustrating the art and science of software construction. Capturing the body of knowledge available from research, academia, and everyday commercial practice, McConnell synthesizes the most effective techniques and must-know principles into clear, pragmatic guidance. No matter what your experience level, development environment, or project size, this book will inform and stimulate your thinking—and help you build the highest quality code. Discover the timeless techniques and strategies that help you: Design for minimum complexity and maximum creativity Reap the benefits of collaborative development Apply defensive programming techniques to reduce and flush out errors Exploit opportunities to refactor—or evolve—code, and do it safely Use construction practices that are right-weight for your project Debug problems quickly and effectively Resolve critical construction issues early and correctly Build quality into the beginning, middle, and end of your project View more on Amazon You might also like View The Pragmatic Programmer: From Journeyman to Master on Reading Length. Look on Amazon. Reading Length. Search for any book Search!
More filters. It is close to pages. One key point of this section is that the goals of a certain construction project should be clear.
A "wicked" problem is one that can be clearly defined fo by solving it. Yes, but using descriptive variable names will save. One example McConnell gives writing an assertion library if your language does not support assertions. Steven C?