Keeping Software Soft cover page

Keeping Software Soft

Keeping Software Soft

A Practical Guide for Developers, Testers, and Managers

This book is free, please consider paying what you think it's worth and supporting independent authors - thanks :)
Keeping Software Soft Edit
This book is 100% complete


About the Book

Software should be easy to change.

Happier, more enjoyable, and more productive software development.

Keeping Software Soft is aimed primarily at apprentice and journeyman developers.The book provides practical guidance on how to keep software as soft as we can.

Reader Comments

"...a great publication for both those just starting on a software development path and those of us who have been round for longer than we care to admit!"

"...strongly recommended it to the junior programmers working at my major contract client - as a clear overview with good examples of software development."

"...well worth the price."


978-0-9924164-0-9 [PDF]

978-0-9924164-1-6 [EPUB]

978-0-9924164-2-3 [MOBI]

Read more

Table of Contents

    • About The Author
      • Other Leanpub Books by Jason Roberts
      • Pluralsight Courses
    • Introduction
      • Why Keep Software Soft?
      • Why Read This Book?
  • Part 1: The Code
    • The SOLID Principles of OO Design
      • The Single Responsibility Principle (SRP)
      • The Open Closed Principle (OCP)
      • The Liskov Substitution Principle (LSP)
      • The Interface Segregation Principle (ISP)
      • Dependency Inversion Principle (DIP)
    • Other Important Principles
      • Keep It Simple Stupid (KISS)
      • Don’t Repeat Yourself (DRY)
      • You Aren’t Gonna Need It (YAGNI)
      • Cohesion
      • Coupling
      • Law of Demeter (LoD)
    • Dependency Inversion Revisited
      • Dependency Injection Containers
      • An Example of Dependency Injection with Ninject
      • Other Containers
      • Why Use a Dependency Injection Container?
    • Some Useful Design Patterns
      • Gateway
      • Decorator
      • Strategy
      • Factory
      • Chain of Responsibility
    • Readability - Writing Code for Humans
      • Comments
      • Naming Booleans
      • Method Length
      • Remove Unused Code
      • Nesting
      • Naming Variables and Parameters
      • Whitespace
      • Regions
      • Magic Strings and Constants
    • An Introduction to Architectural Styles
      • Client-Server
      • Layered
      • Message Bus
      • Service Oriented Architecture
      • Onion Architecture
      • Event Sourcing
  • Part 2: Testing
    • An Introduction to Unit Testing with
      • Qualities of Good Unit Tests
      • Testing Frameworks
      • About
      • Using
      • Data Driven Tests
    • Test Driven Development
      • Overview
      • Example
      • Practicing TDD
      • Why TDD?
    • Faking It - Testing Code in Isolation
      • Mock, Stub, Fake, Dummy, Test Double
      • An Example of Faking
    • Auto Mocking
      • Introducing Auto Mocking
      • More About AutoFixture
      • AutoFixture and Custom Attributes
    • Introduction to JavaScript Unit Testing
      • Introducing QUnit
      • Creating and Running QUnit Tests in Visual Studio 2012
      • Creating and Running QUnit Tests in HTML
    • An Introduction to Automated Functional UI Testing for Web Applications
      • Record-Playback Versus Coded Automation
      • An Example of Coded AFUITs Using WatiN
      • The Demo Application
      • Creating the First Tests
      • Refactoring the Tests
      • Some Other Tools
    • An Introduction to Continuous Integration with TeamCity
      • Build Pipelines
      • Implementing a Build Pipeline in TeamCity
      • Alternative CI/Build Servers
    • A Holistic View of Testing
      • Types of Testing
      • The Testing Pyramid
      • What and Where to Test
      • Testing Legacy Applications
  • Part 3: People and Process
    • An Introduction to Agile Software Development
      • Overview
      • Agile Software Development in Practice
      • Overarching Principles
    • Pair Programming and Code Reviews
      • Formal Code Reviews
      • Pair Programming
    • Time Management and Motivation
      • Time Management
      • Prioritisation With MoSCoW
      • Prioritisation with Covey Quadrants
      • Maintaining Energy with the Pomodoro Technique
      • Maintaining Motivation with the Power of Three
    • Technical Debt
      • Examples of Technical Debt
      • Causes of Technical Debt
      • Mindfulness of Creating Technical Debt
      • Recording and Prioritising Technical Debt
      • The Effect of Technical Debt on People and Organisations
    • Software Craftsmanship, Professionalism, and Personal Development
      • Software Craftsmanship
      • Beyond Craftsmanship - Into Professionalism
      • Personal Development
    • What Programmers Want and What Your Manager Should Understand
      • What Programmers Want Survey
      • Challenging Work, Creative Solutions, Making a Difference
      • Tools and Environment
      • The Joel Test
  • Appendices
    • Appendix A: Manifesto for Agile Software Development
    • Appendix B: Principles behind the Agile Manifesto
    • Appendix C: Testing Framework Attributes
    • Appendix D: Design Pattern List
      • Creational Patterns
      • Structural Patterns
      • Behavioural Patterns
    • Appendix E: Manifesto for Software Craftsmanship

Read More

About the Author

The Leanpub Unconditional, No Risk, 100% Happiness Guarantee

Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks. We process the refunds manually, so they may take a few days to show up.
See full terms