Skip to main content

A Hard Day's Workshop

I want to tell you about how we introduced one of our more recent practices: Workshops.

During one of our retrospectives this spring, it became apparent that some of our colleagues felt that there was room for more learning in our shop. People were sticking a bit too much to their usual tasks and their usual technologies. We're not a consultancy, so it's not really the core of our mission to use the latest and most hyped tools all the time. We still need to stay updated so we make the right architectural choices when considering doing something the old way, or trying out something new.

But we're too busy to learn new stuff!
For a software developer, the responsibility for your actions is split between what you choose to do, and what you're assigned to do. Of course, you can't run wild and smash all the latest open source tools and languages into the main product line, but at the same time, if you don't take initiative to do a little research on what's going out there, it's very unlikely that you will get any new interesting technologies to work with.

I believe that this research is something we have to spend some of our free-time on.  Many developers will disagree with me here, saying that work stuff is for working hours. Unfortunately, I only get 40 hours of office time a week, and this is not enough for being productive at work plus research. (There are a lot of things I want to keep up with for the sake of an interesting career in technology.)

Pick a card, any card
Now, for the purpose of this post, it's not really important which technology we set out to learn. Anyhow, The Pragmatic Programmer says you should learn a new programming language every year. Personally, I've long wanted to learn Scala, and use it for a pet project, either at work or at home. I see a lot of Norwegian tweeters are experimenting heavily with it, as well as a couple of my colleagues, and they're all boasting endlessly about how great it is to program with.

Seek allies
So, I asked three of my Scala-digging colleagues if they would be interested in us arranging a series of internal workshops for our colleagues, to further our own understanding of Scala (I had none at that point) as well as teach the rest something new. They were in. Being four people taking care to arrange the stuff is a lot more powerful and long-term than driving something like this on your own.

Blessing from above
After we had our new technology ready, and a team of people ready to push it, we went to the boss and explained: This is something we are going to do on our free time, but we want to know to what extent you'll be willing to "sponsor" the event. Obviously, us spending our free time on teaching and learning new stuff is something that will benefit the company, given a relevant technology at least. So we asked:
  1. Can we use the offices? (Usually this is a no-brainer)
  2. Will you buy us pizza? (Amazingly cheap compared to paying overtime, or using working hours)
  3. Can we dip into the regular working hours? (say, we start the workshops one hour before end-of-work-day, once a week)
Interestingly, in these situations you meet a compromise which reflects how much your company is willing to spend on learning, which is an important factor in your choice of place of work. This is something your boss/company should have in mind when they answer questions like this. A little extortion never hurt anyone :)

Now, with clearance from above, the four of us got together and planned out the workshops. To minimize preparation work, we borrowed the Scala introduction course from the Norwegian scalaBin organization. We came up with a pet project we could aim to create (an internal problem database, a bit like, and pulled out an agenda where we'd do a 2-hour workshop every second Wednesday. We're now done with the 3rd of these workshops, and it's going well. About two thirds of our colleagues are participating, and I think it's safe to say we've learned a lot already, without intruding too much on private time, and not taking too much time away from regular work activities.

I hope that even after we have mastered Scala, we'll continue these workshops for other things, handing over the responsibility to other colleagues who wish to arrange workshops in new fields. From management side, I hope they will see some business benefit in allowing more of these activities, and let it protrude further into working hours.

It didn't have to be Scala. It could've equally well be any other language, framework or tool. The point is to expand our skill set and knowledge, using our own time and company resources.

Just as you have to fight for your infrastructure, you have to take responsibility for your business using the right technologies, and spending enough effort on learning. I hope that the above experience can perhaps help you getting something started in your own shop.

PS: This is not the only knowledge activity we have at IP Labs. We also have an hour every Friday morning that we use for presentations, videos and retrospectives. I think the more interactive workshops compliment these knowledge meetings nicely.


  1. Anonymous1/6/10 18:45

    There are not many companies blessed with employees that truly make an effort in making things better, even when they have to fight for it. Kudos!

    A comment on learning: If you're not willing to invest in yourself, why should the company do it?

    On the perhaps more extreme side, 40% of the time should be spent on studying and improving yourself. Too much time is spent making bad software with worse technology and products. Oh well, I won't get too much support on this one I guess :)


Post a Comment

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Considerations for JavaScript in Modern (2013) Java/Maven Projects

Disclaimer: I'm a Java developer, not a JavaScript developer. This is just what I've picked up the last years plus a little research the last days. It's just a snapshot of my current knowledge and opinions on the day of writing, apt to change over the next weeks/months. We've gone all modern in our web applications, doing MVC on the client side with AngularJS or Ember , building single-page webapps with REST backends. But how are we managing the growing amount of JavaScript in our application? Yeoman 's logo (not necessarily the conclusion of this blog post) You ain't in Kansas anymore So far we've just been doing half-random stuff. We download some version of a library and throw it into our src/main/webapp/js/lib , or we use it from a CDN , which may be down or unreachable when we want to use the application.. Some times the JS is minified, other times it's not. Some times we name the file with version number, other times without. Some

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration