An Eventful Evening

It’s been a stressful couple of weeks, what with all the exams I’ve been writing lately, so I haven’t had much time to blog. That aside, I didn’t have many spare brain cells left to write with or any interesting events to report. And just when I thought I had nothing to write, I get assaulted on the way to the movies.

Ashley and I were going to see a movie up on Granville Street and were just crossing the intersection of Nelson and Richards when we saw a man strike a woman. At first, I thought it was a guy being a jerk to his girlfriend, but then he rushed at Ashley and me, striking me in the side of the head. No big damage, but it was a bit of a shock. He was yelling and obviously just looking for a fight. Ashley and I put a bit of distance between ourselves and him and went to help the woman.

At this point, I started thinking straight and asked Ashley to dial 911 on her cell phone. Of course, the one time we actually need a cell phone, she doesn’t have it. I watched as across the street the man proceeded to kick at a taxi and get into another scuffle with another man. I signaled to a woman in a car to dial 911 on her phone. She was in some kind of stupor and took forever to pull out her phone and start dialing. By that time, the man that had been involved in the scuffle had dialed 911. I approached him and used his phone to talk to the police.

We followed the man down into Yaletown, keeping our distance while giving the police directions and a description of the man. The police caught up with us near the Opus hotel and arrested the man (much to the chagrin of a classmate I ran into just as the police showed up).

As it turns out, the man had a mental condition of some kind.

What should have been an episode that would only make me further cynical about the human condition turned into quite the opposite when I met up with Ashley at a local Starbucks. As it turned out, the Starbucks manager had given her a free latte while she waited for me, which was a pretty decent thing to do. And it happened again when we went for dinner: we were a little zoned out so Ashley explained to our waitress what had happened. The manager came over and explained he’d had a similar experience in the restaurant a few nights ago. Then he gave us our drinks on the house!

Wow. Maybe people aren’t so bad after all. Only in Vancouver could I get assaulted and end up feeling better about humankind. How’s that for something to write about?

Professional Practice Exam

I wrote the Professional Practice Exam on Monday, part of fulfilling the requirements for registration as a PEng (Professional Engineer) with APEGBC. Though the exam went well, I am still concerned with the focus of the Association on the “traditional” fields of engineering, and the lack of action with respect to advancing the state of the software engineering as a profession. Now, more than ever, the Canadian public (and the world in general) needs professional software engineers who are empowered to protect the public’s health and welfare.

Consider the suggested study material for the exam:

Though the books cover the requisite material in excellent detail, most of the case studies leave much to be desired. Legal precedents cited in the first book focus primarily on legal actions related to the construction industry, ignoring most other areas of engineering. Studies of ethical dilemmas in the second book again focus on “traditional” engineering fields. What amazes me is the complete lack of any coverage of the multitude of unique legal and ethical problems faced by Software Engineering, the youngest of the professional engineering streams. Engineers in this field require more, not less, guidance than their colleagues in more traditional fields of engineering where most of the “best practices” have been well established for decades, if not centuries.

When I registered as an EIT, I wasn’t entirely convinced that the Association provided any real benefit to electronic, computer, or software engineers. Every year at my university (SFU) the Association would swing by and declare, “you should go for your PEng!” but would fail to provide any tangible reason to do so, except for members of the “traditional” engineering fields. I entered the EIT program with the hope that the appearance of the Software Engineering stream signalled that the Association was becoming more relevant.

Three years later, I’ve seen little action on the part of the Association for Software Engineering. Sure, the Engineer and Geoscientist’s Act (“the Act”) requires you to be registered to engage in the practice of engineering, but I see little or no enforcement in the fields of software, computer, or software engineering. There are plenty of people operating in the field without certificates or registration, but the Association isn’t stopping them (in fact, the Act doesn’t provide adequate enforcement provisions according to APEGBC). Most employers aren’t looking for registered computer, electronic, or software engineers, and anyone who’s “really into computers” seems to be calling himself or herself a “software engineer”.

Any time I’ve contacted members of the Association, the reply has taken a long time and has done little to reassure me. The CSED (Computer and Software Engineering Division) of APEGBC shows very little activity. Though I’m trying to get involved to help the CSED, I get the sense that members of the CSED have already been deflated by the Association’s lack of action.

You might ask: why is this important? True, most software is destined for applications that don’t have even a remote chance of endangering life, but bad software is costing companies billions in downtime and exposing their confidential corporate data. Isn’t it part of our obligation to protect property, and the general public good? What public good is served by allowing companies to release defective software? In addition, there is a risk to the traditional engineering fields (civil and mechanical engineering in particular) that their increasing reliance on software products (most likely not designed by engineers) to design and build products could endanger life and limb.

Software touches every aspect of our lives. I would suggest that by failing to act appropriately to enforce registration, the Association is failing to fulfill its obligations as described by the Act. My question is: what is the Association currently doing, or (in the near future) going to do about it?