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

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 operating on many repositories at the same time.

I discovere…

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities. It "was decided" that we'd be doing AES with a key-length of 256, and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet!

The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE in order to do 256 bits. It's a fascinating story, the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them.

Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password and sa…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Working in Teams over Working as Individuals

I recentlypostedthis sketch on Twitter:

Thanks to a few mighty retweets, it gathered a lot of views (9000 impressions, whatever that means). While that's fun and all, I still felt a bit sad that such an awfully simple insight can garner much more popularity than a thorough blog post that I put some hours into.

So, rather than let Twitter get away with this, I'll steal my own content back into the blog :)

The thread went like this:

Pondering how to battle individualism in companies. For some, it is counter-intuitive that teams can be more responsive, faster and even more accountable than single individuals.

Having "teams" in place is no guarantee that team work is happening. Be wary of too large teams, "I/me/mine", personal contact details instead of team point of contact. Good team is sailing crew, not galley slaves.

Beware heroes, go-to persons, calling in favors and other shadow handling of work. Real teams make the work explicit, both requests/needs and re…