When I had the manager of useless that was driving me insane with his inept procedures I eventually flipped and spoke to the company boss. Turned out I was late to the party and pretty much most of the workforce had been complaining.
I backed it up with concrete examples of good procedures that had been replaced with mad time consuming ones (all updating a shared file on a filestore via phoning around to "lock" files verbally was the one that finally made me lose the plot). He was gone the next day.

Question is why are the team working for him not shouting about it if he is that bad? Are they all bad or is in fact the problem further up the chain?

Something suggests this is more than just a bad manager problem and if the poster can't identify conclusively why this manager is bad then he isn't looking hard enough or in the right places. Talk to this manager and his team - not the slashdot community. Then come back with more info if necessary.

Just to give a perspective on these new fangled technologies you speak of. I used it on a unix workstation to store my c code at uni 20 years ago - I never assumed either were new then. The 2nd year had a series of lectures devoted to concurrency.

I've had new graduates lecture me "we should use x" then be surprised when not only am I aware of it but know more about it than they do. I want to use new stuff but only where appropriate. Hell its more fun learning/using something new. (well unless it's the metro interface ofc).

Reading the patent it has a bit of blurb about how it overcomes some issues with the prior art. Patents are evil yes - and I can understand the annoyance but I fail to see how you or anyone could possibly be sued using heapcheck via a patent that lists heapcheck as a reference. You could just list the patent as evidence of your prior work which it acknowledges! The patent states it was submitted in 2005, it also lists your work with a date of 2002. I don't see how they could possibly sue.

Now if heapcheck was expanded to cover the alleged new/alternate methods the patent claims to address things could get more messy.

(insert not a lawyer, in my opinion, multiple legal disclaimers here).

Spot on. The American TV industry seems broken. Advertising rates have plummeted anyway (peak back in the 80s?). A huge chunk of profit must come from dvd sales yet the whole basis of what lives and dies is still on percentage audience share, demographic nonsense to do with advert sales etc. A significant factor seems to be which idiot in charge this month decides to interfere with content/scheduling/time slots etc.

We are looking at a future where download or streaming will replace dvd+broadcast+cable, yet the industry still doesn't seem to have caught up with the previous shift to dvd with their decision making. I want ad free television and I'm happy to pay for it, but no I won't fill in surveys or trust the king of adverts google to move tv forward in an acceptable manner.

Basically I'm still bitter about Firefly being cancelled. It will pass in a few decades.

ire?

Google advertised their own motto. They seem to forget it. Ironic.
The people who don't pirate tv get punished - intrusive adverts, or dvds with a mountain of junk it may or may not let you skip past.
Don't get me started on region encoding nonsense.

I just want to be able to legally buy a tv show without adverts+drm that breaks or reliance on my net connection being up. Why is that so difficult? Just buy it and have it delivered or downloaded so I can use as I want.
Why am I in the stupid situation where I buy dvds(I like to support the makers maybe I shouldn't) + have to download the same content to watch it how I want. It is insane.

So yes ire.

I seem to recall osx or to be more precise hfs auto defragments a file when it is loaded. ie it loads a file then says "oooh messy" and writes it back in the background.
So the file second invisible write happens after the initial write time and in fact after a subsequent read time operation.

I wonder if osx is just doing things when it isn't being measured and files are constantly moving to spare gaps as a result.

(Someone must know more about hfs than my fuzzy memory to verify/refute this theory).