The Great Confusicator (Obsfucator?) has spent a lot of time stumping for Tort Reform this week. His primary example has been firms hit by Asbestos lawsuits.
I wonder if this is because Halliburton subsidiary KBR ended up going into Chapter 11 fighting an Asbestos lawsuit? (More here and here)
Wonder why no one is talking about this…or does the Washington press corps have a short memory?
I stand corrected — CBS MarketWatch does mention Halliburton in an Asbestos story. Right at the very bottom.
Samantha and I hail from Victoria, BC, on Vancouver Island, the largest island off the Pacific Coast of North America. It is blessed with a mild mediterranean climate, year-round.
Apparently they are having a winter storm that has dumped more snow on the area than we have seen in Massachusetts this year.
Have fun!
Dan Gillmor mulls over the thought of whether the NY Times will charge for its online service.
My answer is: NO.
I am increasingly angered by newspapers that make their sites more and more irrelevant to me by hiding behind subscriptions and registrations. Do they need my marketing information?
If they will only make their online content available to subscribers, why have a dead-tree edition? Or vice-versa?
Online news is how the majority of my generation and younger get their information. Lead, follow, or get offline.
Jeremy has one final swing at the termination of his employment.
My take is that the response of HSC is very typical of any large firm who has been caught in a very public and almost untenable situation. And that they chose to discuss a personnel issue at all makes me see them in a very bad light. HR should know about the confidentiality rules in Canada.
The response of former employees also is typical of the response of full-time, politically-tenured employees to contractors in all organizations. I have seen this in almost all work cultures — "How dare he smear our company’s name; and he was just a contractor anyway".
Glad Jeremy has moved on; I will now drop the topic.
Added two new features to the GrabPERF system this morning.
These are attached to each individual test screen.
Have fun!
In this interview, Chris Anderson (of the Long Tail fame) speaks to Jeff Bezos of Amazon about that very topic.
I found a great example of a Heavy-Tailed Frequency distribution in my performance data today.
This clearly shows how data in the wild can be distributed in a non-normal fashion. In this case, there is a very heavy weight on the end of the tail, not simply a few straggling outliers.
It has become very unusual to find sites that exihibit this degree of heavy-tailed behaviour over the last year. When I started in this industry, this was more the norm than the exception.
A good read on evolving excellence through simplicity.
The concepts that apply in the manufacturing process also apply in Web performance. Simplicity makes Web performance excellence easier to achieve.
What does your Web performance process look like?
I am extremely steamed at an article that just read on Caillon’s Blog which basically encourages people to disable HTTP Pipelining.
This is the wrong approach.
If a server announces that it is HTTP/1.1 compliant, then it should be able to handle a browser that is using all of the HTTP/1.1 features. If someone is using a server version which cannot handle all of the features of HTTP/1.1, then they should be forced to fall back to HTTP/1.0.
By continuing to bow to the lowest common denominator, Web performance will not improve and Server developers will not be forced to accept that they must fix their code.
The only reason that server developers have gotten away with lousy pipelining support is because MSIE still does not support it. If MSIE begins to implement pipelining, then watch the mad scramble to resolve this issue.
Proactive Web performance excellence. Do it.
Copyright © 2025 Performance Zen
Theme by Anders Noren — Up ↑
