Share the intellectual wealth
The Five Underplayed Premises Of TDD
Contract Tests - Parameterised Test Cases
Contract Tests - Abstract Test Cases
Contract Tests
The Testing Quadrant
Tales Of TDD: The Big Refactoring
Implementing Approval Tests For PDF Document Generation
Approval Tests For PDF Document Generation
Ignoring Tests
Writing Maintainable Unit Tests In Print
Tales Of TDD: The Case Of Overused Test Doubles
Book Launch: Writing Maintainable Unit Tests
Avoid Inheritance For Test Classes
How To Write Unit Tests For Logging
Prevent Domain Knowledge From Sneaking Into Solitary Tests
Why Solitary Tests Should Be Easy To Read
Tales Of TDD: Stressed And Always In A Hurry
Dealing With Date/Time In Solitary Tests
Announcing Book: Writing Maintainable Unit Tests
Only Test Through Public Interfaces
Inside-Out and Outside-In TDD
Test Double Heuristics
Excessive Specification of Test Doubles
The Boundaries of Solitary Tests
Test Doubles
Indirect Inputs and Outputs
State versus Behaviour Verification
Cascading Failures
The Designing versus Testing Mindset
Why Write Maintainable Unit Tests?
Announcing Video Course: Writing Maintainable Unit Tests
The Test Pyramid
A Taxonomy Of Tests
Fast Feedback
Debugability Considered Useful
Blaming Mocks For Bad Design
Listening to the Vital Signs of TDD
All in the Name of DRY
Memo on O-Ring and Software Erosion
Learning F# - The Thunderdome Principle for Functions
Learning F# - Passing Parameters to Functions
The Burden of Features in Software
Product or Project Focused
Premature Abstraction
The Quest for the One True Static Site Generator
Using F# in Sublime Text on Linux Mint
Hacking Endeavours - A Tale About Having Fun
Out of the Tar Pit
Clojure Kata #3 – Roman Numerals
Awesome talks