Keeping Software Soft
Keeping Software Soft
A Practical Guide for Developers, Testers, and Managers
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.
"...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."
Table of Contents
About The Author
- Other Leanpub Books by Jason Roberts
- Pluralsight Courses
- Why Keep Software Soft?
- Why Read This Book?
- About The Author
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)
- 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
- Chain of Responsibility
Readability - Writing Code for Humans
- Naming Booleans
- Method Length
- Remove Unused Code
- Naming Variables and Parameters
- Magic Strings and Constants
An Introduction to Architectural Styles
- Message Bus
- Service Oriented Architecture
- Onion Architecture
- Event Sourcing
- The SOLID Principles of OO Design
Part 2: Testing
An Introduction to Unit Testing with xUnit.net
- Qualities of Good Unit Tests
- Testing Frameworks
- About xUnit.net
- Using xUnit.net
- Data Driven Tests
Test Driven Development
- Practicing TDD
- Why TDD?
Faking It - Testing Code in Isolation
- Mock, Stub, Fake, Dummy, Test Double
- An Example of Faking
- Introducing Auto Mocking
- More About AutoFixture
- AutoFixture and xUnit.net Custom Attributes
- 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
- An Introduction to Unit Testing with xUnit.net
Part 3: People and Process
An Introduction to Agile Software Development
- 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
- 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
- An Introduction to Agile Software Development
- 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
The Leanpub 60-day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them