Skip to main content

I am not a software engineer

Software development is different from Professional Engineering. Engineers train so they qualify to work with well-defined bodies of knowledge. At least where I live, to be a PE (Professional Engineer) you need a license. That means having proper academic credentials, four years of ‘engineering work experience’ and passing an exam on ethics, professional practice, engineering law, and professional liability.

To call yourself a PE in Ontario means you have met a body of specific requirements. You are a known quantity. We call that a Professional Engineer.

I am a programmer. It is not my intent to denigrate programming. Programming is hard; taking decades to master but calling yourself a ‘software engineer’ is wrong. It muddies the waters with respect to genuine PEs. People who could not even get into an engineering program calling themselves ‘engineers’ is silly. For a real PE, it could be irritating.

People who dump the word ‘engineer’ into their titles cheapen the real engineering title. It is a title for which a real PE studied, worked, and pays an ongoing price in terms of liability, professional ethics, etcetera.

Developers and their skills vary a lot. They range from high to low. I have done work with great developers with doctorates in computer science, and I have done work with less great developers who have not graduated high school and only have one trick up their sleeve. They were all employed, hence 'professional ' in that sense. In some places they would have titles like 'software engineer ' or 'systems engineer '. However, they were hardly equivalent to a PE. Except for actual engineers I have worked with who were doing programming, even the best developers would not have the body of education, skills, and experience of a PE. I do not recall engineers I worked with who did programming taking on ‘engineer’ as part of their title.

Bottom line: ‘engineering’ means something and what it means is different from what people describe as ‘software engineering’.

Again, I am a developer here. I am not trying to denigrate software developers. I can do lots of stuff that an engineer could not do. However, that does not make me an engineer.

Comments

Post a Comment

Popular posts from this blog

The system cannot execute the specified program

It always annoys me no end when I get messages like the following: "The system cannot execute the specified program." I got the above error from Windows XP when I tried to execute a program I use all the time. The message is hugely aggravating because it says the obvious without giving any actionable information. If you have such a problem and you are executing from a deep directory structure that may be your problem. It was in my case. Looking on the web with that phrase brought up a bunch of arcane stuff that did not apply to me. It mostly brought up long threads (as these things tend to do) which follow this pattern: 'Q' is the guy with the problem asking for help 'A' can be any number of people who jump in to 'help'. Q: I got this error "The system cannot execute the specified program." when I tried to ... [long list of things tried] A: What program were you running, what operating system, where is the program? What type of
2 comments
Read more

Coming Soon: General Artificial Intelligence

The closer you get to experts who understand the nuts and bolts and history of AI, the more you find them saying that what we have is not nearly General Artificial Intelligence (GAI), and that GAI seems far away. I think we already have the roots in place with Neural Networks (NN), Deep Learning (DL), Machine Learning (ML), and primitive domain limited Artificial Intelligence (AI). Things like computer vision, voice recognition, and language translation are already in production. These are tough problems, but in some ways, machines are already better than humans are. I expect GAI to be an emergent property as systems mature, join, and augment one another. I was around during the 70s AI winter, and was involved in the 80s AI winter as one of the naysayers. I built a demonstration system with a Sperry voice recognition card in 1984. I could demonstrate it in a quiet room, but as a practical matter, it was not production ready at all. Around 1988 we built demonstration expert systems usin
Post a Comment
Read more

Your call is important to us, but not much.

Rogers entire network is down and Rogers either does not know why or sufficiently disrespects its customers that it won't say. I was on the advisory committee for the largest private network in Canada serving 150,000 employees countrywide. I was also an active participant building out that network. I installed the first Local Area Networks there. I wrote a code generator responsible for the most critical portion of Bell's mobile network. I also wrote a portion of code for a system in the United States that detected and pinpointed line breaks in their network before they happened. For a time, I held the title 'Networking Professor' at our local College. I registered my first domain name in the 1980s. I have administered Internet network servers for decades. In one capacity or another, I have worked with most of the telecommunications providers in Canada past and present. Nearly a billion devices use a small network codec written by me decades ago.  Except that Rogers was
Post a Comment
Read more