Trapped!
A visit to the TTC's website today reveals in large bold print: "NO TTC SERVICE TODAY" Looks like I'll be working from home for today at least!
A visit to the TTC's website today reveals in large bold print: "NO TTC SERVICE TODAY" Looks like I'll be working from home for today at least!
I blogged back in January that I had registered for the Sporting Life 10km. This was part of my New Year's resolutions to lose weight and get my 10km time under 50 minutes. Well, the run was this past Sunday, and my time was 50 minutes 12 seconds. So close! I'm pretty happy with my time though, I felt like I pushed myself a lot harder than I did at the Harry Rosen Spring Run Off in April, and I managed to improve my pace from 5:14 per kilometer to 5:01 per kilometer. The other part of my New Year's resolution, to lose weight, is coming along a bit more slowly. I have shed a few pounds since January, but nowhere near the amount I was hoping to. Still, I'd rather be slightly more fit and heavier than out of shape and lighter!
I spent a little bit of time today looking into some of the storage solution choices out there. I was mainly concerned with systems supported under Linux, but I didn't limit myself to just those.
My quest started this morning when I read a post on Gizmodo: Buffalo DriveStation: Serial ATA, Fanless Design. I had heard of Buffalo Technology before, I've often considered buying one of their products, or something like it. What could be better than a 2 Terabyte box that you just plug into your network and configure? Well...The Perfect Storage Solution of course!
A few simple use cases may describe what I'm looking for. First, if a drive fails, I want to be able to replace it with no downtime, loss of data, and using any drive of sufficient size (at least as large as the one that failed) that I have on hand. Second, if I'm running out of free space, I want to be able to add a brand new drive and start using it. Third, if there is no more physical room for a new drive, I want to be able to migrate data off of the one of the drives (probably the smallest/oldest one), to make room for a newer, larger drive. I suppose this is a direct consequence of satisfaction of the first requirement.
Out of these simple cases, I can distill a few must-have features:
From the American Papist:
Please note an interview with Dr. Janet Smith, Fr. Michael J. McGivney Chair of Life Ethics and Professor of Moral Theology at SHMS will be aired on an Australian Radio program tonight, Tuesday, May 2, 2006 at 8.30pm our time [EST]. The topic will be condoms and aids [what we've been talking about]. You can hear this interview by visiting http://www.abc.net.au/rn/audio.htm [More information on the program: http://www.abc.net.au/rn/talks/8.30/relrpt/Mel would love this, but she's in Vegas right now, so I'll have to download it for her. Mel and I are also going to see Dr. Janet Smith speak at the Humane Vitae conference in Ottawa next weekend. We can't wait!
On his blog, Ian Bicking responds to the article, Ruby and Python compared. While there is much in the latter that is uninformed as to what Python is capable of, the most important point I got from Ian's post was:
An important rule in the Python community is: we are all consenting adults. That is, it is not the responsibility of the language designer or library author to keep people from doing bad things. It is their responsibility to prevent people doing bad things accidentally. But if you really want to do something bad, who are we to say you are wrong? It's your program. Maybe you even have a good reason.I think this should be the motto of any module developer: "Keep people from doing bad things accidentally." It's impossible to keep a developer from shooting himself in the foot if he really wants to, so don't try too hard. Your job is to enable users of your code, not restrict them. I've heard many C++ / Java programmers complain that Python isn't object oriented because it doesn't offer private/protected data for classes. In a perfect world all libraries and modules would be perfectly designed and there would be no need to go mucking with the internals of a module you didn't write. Back here in the real world, APIs are often not as well thought out as they should be. In Python (and in Ruby as well I'm guessing) you can muck about with the internals of classes or objects if you have to. It's either that or get the upstream package fixed and distributed everywhere before you can deploy your application.
My eternal gratitude goes out to Ned Batchelder, whose recent post (via the Unofficial Planet Python) has introduced to me the goodness that is The Daily WTF. Enjoy.
The Harry Rosen Spring Run-Off that I registered for in February was today, and was my first race of the season. I managed 8km in 41:50. Not bad, but not quite the 5 minutes per kilometer that I've been aiming for. It was a beautiful day for a run, the temperature was pretty crisp (just above 0 I think), but the sun was shining brightly. But oh man, that last hill is a killer!
Today on the front page of the Toronto Star, the National Post, and the Globe and Mail is the "news" about the "Gospel of Judas" and how it describes a hidden side to Judas that has been covered up for centuries. I realize that everybody loves a conspiracy theory, hence the popularity of things like the X-Files and The Da Vinci Code. But just because something written at least 1,700 years ago was rejected by the experts of the day does not mean there is or was a conspiracy at work. In the article in the Toronto Star, Francine Kopun quotes expert Bart Ehrman that "There is no doubt it is genuine." A genuine what? Yes, this manuscript dates back to the 3rd century. It is genuinely a 3rd century manuscript. But is it genuinely the "Gospel of Judas"? Does it have anything historically accurate to say about Jesus or Judas? Nope. This is not the first time this "gospel" has popped up. St. Irenaeus of Lyons refers to a "Gospel of Judas" in his work "Against the Heresies," written around 180 AD, more than a century from the date of the manuscript being discussed in the news. Kopun quotes Ehrman again: "I think what this gospel does is show us that Christians in the early centuries believed an extremely wide range of things." If Kopun or Ehrman had done their research, they would have found that these writings were recognized as frauds at the time they were written, and had no basis in truth. I guess there's a lesson to be found here. You can write whatever garbage you want, and if nobody buys into it now, just wait a few millennia and people will trip over themselves to show how it was covered up by the established belief system, and write books and make TV shows and movies about it!