You are currently browsing the tag archive for the ‘software development’ tag.

Interesting post on how is made: as to me is a great product, reliable, adding continuously new (and RIGHT!) features and free :), I think it’s valuable to understand how is made!

The post How is made answers to these questions:

  • Where are we?
  • How do we work?
  • How are new features and improvements made?

Read the post and .. what about answering, here in the comments, to these questions for YOUR organization?


Here is what Martin Fowler writes in his post TradableQualityHypothesis:

I follow Kent Beck in making a distinction between internal and external quality. The pleasantness and effectiveness of a user-interface is external quality as it’s something that can be perceived by the users of a system. That is something that can be sensibly involved in a trade off – do I want extra work on making feature A easier to use or should I add feature B?

The internal structure of the software, however, is not something that’s directly perceivable by the user. I can’t tell from using a program whether its internals are constructed well or not. Internal quality is thus a more hidden attribute. When someone says we should do things reduce the design quality of a system to build more features, that person is applying the tradable quality hypothesis to internal quality.

Hidden in this reasoning there is the equation that lowering quality you can go faster: as Martin says this  is true only in a really really short time frame but this is not the worst effect:

But the tragedy is that as soon as you frame internal quality as tradable, you’ve lost. […] Instead it’s vital to focus on the true value of internal quality – that it’s the enabler to speed. The purpose of internal quality is to go faster.

What’s your experience on this topic? How’s the “quality tradable hypothesis” is seen in your team? Under which circumstances high quality means going faster?


Courtesy of notsogoodphotography, Some Rights Reserved

People do not get called out for introducing bugs. They only get called out if they ask for changes to go out with the release but aren’t around to support them in case something goes wrong (and haven’t found someone to cover for you).

That’s one of the things that got me while reading How Facebook Ships Code « FrameThink – Frameworks for Thinking People

Don’t want to evaluate the sentence from a QA point of view or SW Dev process point, I just want to underline the accepted  responsibility that’s behind that.

What do you think?


(Courtesy of  rainbowbreeze)

Courtesy of
Matt from London

How many time have you heard this sentence “yes we did that small stuff but don’t worry: nothing changed”?

It can be a tiny technical modification to a system, it can be a small organizational change, it can be something that you said to your team, it can be a change in a signature of your email … it doesn’t matter.

When it’s about complex systems any modification no matter its size, no matter where you make it, no matter when you make it, can have an unpredictable impact on any part of the system: that’s basically the definition of complex system.

And I tell you a secret: a group of people that have a relationship IS a complex system (family, office), IT stuff IS a complex system, SW IS a complex system, YOU are a complex system.

So please don’t tell me that nothing changed when you changed something!!!
And remember that this effect has also its good side:

No situation is ever hopeless. Because whatever the situation may be, the moment you start to take action, you change it (Ralph Marsdon)


p.s. By the way, note that complexity is often overrated especially in SW dev 🙂

I’ve just read a very interesting post by Ron Jeffries called Quality vs Speed? I Don’t Think So!.

Among others good ideas, I’ve been caught by this picture:

and this quote:

If slacking on quality makes us go faster, it is clear evidence that there is room to improve our ability to deliver quality rapidly.

GO, read the post and let me know what you think!


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 2,737 other followers

Connect with PieG

Certified Scrum Master

Map of Visitors

Anobii – my bookshelf

Here is (part) of my bookshelf and my wish list

Flickr Photos


%d bloggers like this: