I rarely make a fuss about the places I go and the things I do, but I had another one of those moments last week when I felt the weight of history.
I was in Capetown, South Africa, on a glorious winter week-end, and I had strolled out to the Waterfront. Walking back to the city at sunset, I was suddenly hit by a feeling of the immense age of the mountains compared to the (relatively) new city nestling in the hollow at their base.
Naturally I’d forgotten to take my camera with me on my walk, and my mobile phone couldn’t cope with the low light – but here’s a picture I’d taken (on my phone) on the way out to the Waterfront a couple of hours earlier. If you imagine the perspective from a mile further away, with the city looking about one third of the size and the mountains unchanged, you may get an idea of the image that made me stand and stare.
Now that I’m back home I’ve got a load of comments that need answers – so you can expect to see my name as the author on just about every comment on the comment list for the next two days.
Rob Freeman raised an interesting topic on Oracle-L a couple of weeks ago with the following:
My question is, what constitutes Oracle Book Writing mal-practice (and I pray I’ve never committed it). Certainly mistakes crop up in books all the time, I’m as guilty as any writer of this. This chapter I’m reading though, in an effort to get the reader to doing something quickly, does not lay any foundation, skips critical steps and actually prompts them to do what I consider some very dangerous things.
The posting didn’t really generate a lot of discussion – which is a shame – and my privileges to write to Oracle-L lapsed some time ago, so I’m writing my response to Rob’s observations here.
When I was in Salt Lake City a few months ago, Barbara Matthews (one of the organisers of the SLC Oracle User Group) asked me for my “Top 10” books about Oracle.
In the last five years I’ve visited more than thirty different countries and seen a lot of wonderful sights – some natural,some man-made. But Sunday was the first time I’ve walked into a hotel room and been overwhelmed by the view.
I was in Athens, staying at the Hilton, in a room facing the Acropolis – and most of the wall was glass, so the impact of the view as I walked into the room was staggering.
The picture, inevitably, doesn’t do justice to the scene. When I tried to include the sweep of modern Athens the Acropolis got lost in the picture; when I tried to capture the Acropolis I lost the sense of how it grew out of the surrounding cityscape – this is the best I could do.
When you’re there, the feeling is of an immense sea of modern buildings, with the Acropolis as a giant focal point that spreads a layer of solidity and calm over everything about it. It is an extraordinary contrast.
Here’s an interesting URL that I found by following an incoming link a little while ago.
If you run Firefox as your web browser, this “Customizegoogle” add-in allows you to “filter spammy websites from search results”. (It’s got a lot of other features, but this one seems likely to be the most useful to Oracle users).
I’ve got Firefox on my Linux RAC stack – but I may have to download it for my Windows boxes too, especially the laptop which is the machine I use for most of my writing.
Update: And here’s a URL that should let you do the same thing with Internet Explorer, too.
Update 2: A link to the “Oak Table Safe Search” that limits Google to a few sites that tend to give good information. It will miss some good sites and will occasionally provide an indirect link to some less desirable pages – but generally it’s a good starting point.
Update 3: A couple of interesting developments relating to Google Chromeand “Content farms polute search engine results”.
This may not translate well because of the colloquialisms, but it seems appropriate for the current time of year (early January) in the UK.
You may have noticed that I spend quite a lot of my time explaining why something is a bad idea and should be treated with caution. Occasionally this has resulted in complaints that I keep pouring cold water on everything. The best response to this comment is one I first heard many years ago:
“Cold water is the natural result of hot air meeting thin ice”.
Here’s a guideline on how much trust to place in advice you get from articles about Oracle published on the Internet (even the ones published by Oracle Corp.):
- If it’s not dated – don’t assume it’s true
- If its date is more than about 18 months old – don’t assume it’s (still) true
- If there’s no version number – don’t assume it’s true
- If it’s not your exact version number – don’t assume it’s (still) true
- For ‘technical implementation’ details, if there’s no platform mentioned – don’t assume it’s true
- For ‘technical implementation’ details, if the platform’s not the same as yours – don’t assume it’s true
- For ‘technical implementation’ details, if the feature set described does not match yours – don’t assume it’s true
- If there’s no rational justification supplied, and no repeatable test case – don’t assume it’s true
And even when all the details are perfect and there is a repeatable test case – and even after the repeatable test case produces the same results – ask yourself this question:
“Could there be a different explanation for the same set of results and, if so, how badly could this advice damage my system and how hard would it be to test my alternative hypothesis ?”
Once you’ve got through that lot – then you might be safe trying the advice on a development system.
Update 19th Aug 2010
Since this note was more than 18 months old it needed to be validated (according to its own standards) – and there were a couple more thoughts that crossed my mind:
- If the only justification for a claim is an extract from the Oracle documentation then check that the quoted article (still) exists – and if it doesn’t exist or the quotation isn’t accurate don’t trust the claim.
- If the only justification supplied in an article is an extract from the Oracle documentation don’t quote the article to someone else, supply the link (or reference) to the original documentation – it’s more likely to be in context, and it’s more likely to be corrected and brought up to date (eventually) if it’s wrong.
Update (20th Jan 2013)
Time passes so quickly – I should have reviewed and re-affirmed this item months ago. On the other hand, I’ve just decided it’s not really about Oracle (exclusively) and it’s definitely not a detail of technical implementatin, so it doesn’t really apply to itself. It’s going be valid for years.
Update (19th August 2015)
I just failed to follow my own guidelines – see posting referenced by the last pingback below – so I decided to remind myself of the comments I made all those years ago. And then had to insert one more caveat to the list.