Blogs about Jazz

Blogs >

Jazz Team Blog

2008 February

See you at EclipseCon 2008


It’s funny to say, but EclipseCon is much more than just about Eclipse the IDE. It’s about tools, platforms, runtimes, and grassroots hacking. Take Jazz as an example, where I would say the most important part of Eclipse we use is the OSGi runtime on the server. Whereas on the client side our design has […]

The Team Concert User Workshop: behind the scenes


Recently, the Jazz Jumpstart team published a Rational Team Concert User Workshop on Our small team of Paul, Steve, Philippe, and I work with Team Concert beta customers who are learning how to do serious work with this new platform. We developed the workshop to help these customers get up to speed on the […]

Refining the Jazz user interface

Tags: , , ,

Something I’ve learned in working as a user interface (UI) designer on an agile development team, as with the Jazz Project, is that you don’t so much prescribe design as you iterate on it. Ideally you first consider what the viable design options are, and having chosen the best known path, you start with a […]

A brief history of the Jazz Team Server interface: Our journey from a J2EE server towards a RESTful server

Tags: ,

I joined the Jazz project while it was still in its very early days, roughly two and a half years ago. At that time, the Raleigh team was just finishing up a short-lived experiment of trying to build an extensible platform using J2EE. This experiment demonstrated that the J2EE classloader hierarchy was not the right […]

Some notes on rhythm

I’ve been a software developer for about 14 years and been involved with too many projects where the schedules shifted and slipped – frustrating the developers and losing the interest of customers. So it was an epiphany to me several years ago to see the way the Eclipse project used “rhythm” to get great output […]

The Jazz metronome tool keeps us honest

From – How not to deploy an application over a WAN, “Although the medical appointment application was advertised as being client/server based, it wasn’t. In particular, the application was designed in such a way that the data in each field was sent character by character over the network. Hence, this was another example of […]