Photo credit: Mike Parker, 2015
Where to start?
My friend Laurie lives in an artist’s co-op, and every once in a while she puts together these shows in their gallery space. It was at one of these I met Mike Parker, who went to the same high school as Laurie and I.
OK, got all that?
So I reach out to Mike on Facebook, and every now and again he puts something up, and I put something up. It seems we have similar political views.
Years go by.
Then, in August, he puts up this pretty cool pic, of a girl, nude, in a cardboard box.
She had braided hair, and you could see a couple of tattoos on her forearms. (I only mention the braids for layout purposes. )
On the face of it, Wind is the best deal we have here in Toronto. For $45 I get unlimited everything: talk, text and data. But there’s a long list of deficiencies which need to be addressed. Hopefully this post will be one more incentive for Wind to actually do something about their execrable service. At the very least it should give prospective customers pause.
As I mentioned in a previous post, I’m now working with someone who has a couple of NFL handicapping programs. These are written in APL and only run on Windows machines. I have to install these programs, so I can see how they work. But I don’t currently have a running Windows machine. But I do have a Windows 7 virtual machine which runs on VirtualBox.
Great! But, oh, wait, I haven’t used this VM in ages, and I don’t remember the password. So a little googling for “windows 7 virtualbox password” brings me to top-password.com. Don’t get all excited, now. It’s a dud.
For the past 15 months I’ve had the tremendous pleasure of working at an institution I respect enormously: The Toronto Star. My job was to support the toronto.com property, where hard working editors constantly maintain an up to date list of things to do, attractions, restaurants and events such as concerts and plays, in our wonderful city.
And along the way, I got to work with an awesome team of software professionals, tasked with supporting, maintaining and enhancing the digital version of Canada’s largest newspaper.
But, sadly, all things come to an end. The powers that be decided to move the Toronto.com site off the WordPress platform, and onto Adobe’s CQ5 content management system. So my job was disappearing. I was advised of this decision well in advance, so I started my job search early. But truth be told, I was kind of hoping something would materialize at TorStar.
I was recently contacted by Dave Wilson of DaveWilsonPhotography.com. Dave had been using the PhotoQ WordPress plugin for his photoblog. It allowed him to schedule the release of posts with a given image. It would additionally extract and display the image’s EXIF data. This was before WordPress could schedule posts on its own, and saved Dave all kinds of time. He could spend a few hours loading up pictures and posts, and he’d be set for a month of daily posts.
But nothing lasts forever, and Dave’s happy setup was disturbed as his host’s PHP engine was upgraded, while PhotoQ, now no longer supported, was not. The front end of the site still worked fine, but the admin side had issues.
My friend Mariann has been an avid promoter and attendee of Toronto’s HotDocs festival, lo these many years. So it was no surprise when she called to recruit me to be part of her entourage while attending said festival. I had, in fact, discussed one of this year’s selections with colleagues at my new place of employment (well, perhaps not so new any longer: I’ve been there about six months now; but more on that another time), and was keen to attend a screening of The Internet’s Own Boy: Aaron Swartz. But not just any screening: one of the several screenings was to feature a panel discussion with Cory Doctorow, Lawrence Lessig, Gabriella Coleman and the director, Brian Knappenberger.
Last year I was taken with a sudden and feverish desire to master what some call the NATO Phonetic Alphabet. You know: Alpha, Bravo, Charlie, for ABC.
Except a phonetic alphabet is, in fact, something else; it’s a notational standard for the representation of a language. It’s about how to pronounce the language.
By contrast, the radio alphabet, allows you to accurately transcribe letters by assigning a word for each letter. Handily, the words assigned start with the letter they’re assigned to. So, Alpha for A, Bravo for B, and so on. It’s about reading it out to someone across, say, a radio, and being reasonably certain they won’t mistake a P for a T.
OK, so that’s the What. Continue reading
I’m sick of going looking for this information across the web when I need it. So I’m putting it all together in one place. This is for my own use, but you’re welcome to reference it as well, if you find it useful. Just so it’s been said: the canonical online reference (IMO) is the Mozilla Developer Network, aka MDN. Continue reading
I’ve been on contract for the past couple of months at a lovely company up in Newmarket, called Solutions360. I’m part of a team working on a system for the travel industry. So we’re deep into API’s for hotels, flights, cruises and such. Listing, booking, cancelling have been our constant concerns for weeks now.
My bailiwick is a module called a Service Manager, which translates requests from our system to an outside web service. Then captures the responses and again translates them into a standard format for the system to display.
The first Service Manager I wrote used the
cURL library to communicate with the external service. So when it came time to interface with the Sabre services I tried using the same mechanism; but for some reason it was a non-starter. I tweaked it as much as I could; as much as it made sense to. But the only response I got was an error that the service “couldn’t internalize the request.” *sigh*
And while Sabre’s support team has proven to be enormously helpful and responsive, on the phone and via email, if it isn’t Java or .Net, you’re pretty much on your own. Continue reading
Over the years of learning the many and various skills necessary for being a well-versed web developer, you find a number of tools to help you get things done. Sometimes you have to build those tools for yourself.
There are any number of logging solutions out there, but I decided to build my own for a number of reasons. First, I had some specific requirements in mind, and I didn’t want to spend a bunch of time exhaustively researching the available options, when I could just build my own. Secondly, building my own solution allowed me to exercise design and development muscles I might not otherwise get to flex. Thirdly, building my own allows me to share it with you.
To my great and everlasting shame, however, I never got around to documenting this class. Well, never is a long time. “Never”, until now. But it has been many years since I started this project, and I’d been meaning to post some documentation since then.