Skip to main content

Jazoon 2007: Last day

I didn't really get around to take any notes the last day. Or well, I did take some notes but I lost them.. Here's what I attended at least:
In the last talk, I asked the speaker whether he thought extensions of Java as a platform was a fair way of increasing complexity vs new languages better fit for the job (a more powerful platform does reduce the need for new components), with a particular regard to AOP and Closures. He answered that AspectJ in runtime would be considered a foreign component increasing complexity quite a bit, but closures would be more of a welcome addition to the language.

I asked the same question to Peter Sommerlad yesterday, and his answer was that he discussed this with Kiczales about this some ten years ago, and his belief was that the developers/tools weren't ready for it yet. We first have to master the art of OOP before we advance to AOP, but I'm not sure I agree. Alot of the GoF-patterns we use today are there because of restrictions in C++/Java, and maybe OO wouldn't be that much worse of having to be learned with AOP.. Just a thought.

(By the way, reason this post is done so many days after Jazoon is that we've been constantly occupied since, attending an internal AOP-workshop for the last two days straight. Thanks, Kaare! Great workshop.)

In the closing session/lightning talks I learned how to present the Semantic Web in 1 minute, some good books to read on python and management, and learned lots of other interesting facts that I have since forgotten.

To summarize my experiences of the first Jazoon:

Bad things:
  • Far from packed (700 people I think, was room for a bit more than that methinks)
  • Level of speakers were a bit up'n'down
  • Should've turned the lights in the theaters on during talks
  • The talks' slides (and hopefully video) aren't up yet
  • Zurich is *nearly* as expensive as Oslo. And pretty similar in every other aspect except the language :)
Good things about Jazoon:
  • Attracted a great score of central/south/eastern-European developers (where I predict great things will come from the next few years)
  • Organization was like clock-work
  • Wireless was constantly up
  • Lots of room :)
  • Power slots every other row in the theaters
Thanks to the Jazoon organizers. I really believe you have the infrastructure and organization to become a great conference in the future, perhaps already next year. So get your abstracts ready, folks :)

Oh, and as a side-note, my abstract didn't get accepted for JavaZone this year, so the material probably won't get any more "exposure" here in the blog, although I will continue implementing the pattern in my day-to-day work.

Comments

  1. Dear Thomas, thank you very much for your kind and helpful feedback. Jazoon'07 had just over 800 participants and yes, there was space for more. How did you like the venue? If the venue will be the same for next year then at least we have some spare capacity for more participants :)
    Prepare your abstract for Jazoon'08 now and get ready! Chris (christian.frei@keynode.biz, the organizer of Jazoon'07)

    ReplyDelete

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

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

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

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