Someday, I’ll get back to using Qt in my professional existance. That and the iPhone. Anyway, webkit looks like a great addition.
What’s New in Qt?

Incorporate online content and services such as maps, music stores and instant messaging into your native applications. Qt now integrates with WebKit, the open source browser engine inside Apple’s Safari browser, the Apple iPhone and millions of Nokia smartphones. The integration allows developers to blend web and native content and functionality, create innovative user interfaces, and deliver a consistent, web-enriched user

In my work world, I use clearcase for doing version control. At NYSE, we used a flexible but complex model of several vobs for shared pieces, major branches for specific versions (.e.g. product.11), minor branches (product.11.03) and each developer creating one or more further branches as needed (product.11.03.4538). Lots of merging going on. It took a while to get used to but it works well.
At Credit Suisse, we have a much simpler model for clearcase where everyone creates a local branch off the main view and when they are ready just commits that. It freaks me out but it works.
On my personal projects, I’ve been evolving over the years. Many years ago, I
used RCS.
I thought CVS was a huge improvement over RCS. Then Subversion held sway over me up until
about a year ago when I started experimenting with more distributed version
control systems.
When I wanted to work with someone else, we both had laptops, were frequently
working without a network connection (commuting by train) and we were doing a
lot of experimental stuff. It made sense to use distributed version control. I
started off with Darcs. The concept is great;
everything works as expected. I had repositories under Linux, Windows, and
MacOS. Tres cool. Darcs got a little annoying with constantly prompting me if
I really wanted to included this. Sure, I used “-a” or answered “a” a lot
(accept all changes), but it was frustrating.
Recently, I decided to try Mercurial and I’m totally impressed. I’m not to far into my evaluation but the first few things work like I expect.

1. Creating a new repository and importing all the changes from darcs worked like a charm
2. Creating repositories on several machines via ssh works well.
3. Simple changes and updates is intuitive
4. Performance is great

More info

Here are some other articles

• This article compares performance of mercurial and bazzar (both are fast)
• Here’s a brief feature comparison
  between mercurial and darcs

Constructors should be simple, predictable, and never fail.

Simple

Keep your constructors simple in the sense that:

• Few parameters. Ever hear that a “function should do one thing and do it
  well”? It applies to constructors, too.
• Few overrides. Don’t try to get around the previous dictum by having a bunch
  of overrides on the constructors. It’s confusing for someone to understand
  the initial state if there are a bunch of initial states.
• Leave the work to public methods. If you think everything the constructor
  needs to be able to provide the ultimate configuration for an object you are
  trying to control (constrict) some developers too much.

Predictable

We write code like:

int  days = 13;

and don’t expect initialization to be doing very much work. Developers are used to that. Same with:

MyType val = new MyType(arg1, arg2);

should just be doing initialization comparable to assigning that integer. If
you want to have the constructor do a bunch of database work, factor that out
into a separate method:

val.LoadDB();

Many times people with constructor fever think have an underlying mindset that
thinks an object should be completely initialized and everything handled at the
constructor level. If you make every member function “const” then I’d believe
you. Otherwise, it’s just being a control freak.

Never fail

A constructor shouldn’t fail except under the most exceptional of circumstances
(out of memory). Examples of things that are not exceptional: a file doesn’t
exist, a network connection doesn’t succeed, input is poorly formatted, etc.

Interesting article about programming language popularity. This is the
“TIOBE Programming Community Index”
C++ down; python up; Java (boo) on top.