No doubt about it, I’m going to copyright hell. Yes, I’ve once again raided the Toronto Archives (I highly recommend a search or two; lotsa fun stuff), and emerged with some gleaming gems. Should the Archives ever decide to sue my blatancy, I’ll no doubt be forced to hand over much of TCL’s total monetary earnings to date: $3.67. If I made them cry, emotional damages too. But I just can’t help it; they have way too much great stuff to hide behind a stuffy web interface.

This time around I went back to the mid-sixties in search of the very beginnings of computing in Toronto. Okay, yeah, I’ve been spending a lot of time online making sweet sweet love to the blogosphere. And programming. But the digital miracles I’m pulling out of my ass (and many of us are), these days would’ve been unimaginable forty-five years ago. In fact, even though I’m more closely familiar with most of the gizmos in these photos than the average person, even I’m at a loss to put name or function to everything there. But I’ll try.

Okay, so from my understanding, this is what computing looked like at the University of Toronto circa 1965ish:

Can you imagine what it would’ve taken to slap together a basic web page at that time? Like, look at the fellow in the photo above; picking out a frozen pizza because he knows he’s going to be a while.  It’s nice that they provided slushie machines for the programmers:

I guess he’s picking his flavour.

Oh, yeah, of course I’d be hideously remiss if I didn’t mention the sideburns. That was the requisite look in those days, from my understanding. For when you’d fall asleep on your desk on account of the speed of the computers. Sop up your drool ‘n all. (I know, gross, but hey, practical.)

So here’s Mr. Burns actually earning a living:

… Continue Reading

It’s done, dear reader!

I’ve signed on the dotted line and am now the proud new Senior Flash Developer at Henderson Bas, a downtown ad agency with a bunch of famous clients and awards coming out the wazoo. I normally wouldn’t mention their name but, being so out there, I don’t think they’re averse to being discussed. I’ll just have to refrain from talking too much smack.

The contract was a gargantuan tome, one of the largest volumes I’d ever encountered. A whole adult tree made up just the non-disclosure agreement alone, the rest had to be delivered by freight train. So it’s pretty thorough. I’m fairly certain I’ll have to relinquish my spleen upon termination, but that’s a pretty standard clause. Otherwise, I’ll be slapping stuff together for HB come Monday; incidentally also my birthday (I know, right?)

In the same way that I won’t talk smack about HB, I’m not going to go into the gruesome details of why I left my current position. Let’s just say that there were some … issues.

… Continue Reading

Is it okay if I get a little personal today? Just this once?

I did resist for so long, but I finally feel like I need to mention … the day job.

Okay, I need to bitch.

Are you groaning already? See, that’s why I resisted. I know how you feel about people whining about their jobs, and I totally get it. I mean, there are plenty of people who would love a job, and there’s plenty else to blog about, right?

You couldn’t be more correct in agreeing with me. But  I figure TCL can accommodate everything Toronto-related for at least one post. And I work in Toronto, so it qualifies.

Besides, my intention is to make this as painless, boringless, and whiningless as humanly possible. No names, of course, and I don’t claim that any of this is true. But I think inspired would be a good way to put it. Very inspired.

The People

Manager: My immediate manager (plus a few other people’s, including the art team’s).

MANAGER: Manager’s immediate manager.

Art team: The people who produce the designs and artwork for the software.

IT: The people who manage all the computer hardware and software that we use.

The Words

Bug: Any problem with a piece of software. Could be as small as the wrong colour on a button, or as big as your computer bursting into flames.

Bug ticket: GODDAM COCKSUCKING MOTHER OF A WHORE!! (A notification, usually by email, that the testers found a bug in the software we’ve written).

Code: The instructions (written by us) that make up the brains of the software. If we’re feeling fancy, we call it “source code”. But code sounds cooler.

Build: When all the code, art, etc. get collected and mushed together to produce the final software product.

Specification: A long and boring document that describes, in detail, what the software should do, how it should do it, how it should look while it’s doing it, and so on. At least, that’s what we hope for.

Server: A computer that sits on a network and “serves” data to any other computers that request it. That data could be a web page, Twitter feed, or hardcore pornography. Computers are awesome!

To: MANAGER@employer.com
From: patrick@employer.com
Subject: Requested time allotment report for Tuesday
Sent: Tuesday, September 1, 2009

Time Allotment

10:00 – 10:30: Searching for Manager to discuss bug. After questioning, art team revealed that he is home sick today.

10:30 – 10:45: Had to do some research to retrieve Manager’s unlisted telephone number. The one he recorded for our records is our own office number (we should probably update that).

10:45 – 11:00: Telephone call with Manager to discuss bug. Manager maintained that it was “impossible” for it to be his code so I re-assigned bug ticket to myself for investigation.

11:00 – 13:00: Ran verifications and concluded that the bug must be addressed in Manager’s code.

13:30 – 13:35: Telephone call with Manager who confirmed that, “of course”, the bug was something he needed to fix.

13:35 – 13:40: Emailed response to build team’s complaint regarding errors in our builds. I reminded them that we can’t prepare our code for a build if they don’t tell us they want to do one. We have not as yet been able to develop psychic abilities.

13:49 – 14:00: Discussion with you regarding project X:
Project to be completed by this Friday or next Monday for release in the afternoon, same day. Art team will produce graphics on Thursday and  the specification will be ready by Friday morning. Testing to begin next Tuesday with a round of bug fixes scheduled for next Wednesday. Scheduling discrepancies will be dealt with later. This is to be exclusively top-priority until finished.

14:00 – 14:30: Your team meeting request to discuss why the schedule wasn’t being met. Team agreed that closer attention needed to be paid to scheduling.

14:30 – 14:45: At your request, sat with your assistant to update the schedule with accurate dates and times for current projects.

14:45 – 14:50: Emailed IT explaining why I needed a license for the Adobe Flash development software (specified that I am an Adobe Flash developer). The software lock currently in place on my copy of the expired software is preventing me from effectively doing my job.

14:50 – 14:55: Emailed IT again explaining why my current software was, as yet, unlicensed. I included copies of the six unfulfilled software requisition forms I submitted during my first six months of employment.

14:55 – 15:00: Discussed with you why I required a software license for the Adobe Flash software.

16:00 – 16:05: Larry asked, on your behalf, for a detailed estimate on development time for project X.

16:05 – 16:10: Wong asked, on your behalf, for a detailed estimate on development time for project X.

16:10 – 16:15: Vergil asked, on your behalf, for a detailed estimate on development time for project X.

16:15 – 16:20: You requested an estimate on development time for project X.

16:20 – 16:50: Took lunch.

16:50 – 17:00: Worked on project X.

17:00 – 17:10: Meeting to re-assign priorities. I should now focus all my efforts on project Y.

17:10 – 17:15: Vergil asked, on your behalf, for a detailed status report on the progress of project X.

17:15 – 17:20: Emailed IT to request more disk space on our only development server. Explained that it was the only way to test our software. Request was denied, but I would like to point out that I am willing to purchase an 8 Gigabyte memory stick ($20), out of pocket, to effectively quadruple our storage capacity. Please advise.

17:20 – 17:40: Deleted and compressed data on the development server to clear up some space.

17:40 – 17:50: Sat with your assistant to re-input the schedule from this morning. I’d like to suggest that only one person be responsible for updating the schedule to preventing this type of data loss in the future.

17:50 – 18:00: Produced this time allotment report to identify some of the inefficiencies in our system.

Thanks for humouring me. I feel … lighter.

Should I find myself suddenly unemployed for some reason, I’ll even be able to reveal how much of that is actual, unembellished truth. The number shocks even me.

And as a special favour to you, I will abstain from boring you to tears again for at least a week.

The new Netbook I purchased yesterday has been inaugurally dropped, shaken like a wailing toddler by a coworker, and still appears to be running. I can’t adequately express the excited shivers I feel running up my spine as I write this in the thick of it: on the streetcar! Must be why they call it the Eee PC.

Or maybe it’s just the caffeine. There’s not really much going on; streetcar’s a bit off schedule. Hum.

Actually, I got this funny little conpooter because my gargantuan laptop; well, she’s about to die. She can’t boot sometimes and that horrible, horrible clicking sound coming from somewhere in that portly package, that usually signals imminent death. *sob*

I could almost survive without the teevee (which is one of Bertha’s — that’s the computer — functions), but not having TCL, that would have been too much. So I bit the pillow and shelled out a few hundred for this little wonder of a gizmo. If only my fingers weren’t so big-boned. The keyboard’s in the lowest order  of  comfortable typing surfaces, but it should do until I scrape enough money together to purchase a beefier machine. Or at least something that’ll let me play Tomb Raider comfortably.

For $350 bucks I got a 1.9 gigahertz processor, a gigabyte of RAM, a 160 gigabyte hard drive, and the soothing knowledge that when Bertha finally kicks it, I’ll at least have something to fall back on. If those specs don’t mean anything to you, trust me, it’s a good price.

My shopping prowess aside, such good deals can be had commonly in a little section of College Street between Bathurst and Spadina that I’ve taken to calling Computer Alley. It’s not really an alley, but doesn’t it make it sound somehow more intriguing?

On this short strip you will find an unusually high density of computer stores, many of them operating directly beside each other, and many staffed by Indian, Sri Lankan, or Pakistani men, which always implies good bargains (you know it’s true). Sometimes the price cuts are so deep, it’s a hemorrhagic wonderland of bargains. Even if you only have twenty bucks burning a hole in your pocket, you’ll find a nifty gadget to spend it on. For the gentlemen, besides computer hardware there are plenty of wierd and useless digital devices that will help to demonstrate the superior size of your penis to the ladies. Ladies, some of these things are *sooooo* cute. There; all bases covered.

The really great thing about strolling down Computer Alley is the number of licensed establishments interjected between these hardware shops; liquor, money, and digital hardware is a fun afternoon for everyone, especially the kids. You might even spot me there inebriatedly trying to squeeze some bargains out of the hapless shopkeeps. Then again, with no photo of me, that may prove to be somewhat challenging. How about this? I’ll be the guy schlepping the Asus around.