Gojko Adzic

Here’s the video from the talk on dependency injection with Castle Windsor that Mike Hadlow and I did last month at Skills Matter.

in the first part of the talk, Mike introduces Dependency Injection and explains how to apply that pattern in practice with Castle Windsor. Then he talks about Castle component lifestyles and implementing common architectural and design patterns using Castle Windsor component model. In the second part of the talk, I present strategies how to manage component configuration effectively for production. After that, I explain how to use Castle facilities to extend the framework, integrate third-party services and manage components easier.

download the slides and the source code from the talk.

In order to get requirements, business analysts often work through a number of realistic examples with the customers, such as existing report forms or examining existing work processes. These examples are then translated to abstract requirements in the first step of the Telephone game. Developers extract knowledge from that and translate it into executable code, which is handed over to testers. Testers then take the specifications, extract knowledge from them and translate it into verification scripts, which are then applied to the code that was handed over to them by the developers. In theory, this works just fine and everyone is happy. In practice, this process is essentially flawed and leaves huge communication gaps at every step. Important ideas fall through those gaps and mysteriously disappear. After every translation, information gets distorted and misunderstood, leading to large mistakes once the ideas come through the other end of the pipe. Continue Reading »