Bjørn Stabell 白熊

This is of course pretty controversial stuff, and in all honesty, Arlo only has his own data and the feedback of 6 teams that tried it as supporting evidence that it works. Of the 6 teams, all had productivity boosts. 4 teams continued, 2 stopped. The reasons why they stopped was interesting, though: they liked specializations, and were happy with slightly less productivity.

(more…)

The final practice Arlo described was team-owned tasks. Avoiding assigning tasks to people is very important to encourage team responsibility, which leads to team accountability, which is a necessary requisite to building strong self-organizing teams.

(more…)

Another question they had was:

• Who should do which tasks?

The normal approach is to put the most qualified implementor on a task. Naturally, that should ensure the task got done faster and better, right? Well, just to see how it worked, they once tried the exact opposite: putting the least qualified implementor on a task. Again, what they found was astonishing.

(more…)

Arlo’s team wanted to be extreme, and they started with one of the XP practices, pair programming. Going extreme meant that they would pair program all the time. No code produced by a single person was allowed to be checked into the repository.

But, pair programming is also a pretty new and relatively undefined practice. There were still a lot of questions open, among them:

• How long should each pairing session last?

  (more…)

The most interesting and eye-opening talks at EuroPython 2007 were probably Arlo Belshee’s talks on agile methodologies and his team’s experiments and results in that regard. The following blog posts summarizes what I learned from listening to his talks, doing his XP workshop, discussions with him, and digging up related information on the web (such as a paper and a podcast). I strongly believe this could be the next phase in how we develop software, and I hope I’ll be able to whet your aptetite for change as well

(more…)

Via Simon Willison’s blog, SlideShare has an impressive list of slideshows about web application scalability.

Enough is enough.

Say no to Microsoft OOXML becoming an ISO standard by signing this petition.

ODF is a completely free and perfectly viable format for such information. Despite Microsoft attempts at stating otherwise, it has already been proven to be able to store any information MS Office needs to store; there’s not even any reason for OOXML to exist. It’s such an obvious attempt at confusing the public; let’s show we’re not confused.

Some cool REST links I’ve come across lately:

• Implementing the DayTrader example application using a RESTful interface shows how even a bit more complex applications can use REST.
• ITC has a RESTful Web Services podcast where Jon Udell talks with Leonard Richardson and Sam Ruby about their new book. They even discuss some things like doing transactions with REST.

I have good luck with this trick on several Sony Ericssons (including W800i and now K800/K800i):

• edit ABDeviceCommandSets.plist in the /Applications/Address\ Book.app/Contents/Resources/Telephony.bundle/Contents/Resources/ directory with the editor of your choice
• find K700 and create an identical line underneath it, replacing K700 on the new line with your (hopefully compatible) model number; in my case I added two lines, one for K800 and one for K800i, just to be sure

Restart the AddressBook, and SMS away.

In early May 2007 something amazing happened. Hollywood’s most guarded secret, the key to decrypt HD-DVDs, was found and released on the Internet, via the site digg.com. At first Kevin Rose, the Digg founder, felt pressured by Hollywood lawyers to take down the key, but this made Digg users go completely ballistic, and in the end Kevin posted the code himself saying something to the sort of “this may be the end for us, but at least we went down fighting” (see original post). The key in hex, in case you wonder, is:

09-f9-11-02-9d-74-e3-5b-d8-41-56-c5-63-56-88-c0

Even the iphone didn’t generate this much attention, the blogsphere was flooded with reactions from the two factions: “digg surrenders to mob” and “the truth will not be silenced”. I’m afraid I, with most techies and new media people, belong with the last group that thinks DRM is the Next Big Evil.

People went out of their way to spread the code, to the point of creating songs. The first song wasn’t really that good, but then Geoff Smith created a song called “Digg the Code” that Cali Lewis of the GeekBrief.tv podcast put video on…. What can I say, it’s awesome:

There are currently more occurences of this “secret code” on the net than there are HD-DVD players in the world.