Long ago, back when green screens and green-bar paper roamed across the software
development landscape, I was a young software developer at a startup software company.
There was a development group that I worked with that held periodic
code reviews. These were conducted as lengthy meetings with the entire team
gathered around a conference room table.
If you ever get the chance to go to Oslo, don't pass it up. It's a beautiful city filled with friendly people. And don't worry if you don't speak Norwegian - almost everyone I encountered spoke perfect English, which is good since jeg snakker bare litt norsk.
I was in Oslo last week to attend JavaZone 2006, which was very worthwhile.
Today was day zero of JavaZone 2006 -
there were some all-day courses but I did not arrive early
enough to take part. The official conference starts tomorrow.
I have always thought that profilers are just debuggers with a different name. Case in
point: in a debugger I can watch the logic of my program change things like
the value of a variable. Similarly, one of the things I can watch in a profiler is how my program
uses memory. For example, I can see the number of instances of a particular class
that have been created.
A couple of weeks ago I was busy getting ready to attend JBoss World.
in a hurry trying to install the latest build
of version 5.5 of the