Skip to main content

My excuse for not blogging the last month

Recent activities eating away blog-activity include mostly JAFS - our annual internal weekend getaway. JAFS essentially means hauling our ~40 Java-programming colleagues off to a desolate hotel for a weekend, doing not so much else than having fun programming (and shooting some paintball).

The concept of the weekend's tasks are based on the following:
  1. Divide the gang into 5 groups
  2. Present some technologies that are core, meaning everyone of us should know by heart (for instance Spring and Maven)
  3. Present some new technologies that are hot, and might come in handy in the near future (for instance JRuby and OpenESB)
  4. Do some cool programming competition that makes use of above technologies
These points demand a mass of preperations. We've been 5 people spending evenings and weekends planning the event for the last month.

First we spent a whole load of time settling on which tehcnologies to focus on. See we've got four different camps of technology groups in Objectware, each of which are tugging in different directions, mainly core, web, integration and enterprise design & architecture. I like to believe we achieved doing a fair divide between the different camps, since these four camps are paying for the whole ordeal ;)

We also spent alot of time agreeing on the programming competition. Well, we actually settled on not doing a programming competition, instead focusing on cooperation between the 5 teams. Instead of having different teams compete over who could do the best implementation using different technologies (like we did last year), each team were to implement parts of a larger system which would cooperate using services across an ESB.

The system itself was sort of a collaboration suite framework, based on Subversion commits, Continous Integration and a robot. The ultimate functionality of the system: If you break the build, lil' Timmy here will come driving into your cubicle and steal your beer.



To be honest the solution will not be used directly, but the codebase does contain alot of good reference implementation of the various technologies we involved. We also got a good heap of discussions regarding among other things:
Oh, another thing we had to do in advance: we spent a whole lot of time implementing Proof-of-Concepts on each tecnhology to help the teams get started once they got up there. Now there was a learning experience :)

Aaand, the number one rule of bringing 40 programmers to a hotel: DO NOT TRUST THE NETWORK! Excactly. Even if the hotel has promised you full wireless, it ain't gonna work with 30 people who are trying to connect to the Maven repository, Subversion, etc etc.

So, we set up a mighty fine Ubuntu box with the following:
  • DHCP-service for allocating all the teams an address on our subnet (jafs.objectware.no)
  • DNS/bind for all the interal addresses on the domain
  • Subversion repo on svn.jafs.objectware.no
  • Continous Integration server on ci.jafs.objectware.no
  • Maven repositories on repo.jafs.objectware.no (snapshot-repo, release-repo and site-repo)
  • IRC server (of course!) on irc.jafs.objectware.no
And of course we brought along 40 TP-cables and a handful of switches to provide each contender with wired network.

Now it might seem like a bunch of uneccesary mumbo to setup all these wires, aliases and services, but believe me we all appreciated being able to just hook into a 100/1000-MBit network and be up and running. Zero network problems, I tell ye :)

So that was JAFS... Right after we were done I had to get ready for delivering my 10 minute lightning talk on Smidig 2007 (the Norwegian Agile-community's first conference). The conference was as impressive in implementation as was its lack of up-front planning (taking about two months to prepare, was it?).

The conference left me inspired and hungry for more. If I remember, the next post will be about distributed continous integration.

Comments

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

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 --

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

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 https://github.com/tfnico/config-mr.git 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

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