So Where Is The Value?

In everything we do there should be some value – some importance in what we do.

If not then why do it?

looking

Without any worth, the thing that you’re doing becomes a chore or you can easily drift on to something else. So we need to see the value in what we’re doing.

However, as a team we don’t always see the value at the same time; depending on your point of view you will see the value at different stages. Continue reading →

If It Waddles Like a Duck – It Must Be A Duck?

The saying…

If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

implies that a person can identify an unknown subject by observing that subject’s habitual characteristics.  It is sometimes used to counter abstruse, or even valid, arguments that something is not what it appears to be. – Wikipediahttps://en.wikipedia.org/wiki/Duck_test

ducks.jpg

How about this..?

Continue reading →

Do Agile Development Teams Need Software Architects?

Agile allows us to commit at the last responsible moment, delivering value early and have self-organised teams.

So why have a role in a team which forces you to do upfront design on a system, when we don’t know all the requirements yet, let alone how we’re going to meet the requirements?

Continue reading →

Don’t Devalue The Learning Process

I first heard the phrase “Don’t devalue the learning process” on a podcast of either Hanselminutes, This Developer’s Life or .Net Rocks. The talk revolved around the way, in this industry, when we struggle to resolve issues, we battle through, attempt new things and then when we find the solution go “Oh, it was that. Of course. Right what’s next?” The two feelings don’t balance out each other; the effort we put in to resolving the issue isn’t matched with the equivalent feeling when we find the solution.

Jumping for Joy

Jumping for Joy

Continue reading →