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!

SourceForge.NET's new File Release manager takes computing productivity back to the days of the punched card reader, and it does it with Web 2.0!

A couple of plugs, with no ulterior motive, and a mildly philosophical musing.

Just a heads up about three new libraries, and improvements in two established ones, ... (and a thinly veiled hint at some help from any members of the C++ community who have time, and a desire to work with highly efficient, highly robust libraries.)

Having the computer help you write and maintain your code is an essential facet of successful software development, and all good consultants will recommended that you follow suit. (Even if, sometimes, they forget to do so themselves ...)

Having spent nearly two years "getting everything sorted" ready to write my next book, I've decided enough is enough. It starts TODAY!

Two radically different philosophies to the management of software developers. Which one do you favour?

A few days ago I was in the office of one of my clients, talking to the dev guys about Pantheios (what else?!), and they were asking why I do open-source. The resulting discussion was quite illuminating, not least to me, so I thought it might be useful to discuss it here and see why other people do it.

After having spent the last 15 frustrating months of too-successful consulting that has stolen all my time for writing and most of my time for researching/open-source development, something's got to give! Is blogging the answer to my quandary?

Attempting to find a compromise between the constraints of a facade that wraps a system API, the limitations of a limited namespace naming scheme, and a user wanting more expressiveness, revealed an interesting compromise in design.

Looking for your best Fs, Fs, Fs, Fs and Fs regarding everyone's favourite (to use, or to moan about) language, C++. If you've got 'em, let me have 'em. The worst that can happen is you'll get a mention in the new book ...

After a prolongued hiatus from public writing activities (articles, blogs, books) throughout 2006, I'm about to stage a comeback. For those with nothing to do with the next 120 seconds, here's an explanation of why, and what you can expect in the coming months.

As a part of a recent discussion about strategy on The C++ Source within the Editorial Panel, I mooted my taxonomy of documentation, and claimed to be good at some aspects, and not others. This having raised eyebrows, I am keen to learn more of the wider world experience ...

Should individual human beings, and humanity's institutions, adopt the principles of contract programming, and use contract enforcement in their own functioning? Would that lead to a better world?

The new programming language, D, may not be reaDy for its 1.0 release just yet, but it's harD not to be impresseD by how proDuctive one can be in it. Here's a little tale of toDay's activities, as a taster for the uninitiateD.