Skip to main content

Recommended Reading List 2015

In a similar manner to previous years here is my recommended reading list for 2015. As before some of these books have been released for a while, but these are some of my highlights for various reasons.


Dependency Injection in .NET
I had put off reading this book for a while despite numerous teams having a copy. It turns out a good chunk of the book is applicable to any language, with the later third being dedicated to actual .NET solutions. The other two thirds of the book has expanded my understanding of DI.
Effective Java: A Programming Language Guide
Many developers recommend this book even for non Java development. Many of the tips and advice included we not new to myself but the book provided further insight and explanation. A good summary of best practices for any OO developers.
Web Application Security, A Beginner's Guide
A good introductory book on security which provided a useful refresher for myself as well as providing a platform for further research on some of the key areas and topics.
Enterprise Integration Patterns
A useful sequel to expand on Patterns of Enterprise Application Architecture. This book focuses more on messaging concepts, going into detail on a number of topics. The content of the book is expressed in technology agnostic terms, which has been incredibly useful when applied to actual implementations.
REST API Design Guidelines
Much of the guidelines in here fall into the category of common sense or industry experience. Despite this the guidelines provide great justifications for API design. An essential reference for any REST API.
57 Exercises for Programmers
A highly practical book in the sense that the book is full of over sixty practical tasks. Many of these fall into code katas which are ideal for learning new languages or just staying sharp.
Practical Object-Oriented Design in Ruby
Despite the name this book applies to OO development in general while the examples use Ruby. The ideas and concepts expressed in this book have changed my view on OO programming. If anything the book will make you think differently about how to design and develop solutions.
Fifty Quick Ideas To Improve Your Tests
A light read with each chapter dedicated to a single, focused topic. Many of the ideas are well known practices but with expanded justifications and recommendations.
HTTP The Definitive Guide
The guide to HTTP if you are a developer. Each area is explained from high level concepts down to the nitty gritty details.


Implementing Lean Software Development: From Concept to Cash
A great summary of applying lean concepts to software development. Much of the content is familiar though the ideas applied to software development makes this book stand out. This acts as a useful refresher for lean processes as well.
The Lean Startup
One of the most inspirational books I've read this year. Full of useful and tested practices that has changed my perspective on beginning a startup. Interestingly much of the advice can be applied to individuals working within larger organizations on smaller projects.


Popular posts from this blog

Three Steps to Code Quality via TDD

Common complaints and problems that I've both encountered and hear other developers raise when it comes to the practice of Test Driven Development are: Impossible to refactor without all the tests breakingMinor changes require hours of changes to test codeTest setup is huge, slow to write and difficult to understandThe use of test doubles (mocks, stubs and fakes is confusing)Over the next three posts I will demonstrate three easy steps that can resolve the problems above. In turn this will allow developers to gain one of the benefits that TDD promises - the ability to refactor your code mercifully in order to improve code quality.StepsStop Making Everything PublicLimit the Amount of Dependencies you Use A Unit is Not Always a Method or ClassCode quality is a tricky subject and highly subjective, however if you follow the three guidelines above you should have the ability to radically change implementation details and therefore improve code quality when needed.

DRY vs DAMP in Tests

In the previous post I mentioned that duplication in tests is not always bad. Sometimes duplication becomes a problem. Tests can become large or virtually identically excluding a few lines. Changes to these tests can take a while and increase the maintenance overhead. At this point, DRY violations need to be resolved.SolutionsTest HelpersA common solution is to extract common functionality into setup methods or other helper utilities. While this will remove and reduce duplication this can make tests a bit harder to read as the test is now split amongst unrelated components. There is a limit to how useful such extractions can help as each test may need to do something slightly differently.DAMP - Descriptive and Meaningful PhrasesDescriptive and Meaningful Phrases is the alter ego of DRY. DAMP tests often use the builder pattern to construct the System Under Test. This allows calls to be chained in a fluent API style, similar to the Page Object Pattern. Internally the implementation wil…

Coding In the Real World

As a student when confronted with a problem, I would end up coding it and thinking - how do the professionals do this?For some reason I had the impression that once I entered the industry I would find enlightenment. Discovering the one true way to write high quality, professional code.It turns out that code in industry is not too far removed from the code I was writing back when I knew very little.Code in the real world can be:messy or cleanhard or easy to understandsimple or complexeasy or hard to changeor any combination of the aboveVery rarely will you be confronted with a problem that is difficult. Most challenges typically are formed around individuals and processes, rather than day to day coding. Years later I finally have the answer. Code in the real world is not that much different to code we were all writing when we first started out.If I could offer myself some advice back in those early days it would be to follow KISS, YAGNI and DRY religiously. The rest will fall into plac…

Feature Toggles

I'm a fan of regular releasing. My background and experience leads me to release as regularly as possible. There are numerous benefits to regular releases; limited risk, slicker release processes and the ability to change as requirements evolve.The problem with this concept is how can you release when features are not functionally complete?SolutionIf there is still work in progress, one solution to allow frequent releases is to use feature toggles. Feature toggles are simple conditional statements that are either enabled or disabled based on some condition.This simple example shows a feature toggle for an "Edit User" feature. If the boolean condition is false, then we only show the "New User" feature and the "Admin" feature. This boolean value will be provided by various means, usually a configuration file. This means at certain points we can change this value in order to demonstrate the "Edit User" functionality. Our demo environment could …

Reused Abstraction Principle

This is the second part of my series on abstractions.Part 1 - AbstractionsPart 3 - Dependency Elimination PrincipleThe Reused Abstraction Principle is a simple in concept in practice, but oddly rarely followed in typical enterprise development. I myself have been incredibly guilty of this in the past.Most code bases have a 1:1 mapping of interfaces to implementations. Usually this is the sign of TDD or automated testing being applied badly. The majority of these interfaces are wrong. 1:1 mappings between interfaces and implementations is a code smell.Such situations are usually the result of extracting an interface from an implementation, rather than having the client drive behaviour.These interfaces are also often bad abstractions, known as "leaky abstractions". As I've discussed previously, these abstractions tend to offer nothing more than simple indirection.ExampleApply the "rule of three". If there is only ever one implementation, then you don't need …