If you mean purely the process of typing in code, well--that's kind of hard to gauge, isn't it? I've always found that the trial-and-error of development processes means that unless you're working in an orthodox manner it's really hard to separate "thinking" from "doing". Also, I find that when you're in the "zone" it's not painful at all. Sounds like you may be working on something you don't enjoy so much? :D

I think what we're seeing here is IBM's attempt to dust off and leverage all that old work that went into the original OS/2 UI. GNOME and KDE have fought on different fronts but suffer from the usual issue which Open Source software faces: lack of unitary direction; and compelling featuresets. Final salvo in IBM's attempt to co-opt Linux's mindshare? You make the call! :D

i agree; and the real issue is getting systems in place that are non-intrusive. Things like email retention are great policy but run up against the myriad things people can do to remove or move them. Obviously, any email should be captured at the SMTP level. What stuck GP as odd is that in a very IT-centric operation, they state they have no policy: big company or no (and I agree with the slovenly and slapped together methods most work with) they are THE IT company. I imagine if this was not done it was again, via inertia rather than pure malice.

Of course by not having the emails, they have not done themselves well cos they cannot prove or disprove the allegation, and in the light of what this evidence provides it comes across a bit as "the dog ate my homework".

In sum: everyone knows a drunk is just gonna have one more. Sympathizing with it is another thing...