← Originals
Robert C. Martin

Robert C. Martin

8 books

guides

What they argue

Robert C. Martin is a software engineering thinker who treats software development as a professional craft rather than just a technical skill. He works in the territory of software architecture, engineering disciplines, and the human dynamics of Agile development.

  1. Agile as a Technical Discipline

    Agile success is predicated on the marriage of soft human dynamics like communication and trust with hard engineering disciplines. The values of the Agile Manifesto are only achievable if the team possesses strong underlying engineering practices.

    From Agile Software Development, Principles, Patterns, and Practices (book)

  2. The Dependency Rule

    Source code dependencies can only point inwards toward the core business logic to prevent 'Leaky Abstractions.' This ensures that the business rules are isolated from the infrastructure tools used to run the software.

    From Clean Architecture (book)

  3. Code as Communication

    Because software is read far more often than it is written, the primary user of code is the human reader. Clean code is about making the next human understand your intent without having to decipher your logic.

    From Clean Code: A Handbook of Agile Software Craftsmanship (book)

  4. The Craft of Software

    Software development is a trade involving skills, tools, and a standard of excellence. This perspective shifts the identity of the developer from a 'coder' to a practitioner of a craft.

    From Clean Craftsmanship (book)

  5. Primacy of Automated Testing

    Writing tests as a prerequisite for production code (TDD) provides a necessary safety net for development. Without this, developers lack the security to make changes to the codebase.

    From Agile Software Development, Principles, Patterns, and Practices (book)

  6. Meaningful Names

    The name of a variable, function, or class should reveal its intent, purpose, and scope. Developers should avoid generic names and abbreviations that require a mental lookup table.

    From Clean Code: A Handbook of Agile Software Craftsmanship (book)

Every idea names the summary it came from. Written by a local model from this mind’s own work, never from memory.

Books 5

Open Robert C. Martin in Originals