Rants and Ruminations 15 to 21 of 149 articles InfoSyndicate: full/short
Continuous test runs   14 Dec 05
[print link all ]
Yesterday in Mechelen, at the pair programming party, Rob westgeest and I tried out a different way of running tests often. We were working on a  mini-feature in Hourensou We had been having some trouble with the tests before. We were using a freshly installed machine, with only a couple of simple text editors (scite and gedit) present. We wanted to run the tests often. However, I dislike having to switch from window to window all the time (in this case, switching from an editor window to a terminal window with the tests).

Therefore, we tried something simple: run all the tests in a loop, continuously. That way, if we saved, we only had to wait a little while for the tests to run of their own accord. The loop was written in bash shell script, so we get a fresh ruby interpreter each time the tests are run (the alternative was to use irb, the interactive ruby interpreter with a loop around a bunch of 'require' statements). We used 'nice' to make the tests run at a lower priority than our other processes. The tests are contained (in this case) in all.rb:
while true; do nice ruby all.rb ; done
Having the tests run all the time had an interesting effect. We were even more motivated than usual to make all the tests run, and errors were spotted quickly - just sit back for a moment, relax, and watch the testsrun. Reading the failure messages was a bit more difficult though; as the tests keep on running the results keep scrolling upwards.

I don't know a simple way (yet) how to run tests only if files are modified. Possibly a rakefile could work, but that's already a lot more work than the one line of bash script we came up with as the simplest thing that could possibly work.

Not Quite XP (yet) haiku   08 Dec 05
[print link all ]

A customer passes by

screaming

Storycards rustle on the wall

(inspired by Daily Scrum Haiku posted by Simon Baker ).

Pictures from XP Days London 2005   06 Dec 05
[print link all ]

So, finally, here are my pictures from XP Days London last week. There’s quite a bunch, this time they are grouped by session. I’ll select one from each as a taster.

three people in a cab

`Five People in a cab

staring at red lights

A haiku on the table`

Pictures from the eXtreme Tuesday Club

Marko van der Puil, Ivan Moore and Andy Pols watching closely from a distance

`Lego is so cool`

Pictures from the agile architecture workshop

people laughing

`Subverting metrics is fun`

dark Pictures from the Do you get what you measure? workshop

four people looking at the subway map

`The map is not the terrain`

people in subway

`it really isn’t`

Dead fish, and other miscellaneous pictures

One minute presentations @ XP Days Benelux   05 Dec 05
[print link all ]

I found a blog entry by Cedric Girard in French, about xp days Benelux. It’s cool. I hope you can read french, because some of his appreciations are untranslatable.

Cedric writes about how he found the values of Communication, Simplicity and Courage in the way the conference participants gave one-minute presentations on sessions they attended, at the end of the conference. Honest, direct and simple, as he puts it.

We had scheduled one-minute presentations by session organisers on both mornings (Cedric uses the word ‘conferencier’, which means comedian in dutch – several of the presentations were hilarious). The intention was to give participants a more accurate feel for the sessions than a piece of paper or a title can possibly give.

Marko van der Puil showing how not to complain effectively

Then, at the bar on Thursday, someone suggested to Vera participants do the same. We decided (courage!) to give it a try. The one minute presentations by participants were as funny as those by presenters, and we got a feel for those sessions we wished we’d attended.

I’m curious who suggested it by the way, as the suggesters’ identity has disappeared in the fog of excellent conversation and drinks apparently ;-).

I measure a decent conference program by the difficulty one has to choose a session – in each timeslot there should be at least two sessions that you really want to attend. Judging from the participants’ presentations and the reactions to them, we succeeded :-).

Drift Table Photos   04 Dec 05
[print link all ]

In “the previous entry”, I was complaining that I couldn’t find a paper or photo’s of the drift table. Simon Baker informs me this blog entry by Andy Pols has some photo’s of the drift table.

Andy also provides a reference to a paper that is readily downloadable: The drift table, designing for ludic engagement .

Man bent over the drift table, statueette and a desk calculator used as weights

a look through the lens, showing trees and houses in a crystal ball like fashion

Images courtesy of www.interaction.rca.ac.uk/equator/steve_drift_table.html

And, like Andy, I want one!

Recovering from several XP Days :-)   04 Dec 05
[print link all ]

Well, XP Days London was Fun again. I’ve had a peek at the many photos I took, I’ll publish them later this week, as Rob and I are currently busy preparing the next eXperience Agile course.

In the meantime, I recommend what some other writings on sessions I went to.

I normally have a funny feeling with keynote sessions. I’ve become so accustomed to interactive sessions, that I find sitting for an hour at a time, watching the slides go by to be a bit boring. Unless the presentation is really engaging. William Gaver ‘s presentation on Ludic Design was such a presentation. Unfortunately, I can’t find the videos he used (made by a documentary filmmaker) online. These videos showed very effectively how the drift table (a coffee table with a lense in the middle that lets you drift over the english country side as if you were in a hot air balloon) and another device were used in different ways than the designers anticipated.

It resonates with something I’ve observed from practice quite a bit – people will use your system in ways you’ve never expected. I prefer to be creative with it, and see what we can learn. Others seem to prefer saying `Bad User! This is not the way the system was intended!`…

rant
(Unfortunately, the papers on the drift table (probably written on British taxpayers’ money) seem to be locked behind ACM’s Portal, you have to be a member to access it… Don’t you just love how academic publishing works… ).
/rant

Plugging on hospitality to websites   03 Dec 05
[print link all ]
Dave Pollard writes about atomization of software  by using peer produced software consisting of small building blocks. This is a story about how changing only four lines in a template, can make people feel much more welcome in editing a website. I don't want websites and their 'back ends' to be merely usable, I want them to be hospitable (or with a reference to Christopher Alexander, habitable). I've been using Wiki2Go produced by my peer Pascal van Cauwenberghe. (by the way 'toffe peer' means cool dude in dutch ). It already has a plugin interface on the server side, allowing us to plug in graphs with very little effort. Something that has been bugging me about wikis was what I once considered a feature.

To me, a couple of years ago wikis attracted me for those two main features:
  • Easy associative, serendipitous linking by using WikiWords (use a word with several capitals, and it becomes a link. If the corresponding page doesn't exist yet, you can click on the ? link that appears after the word to create it).
  • Easier text formatting than plain html (e.g. by using a * to make a bullet).
With the growing number of wiki implementations that each seem to have their own preference for text formatting, the second one became less and less important. Actually, all those different text formatting engines became annoying. I even developed a prefence for writing in html directly, as that is at least standardized.

I have ranted before about how content management systems can get in the way of my writing process. These days I get to work more often with casual users, for whom the venerable 'blank text box' is threatening. You can see a 'traditional wiki edit screen' in this screenshot (taken from systemsthinking.net which I co-host):
 image of traditional wiki edit screen, text box in the middle

Notice the subtle finger lifting at the text in the bottom ("if you edit, please remember to do it in GoodStyle"), making the bar for a passer-by to edit even higher.

I was ranting to Ira Weinstein about the lack of hospitality in editing websites. He pointed me to fck editor (I find the name a bit dumb, but who am I). Basically, it looks like a regular word processor inside your html place. I was so intrigued by this, that I had to do an experiment with it. Rob Westgeest and I spent half an hour on a spike to add it to an existing wiki. That was enough. It worked. Five different lines in the 'edit' template of a wiki, and adding an fckeditor directory on the webserver and that was it. We spent another half an hour trying out the various features, going 'this is cool, and this, and this...'.

The following is a screenshot from the private wiki on satirworkshops.com, one of several new sites I'm building. I am working with Marc Evers on a handout for the Balancing Act workshop:


image of wiki edit screen with fck editor, with word-processor like toolbar on top, text hardly distinguishable from view

(the Satir Change Model picture and the site layout in this screenshot are provided by Nynke Fokma.)
Notice the three rows of icons on the top of the edit box. The 'page title' box and the 'save' and 'undo changes' buttons are the same as in the previous screenshot. Otherwise, the page is pretty much shown as it appears when you're not editing it:


image of wiki view of the same page, only the toolbar and save/undo changes buttons are missing

I find editing a wiki page like this much more comfortable. I often used to click 'save' every couple of seconds to see if I formatted bullets correctly, or if the links looked as expected. Now I can keep on typing and adding images, and I save when I'm done, or when Marc wants to take over the keyboard.

What I like most:
  • WikiLinks still work.
  • Pasting to and from OpenOffice (or the other word processor) works without visible differences.
  • I can see the images in the page while I am editing.
  • Text layout changes are instant and wysiwig.
  • I can still get at the html source if I want to, by clicking on the Source button (unfortunately still necessary, as most, but not all, formatting changes work from within the editor).
  • I only needed to modify an edit template to get started, no modifications to the core wiki software were necessary.
  • Look and feel, including keyboard combinations, is much like word processors, so the barrier for casual users to edit pages is much lowered.
Having all pages in html can make it fairly easy to convert existing websites to wikis. A small downside is that existing wikis also have to be converted, pages have to be html, rather than wiki formatting. I made a 40 line script for that in ruby that seems to do the trick, converting complete wikis at once. So now I'm converting the closed wiki's I'm having to see how stable it is. After that, some public wikis are likely to follow.

If you want to try it out, seedwiki hosts free wikis that use the same editor. The fck editor site also has a try out box. If you host wiki's yourself, I'd suggest you take half an hour to change an edit template and install the editor!

(I know this editor is 100% javascript. Some people who know me may say huh? Well, I changed my mind based on this. With effort, it is possible to make very useful things with javascript. I love 'voortschrijdend inzicht' ('advancing insight') :-) ).

Copyright © 2009 Willem van den Ende