The first time I’ve learnt about OOP Design Patterns was at a Software Engineering introductory course. Since then I had a growing feeling that there is something wrong in the way that the industry treats them. Don’t get me wrong – those patterns exist so that developers wouldn’t need to reinvent the wheel each time … Continue reading The Problem With Design Patterns
I always believed OO design patterns to be necessary to know and understand by all software developers, I didn’t like the fact that sometimes design was forced into a known design pattern just because a pattern existed (and wrote about it). After seen patterns abused time after time I lost faith and I was frustrated … Continue reading Book Review – Head First Design Patterns
While teaching a course on design patterns I was asked by one of the participants when would I use an interface and when to use an abstract class. I’ve started the outline the reasons for each and ended up with a few good ones which I like to share in the following post. Interfaces and … Continue reading Back to basics: Using interface vs. abstract class
In my not-so-distant past I needed to write a component which would control an air conditioning unit.My application needed to send commands to the external device (on, off, set temperature) and read information from it (room temperature, humidity etc.)And so I came with the following:It’s a bit simplistic but the idea was that the client … Continue reading Unit and integration are ambiguous names for tests–and that’s ok
Now that I’m back from NDC London I have a chance to plan my upcoming speaking engagements – and it’s going to be a few busy months.I’ve already blogged about my plans for the next few months but since then I found out that I’ll be coming back to London (always a pleasure) in March … Continue reading New Speaking engagement – DevWeek 2015
A while ago I was asked to talk about the problems of using TDD – being me I’ve decided to do the exact opposite, this session was names “what is wrong with TDD”.I felt that one of the major issues is that TDD looks weird, it’s counter-intuitive, and convincing developers to actually try it hard … Continue reading What’s wrong with TDD
Not being able to unit test an essential scenario is one of the reasons developers stop unit testing their code. In fact most of the time when a team decides not to use TDD (Test Driven Development) is because it seems as if they won’t be able to test the production code using unit tests. … Continue reading How to unit test “un-testable” code (in a nutshell)
Helper Code 