Duckett and run

Tags

, , , , , , , , , , ,

In my Calgary Sun column Tuesday morning, I decried the attitude of Alberta Health Services president and CEO Stephen Duckett as he was being scrummed by reporters in Edmonton on Friday.
In short, he avoided media questions for three minutes, repeatedly saying he was too busy because he was eating a cookie. For the incredulous, here’s video via CTV Edmonton’s YouTube page, which has already been seen by more than 124,000 people as of Tuesday night:

This clip has spawned a number of mash-up videos, with each of those registering thousands more hits on their own.
Meanwhile, there was word late Tuesday that Duckett’s future employment with AHS will be reviewed by an emergency meeting of its board on Wednesday.
Ever since this controversy broke out on Friday, a few voices in the wilderness have come out in Duckett’s defence — saying in effect that this entire story has been a result of media manufacturing.
I can’t disagree more.
Reporters are doing their jobs when they pose questions to public officials.
It’s one thing to hear a second- or third-tier official explaining things in a press conference.
It’s a whole other thing to hear from the top dog of any organization — especially from someone who draws hundreds of thousands of dollars a year in pay and perks from the public purse. EDIT: In annual terms, that would be $575,000 in base salary, $10,000 in professional development, $15,000 for variable allowances including tax tips and club memberships, $18,000 for vehicles, health benefits, plus a variable bonus.
We’ve had people who’ve been so fed up with emergency rooms that they’ve dialled 911 from a hospital to see if they can hurry things along.
We’ve had an MLA (who happens to be an ER doctor himself) booted from the government ranks for speaking frankly about the state of things in our hospitals.
Clearly, these events are not manufactured by the media. The problems are real.
Which brings us back to Duckett.
If he understood how dire the situation seems to Albertans, he would have put the cookie down to reassure Albertans that things are being done to correct the situation.
Or he could have stopped to say he disagreed with Albertans’ assessment of the state of the health-care system.
Whatever. The point is, he should have stopped.
He is the boss of Alberta’s health-care bureaucracy.
No one else can tell us what he thinks — not AHS staffers closest to him, not the people at the legislature.
Media people are paid to extract facts and answers from the likes of Duckett.
After all, most Jane and Joe Albertans don’t have the time to quiz public officials every day.
Likewise, Duckett and others are paid to run our public services and as such, they are accountable to the public — sometimes through media questions.
The members of the Edmonton media involved with the Duckett affair were doing their job.
Stephen Duckett, on the other hand, wasn’t doing his.

Row on row

Tags

, ,

Please take a moment Thursday morning to remember our veterans.

Row on row

Shifting skyline

Tags

, , , ,

It just occurred to me the Calgary skyline poster at the top of this blog will soon need overhauling. Since I snapped that photo almost three years ago now, a truckload of new buildings have popped up in the core, including a couple that are still under construction. In fact, there are so many new buildings this city’s office vacancy rate is expected to soar in the coming years.
Anyway … time to hoof it to that parking lot on the east side of Nose Hill Park for a refresh, don’t you say?

Killing time at the laundromat

Tags

, , ,

Make it hot

Hardware solution to Safari 5 trouble. Really!

Tags

, , , , , , , , , , , ,

This whole Safari trouble got me surveying some people around me who use Macs and had upgraded to Safari 5.
My best bud, who has a late-model Airport Extreme, has had no trouble whatsoever. Another fella, who has a router as old as mine, was having the same trouble as I was. On the Internet, posts from Mac help forums users suggested people with no trouble possessed newer-model routers.
While skeptical about this Safari trouble being fixable by hardware, I figured I would sink some money on a new router. (I was going to do it anyhow.)
Lo and behold … all my troubles are gone.
And as a side bonus, I can better wireless throughput and can now print through my router. Just waiting to add a large network drive to back up my data.
But that’s not the point.
Not everyone can go and splurge on a new router just because Apple decided to upgrade their Web browser. Surely there is some software fix for whatever hardware trouble people are encountering.
This brings me back to my original hunch: Someone at Apple needs to add a check box to disable DNS prefetching. My gut tells me that’s been the problem all along. That’s how I “fixed” Chrome when its DNS prefetch feature continually caused my Internet connection to time out.
But is anybody at Apple listening?

Well, not quite done yet

Tags

, , ,

Reseting my prefs helped things a bit but those errors are still happening. Grr.

Reset your preferences!

Tags

, , ,

After reading some more about other people’s Safari 5 woes, I decided to reset Safari and trash the files containing Safari’s cache and preferences. Lo and behold, it seems to have solved my woes … Stay tuned.

Solution to Safari 5 DNS woes?

Tags

, , ,

Several discussion groups at apple.com suggest changing the DNS server settings on your computer to those from Google Public DNS instead of those from your ISP. I’m giving it a try … will report back.

“Safari can’t find the server”

Tags

, , , , , ,

But the server is there, I swear!
I wrote early this morning I couldn’t replicate an error in Safari 5 I had been experiencing through the previous day, where the browser would tell me it could not connect to a server even though the server was just fine.
Since I posted that message, the error came up again — and I got some screen grabs for you.
When confronted with the error message …

201006-SafariFail1 20100610-SafariFail3

… I hit the refresh button to reveal the webpages:

20100610-SafariFail2 20100610-SafariFail4

Anyone else in cyberspace experiencing this trouble?

A few words about Safari 5

Tags

, , , , ,

I installed Safari 5 on my computer last night. The vast majority of things work just fine.
I can’t really say I’ve noticed much of an improvement in performance but then I haven’t put the browser through its paces yet, either.
One major change is the introduction of the Reader feature, which allows you to read stories on news websites without the clutter of menus and such.
Just click on the “Reader” button at the end of the menu bar …

ReaderButton

… and Safari will turn an article on a webpage from this …

ReaderBefore

… to this:

ReaderAfter

Just click on the “Reader” button again to turn the feature off.
Pretty neat trick, if I may say so — although I must admit advertisers and their representatives will probably have a different opinion on the matter.
One negative thing that did stick out, though, was behaviour reminiscent of Google’s Chrome when it first came out a few years ago.
The browser would intermittently be unable to resolve hosts and fail to display web pages.
It was eventually determined the trouble was its DNS prefetching feature, which you could turn off to solve the trouble.
Earlier today, Safari did something similar from time to time, too, although far less frequently than Chrome did.
And now that I am trying to replicate the failure, I can’t.
Oh well, I will share if it crops up again.
In any case, if anyone out there in cyberspace knows how to turn off DNS prefetching in Safari, lemme know. It might come in handy later!