The next release of ScalaTest will offer a unified API for table- and generator-driven property checks. This blog post gives a preview.

Despite being part of the microcomputer revolution from the beginning, the Kindle is the first piece of technology I've seen that feels alien to me. And I mean that in a good way.

Chris Wysopal likens application security debt to technical debt in a couple of recent blog posts. It turns out that the debt metaphor is particularly apt as, like financial debt, application security debt is susceptible to interest rate fluctuations.

I've posted my summary of the Java Posse Roundup 2011 from last week. We're also having a workshop event in Crested Butte July 25-29 on Scala, Flex and Design.

There's been a lot of talk lately about a decision by the community to fork the Hudson continuous integration project, but the real fork has been done by Oracle, not the community.

Feb 14-16, IBM's "Watson" is going to be playing Jeopardy.

Registrations are now open for the upcoming Java Posse Roundup, which will be held in my beautiful mountain town of Crested Butte, Colorado during the height of ski season.

Complexity entails completeness! The software industry should admire and support a holistic approach to software engineering. Unfortunately, the industry does not herald a holistic viewpoint, since the software industry has a wrong treatment of complexity. This has to be changed!

A follow-up to my previous piece on Facebook.

This is another article that originated on my Reinventing-Business blog but might also be interesting here.

Progress happens, and it's not Java for me anymore. I'm hoping this Gosu thing is.

Transition to Scala 2.8 and Lift 2.1 turned the usual beginner trails impenetrable. It took me more than a week to figure out how to start with Lift on IntelliJ if you use Scala 2.8. Here's my experience.

While Scala can work with Java collections, and Java, more or less, can work with Scala collections, for sanity sake they better should be kept separate. So how do Java and Scala code exchange collections?

Yesterday, after four years of vacillation and procrastination and occasional modification, I finally got the preface of my next book, Breaking Up The Monolith: Advanced C++ Design Without Compromise, into a form with which I'm happy. Eight pages in four years; at that rate the full book will take me 150 years!

I'm not sure what's worse here: the fact that some of my data is going to go away, or the fact that I found this out almost by accident. Someone is going to get burned by this.