Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?

Book description:

Even bad code can function. But if code isn't clean, it can bring a development organization to its knees. Every year, countless hours and significant resources are lost because of poorly written code. But it doesn't have to be that way.

Noted software expert Robert C. Martin presents a revolutionary paradigm with Clean Code: A Handbook of Agile Software Craftsmanship. Martin has teamed up with his colleagues from Object Mentor to distill their best agile practice of cleaning code "on the fly" into a book that will instill within you the values of a software craftsman and make you a better programmer -- but only if you work at it.

What kind of work will you be doing? You'll be reading code -- lots of code. And you will be challenged to

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Quality Book Excerpts Perfect Software, Ch. 8: What Makes a Good Test Seven Steps to Mastering Business Analysis, Ch. 1 The Software Project Manager's Bridge to Agility: Chapter 5, Scope Management Software Security Engineering: A Guide for Project Managers -- Chapter 3, Requirements Engineering for Secure Software Requirements Management Using IBM Rational RequisitePro: Chapter 1, Requirements Management Implementing ITIL Configuration Management: Chapter 3, Determining Scope, Span and Granularity Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams Inherent Quality Simplicity, Section V: The Evolution Managing the Test People, Chapter 6: Keeping Your Beast Effective Mastering the Requirements Process, 2nd Edition: Chapter 2, The Requirements Process Methodologies Agile Software Development: The Cooperative Game, 2nd Edition -- Chapter 3, Communicating, Cooperating Teams Inherent Quality Simplicity, Section V: The Evolution Outside-in Software Development: A Practical Approach to Building Successful Stakeholder-based Products -- Chapter 1, Introducing Outside-in Development Automated Defect Prevention: Best Practices in Software Management, Chapter 1 -- The Case for Automated Defect Prevention The Economics of Open Source Software Development -- Chapter 1, An Introduction Model-Driven Software Development: Technology, Engineering, Management -- Chapter 2, MDSD: Basic Ideas and Terminology Implementing the IBM Rational Unified Process and Solutions: A Guide to Improving Your Software Development Capability and Maturity -- Chapter 2, Your First Steps Scaling Software Agility: Best Practices for Large Enterprises -- Chapter 7, The Essence of Agile Real-Life MDA -- Chapter 1, Introduction Agile software development Agile development growing, but problems remain Agile, IBM tools boost Merge Healthcare's software quality Agile development reshaping requirements Agile software development tutorial: How to transition to agile Agile software development tutorial: Pros and cons of agile Agile software development tutorial: Agile requirements gathering Agile software development tutorial: Agile project management, tools Agile software development tutorial: Agile testing Reporter's Notebook: Jack Vaughan on agile methodology Best practices for moving testers from waterfall to agile development

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary acceptance test  (SearchSoftwareQuality.com) iteration  (SearchSoftwareQuality.com) planning board  (SearchSoftwareQuality.com) planning game  (SearchSoftwareQuality.com) release  (SearchSoftwareQuality.com) release plan  (SearchSoftwareQuality.com) spike  (SearchSoftwareQuality.com) stand-up  (SearchSoftwareQuality.com) story  (SearchSoftwareQuality.com) timebox  (SearchSoftwareQuality.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

think about what's right about that code, and what's wrong with it. More importantly, you will be challenged to reassess your professional values and your commitment to your craft.

Clean Code is divided into three parts. The first describes the principles, patterns, and practices of writing clean code. The second part consists of several case studies of increasing complexity. Each case study is an exercise in cleaning up code -- of transforming a code base that has some problems into one that is sound and efficient. The third part is the payoff: a single chapter containing a list of heuristics and "smells" gathered while creating the case studies. The result is a knowledge base that describes the way we think when we write, read, and clean code.

This book is a must for any developer, software engineer, project manager, team lead, or systems analyst with an interest in producing better code.

>> Read Chapter 1: What Is Clean Code?

>> Buy the book