Me(di)tating

During the last few weeks I did a bunch of me(di)tation. This is, at least in part, a result of reading Andy Hunt’s book Pragmatic Thinking & Learning. Metation is a neologism that came to my mind when writing this post and it means doing meta things. When the things you are metaing are thinking and learning, i.e. thinking about thinking and learning about learning, this tends to leave you in a meditative mood, so the pun is not that far-fetched after all.

Right now there are many things I would like to learn. I got the feeling that maybe I even wanted to learn a little too much at a time. Furthermore I noticed that there are things on the list of things I would like to learn that I can’t tell what exactly I want to learn them for. Fortunately, there is a chapter about SMART objectives in the book mentioned above.

There are multiple words you can expand each letter to. The ones in the book are Specific, Measurable, Achievable, Relevant and Time-Boxed. SMART objectives force you to give answers to five questions about any learning endeavour you are about to begin. In doing so, something as vague as ‘I want to learn skill X’ is transformed into the more specific ‘I want to reach the Y level of skill X in order to complete taks Z. My first steps to get there are a, b and c.’

I defined my first set of goals a few days ago when I had to kill some hours on the train. This is highly experimental and it would be too embarrassing if I published these here right now and then don’t achieve any. If the results are satisfying, I might blog about it later, though.

The last section I read was about a technique called SQ3R, which stands for Survey, Question, Read, Recite and Review. Instead of just picking a book and reading it, you are supposed to take a more sustainable approach. Scan the TOC and headings first, collect a list of questions you want yourself to be able to answer after having read the book. Then start reading and take notes along the way. When you are done, don’t just put it back into the shelf. Discuss the contents with friends or co-workers. Get deeper into it by teaching it to someone else.

I am just a little further than halfway through the book and I have already had so many light bulb moments that I felt that this book was targeted at me specifically more than once. On the other hand, there are almost too many good ideas and I honstely don’t know which of these techniques will outlive the experimental stage. Some do indeed sound very promising or at least interesting. But the single most astonishing piece of wisdom I got out of this book is the first one of the tips that just reads

Always consider the context

I greatly appreciate this one for two reasons. Firstly, because it is so true, and secondly, because it is so meta.

O du schöner Westerwald

That’s where I come from. And that’s where we are going.
In April the majority of jovoto’s technical staff will spend a week in the lovely countryside in which I grew up. We take the chance of escaping the office in order to work highly focussed on a specific task in an inspiring environment. As this [...]

it’s getting hot! treetonin now with node temperature

I just added a feature to treetonin and it’s called node temperature. It is inspired by the PageTemperature plugin for the Kwiki wiki. About a year ago I was about to start a private project with two co-workers. We had some good ideas but not enough time to finally get it going.
While setting up the [...]

treetonin and scriptextual

As announced in the last post, I published treetonin as a replacement for Jreepad. During the last few weeks most of the time I was taking notes, it were just time tracking notes. I tried several time tracking tools over the years and I think time tracking, as it is somewhat of a meta task, [...]

treetonin

I read Eric S. Raymonds book The Cathedral and the Bazaar about a year ago. In this book he seeds bits of wisdom as lessons. I found most of these lessons interesting, clever, amusing when reading the book, but I don’t really remember them. With one exception, and that’s the very first one.
1. Every good [...]

I just received a patch. It fixes one bug that was a terrible pain in the ass for quite some time, so I applied it immediately. I just had to adapt some tests. Here’s what’s new.
< me.student.should == true
< me.degree.should be_nil

> me.student.should == false
> me.degree.should == Factory.build :degree, :title => ‘Diplom-Informatiker’
> me.degree.should be_equivalent_to Factory.build :degree, [...]

take your gitconfig to your pair mate

Drum roll, please. This is the third post about pair programming in a row.
On my own box I use mostly TextMate, while my pair mate Tim prefers vi, so there’s no point in taking settings from one environment to the other. By contrast, we both use git directly from the shell, without any wrapping GUI [...]

double shot pair programming considered harmful

Even the greatest ideas have aspects that are not that shiny. In my last post I reported with excitement about my first experiences with double shot pair programming, that is pair programming with an own keyboard for each developer. Now I discovered a side effect of this technique that is so dangerous that I just [...]

double shot pair programming

This crappy image shows the work environment we now used for the second day. Pair programming, double shot flavor. Two developers, one machine, but two keyboard attached.
I started this as a hoax more or less, since I don’t like my pair partners’s ultra-flat Apple keyboard and he kind of doesn’t appreciate my obviously superior Das [...]

A workflow proposal for I18n with Git and a non-developer

A few weeks ago we migrated jovoto from Gettext to the new I18n that became available with Rails 2.2.
In the Gettext approach we had the following workflow for collaboration with a translator.

Add code with new/updated calls to Gettext’s translation methods
Run rake gettext:updatepo to pull new English strings into the po file
Put po file on a [...]