Skip to main content

JavaZone'08 coming up

I'm still going through my post-summer awakening, so I still haven't gotten the wheels of this blog running again. But current events are sort of relevant to the people I'm guessing are part of this blog's readership.

The biggest happening coming along is JavaZone 2008. Now this is especially important for me for two reasons. First reason:

I've been a part of the crew preparing the conference. My role has been gathering a crew of volunteers to help out with all the practical work during the conference. Hooray, very rewarding work, getting 40 people to work two days for virtually nothing!

Luckily there's a great crowd of Java-interested students in Oslo, and they can't afford a conference-ticket! So our evil schemes of acquiring a cheap workforce are proceeding as planned. Actually, there is a win-win relationship going on here. Student-organizations like to profile themselves in front of companies, cause companies have a tendency to give away free stuff when they do presentations at universities in order to recruit more newly educated computer scientists. Never underestimate the value of free food for a student.

Companies, however, are wondering "So how do we get to these students?" - when it comes to the University of Oslo, Institute of Informatics (the biggest contributor of volunteers to JavaZone), the answer is through events like dagen@ifi, and student organizations like ProsIT and Navet. You (recruiters) can meet members of these organizations at JavaZone. But try not to bother them while they're busy with the crucial tasks of keeping the conference running smoothly :)

We still need more volunteers, though, so if you know anyone who'll chip in some hours of work in exchange for some freebies and free attendance to the conference, send them over to the JavaZone volunteer sign-up page:

www.javazone.no/funk

Second reason: My proposal for JavaZone'08 talk got accepted! The title of it is "How I Learned to Love and Hate Web Testing", and that's pretty much what's it about as well. If you want more details you can read my last blog post on the subject. I haven't gotten to prepare the talk half as much as I've wanted, but I've got most of the content pretty clear up in my head.

I've started writing a manuscript for the entire talk. Now before you think "Stop it!" I won't print it and read it out loud when I do the talk. It's more like a movie script. I know too well that Norwegian audiences beyond a certain size are very hard to read, and therefore hard to adjust to, so I'm going to perform the talk exactly has I have planned it in advance. What I loose in adaptability I'll gain in stability and content. Or that's what I hope anyway. Comments on how to prepare for talks in front of big JavaZone audiences are appreciated.

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