The August issue of the Java Performance Newsletter was published

I'll probably never blog from a conference, since sometimes the true impact of news takes a while to assess. Besides which, sometimes there are other priorities, even when you're at a conference. And then there are other costs ...

The industry needs refactoring tools for C++. Now.

Get more bang for your buck with multi-platform application development, but be prepared to work for it, even in Java.

I just got a phone call from a perfectly nice woman who proceeded to ask me about my company's IT needs. While on the surface this could have been any number of solicitation calls that I get on a regular basis; this one really struck a nerve from the get-go.

Some thoughts about knowing, learning, and software design, many of which were thought or written down while watching baseball.

There is a new java site that should make your user's Java installation experience a joy and a snap.

What is the difference between knowing how to use a profiler and knowing how to tune an app? At least $10,000.

The more I practice taiji, the more I notice three seemingly contradictory things. First, I keep discovering subtle details that I hadn't previously seen. Second, it keeps getting simpler. Third, it never gets easier: our teacher, who has been doing it for twenty-five years, sweats just as much as the old fat guy who wears my outfit.

In the month of July, Artima.com for the first time served over one million pages. I want to thank the approximately 188,000 people who visited last month.

Ever download a framework and feel overwhelmed? Maybe there is a way around that.

Be careful not to confuse the map with the territory. Presentation and representation are different concepts for different purposes. The everyday notation for many quantities, such as money or time of day, is not necessarily a good indicator of how they should best be represented in a program.

The JavaPerformanceTuning.com July newsletter was published

Guerrilla Development is software development in an environment unsupportive of the effort. In my first few essays I discussed some of the problems software departments might have in their interactions with the rest of the company. In this one, I talk a bit about UML and my concerns for its future.

Becoming a boss doesn't make us smarter, nor is it a license to use our power unwisely. We need to listen to our folks, and let them act on their own, sometimes even when they're wrong.