• submit to reddit
Benjamin Mitchell07/20/11
0 replies

The importance of understanding variation or how to avoid treating all contractors as thieves

Here’s a story of how managers detected a problem, but by not understanding the cause of the problem of the type of variation the problem represented, applied the wrong type of solution which meant things were worse for everyone: Once upon a time in a...

Patrick Debois07/20/11
0 replies

Storytelling in IT - Conversation matters

  Great minds think alike, and fools seldom differ." implies that consensus is often the result of a coincidence or luck. If you look at the success rate of presentations, you might actually think that this is shear luck. So why is it you...

Giorgio Sironi07/20/11
0 replies

Practical PHP Refactoring: Extract Class

Sometimes there is too much logic to deal with in a single class. You tried extracting methods, but they are so many that the design is still complex to understand.The next step in the refactoring quest is Extract Class, the creation of a new class whose...

Jay Fields07/20/11
5 replies

Individuals Over People

I've been pondering a few different ideas lately that all center around a common theme: to be maximally effective you need to identify and allow people to focus on their strengths.

Michael Sahota07/19/11
1 replies

Exploring Agile Community Challenges through StrategicPlay® with Lego®

Last weekend, a group of local Agilistas got together for BBQ, drink, and to play with Lego. Well, not just play, but StrategicPlay® – with a purpose. And wow, what a result! The outcome was some deep insights into the Agile community that we’d like to...

Esther Derby 07/19/11
2 replies

Misconceptions about Self-Organizing Teams

At a recent conference, I over-heard three managers talking about self-organizing teams. “You can’t just turn people loose and let a team make all the decisions. They’ll mess things up. And with all these ScrumMasters, coaches, and self-organizing...

James Betteley07/19/11
0 replies

Continuous Delivery in Practice

A couple of months ago I was fortunate enough to be invited to the Thoughtworks live 2011 event in London. The main topics of this event were agile (as you’d expect from Thoughtworks) and Continuous Delivery.

Paul Stack07/19/11
1 replies

Development Key Skills (or lack of them!)

This post is highly subjective and denotes the skills that I think a developer should have in his/her tool belt by default.

Dave Rooney07/18/11
0 replies

The Power of Whining and the Evolution of Agile

It's somewhat amazing to think about the power of whining ("whinging" to those across the pond and in Oz & NZ!).  Back in February, I received a "Dear Dave" letter from the Agile 2011 conference saying that my "Survival...

Ashod Nakashian07/18/11
1 replies

Working Too Hard

Some of us have to work a good 16 hours a day, or more. Some split this time between school and job, multiple jobs, job and hobby project or spend it on their one-and-only job or startup. After a while, waking up becomes a struggle. Disoriented, exhausted...

Caleb Jenkins07/18/11
1 replies

Taming the Legacy Code Beast

This weekend I spoke at the Big Design Conference 2011 in Dallas. If you’ve never been to the Big Design Conference – I highly recommend it!

Dror Helper07/18/11
1 replies

How to return default(Type) in runtime – a TDD example in four unit tests

I’ve found this question while going over my old StackOverflow answers:I'm using reflection to loop through a Type's properties and set certain types to their default. Now, I could do a switch on the type and set the default(Type) explicitly, but I'd...

Giorgio Sironi07/18/11
0 replies

Practical PHP Refactoring: Move Field

Object-oriented programming is based on the encapsulation of state and behavior associated with that state in decoupled items called objects. In the previous issue of this series, we saw how to move behavior to match existing state, while today we'll see the...

Martin Fowler07/17/11
0 replies

Command Query Responsibility Segregation

CQRS stands for Command Query Responsibility Segregation. It's a pattern that I first heard described by Greg Young. At its heart is a simple notion that you can use a different model to update information than the model you use to read information....