4 ms·
I call myself a Software Engineer specifically because I see it as different to being a programmer. I don't just write code, I try to solve problems in a rigoro
by danpalmer 10y ago
I call myself a Software Engineer specifically because I see it as different to being a programmer. I don't just write code, I try to solve problems in a rigorous and maintainable way, while being aware of the wider implications of my work to the business, our customers, and anyone else who might be affected by it. Sure we don't have the same regulation as civil engineers, but I try to do my work in the same spirit.
As part of this, I have a "masters of engineering" in computer science, which again, while not the same as civil engineers, still had a lot more wider study than a standard computer science degree.
I think programmers should do more engineering, and I think they should be recognised as engineers when they do.
- hashkb 10y agoThis misses the point that all other types of engineering are regulated and licensed.
- hashkb 10y ago...or at least ignores it without a reason.
- Hyperborian 10y agoHas that always been? Were the first engineers regulated and licensed? By whom? Perhaps we're just looking at a category of engineering that is not yet at that level of maturity.
- Alex3917 10y ago> This misses the point that all other types of engineering are regulated and licensed. Software is going to be regulated, licensed, and unionized within the next ten years. The main reason it's not currently is because the best practices have historically changed every couple years due to Moore's Law, but there is about to be an extended slowdown that will give the industry the time it needs to get its act together.
- frou_dh 10y agoThere is a constant: people using memory-unsafe languages, and then collective shrugging after the same things have happened over and over. Cloudbleed? Old news by now...
- eru 10y agoCare to take a bet on that? We just need to nail down some details: what jurisdiction(s) are we talking about? And what do you mean by licenced?: eg people without the licence won't be allowed to program computers? What odds are you offering? I am pretty confident, so I am happy to give you ten to one odds. Ie you pay me 1 dollar if no regulation&unionization happens, I pay you 10 if it does.
- Alex3917 10y agoNot interested in betting. > What jurisdiction(s) are we talking about? But to clarify, I'm talking about the U.S. > And what do you mean by licenced?: eg people without the licence won't be allowed to program computers? I think at least one of the big tech firms will be unionized within the next five years, with more following soon after. I think initially people already employed will be grandfathered in without any licensing requirements. But within a few years, I think folks are going to have to demonstrate basic knowledge of security principles in order to become union members. I don't think you will need a certification to work in the industry in the immediate future, but I think that tech employers will have a clear choice in choosing between union and non union employees.
- eru 10y agoIt's not about the money, it's about going on public record (and also about nailing down the odds you are willing to give). Interesting perspective you have. May I ask what makes you think so? Any current indications? What could go otherwise, and why? Do you see the beginning of these trends already? I would be very surprised if any of the big American big tech companies (say, Microsoft, Google, Facebook, Amazon or any other company that rises to similar status in the next five years) will get unionised like you say. There are already certificates available for employers to judge: be that university issued degrees or industry certificates like from Cisco or Microsoft. From all I can tell, the top employers don't care about them (and if anything, I have seen people scanning resumes react negatively to CVs claiming industry certifications). So current trends don't seem to point in your direction---as far as I can tell.
- ubersoldat2k7 10y agoOTOH, the same principles behind civil engineering apply today and 10 years in the future, which means it can be regulated. Just think what this would mean for software, taking into account the iPhone is 10 years old.
- danpalmer 10y agoWe have regulations. I deal with the data protection act, if you use medical records there's lots of regulation around that. I'd argue that there's plenty of engineering that doesn't have regulation as well. I think engineering is less about adhering to regulations, and more about solving problems in a wider context.
- nobleach 10y agoAll? Are people that work in music studios (Sound Engineers) regulated? I have know people that have gone to Full Sail (one of those 40,000 for-profit schools) That have gone on to be "Engineers". Engineer simply means "one who engineers things".... or drives a train.
- ohstopitu 10y agoSoftware Engineering is recognized as Engineering both by IEEE and by Professional Engineers of Ontario (or other provinces) who are members of Engineers Canada. Certification does exist....it's not widely used or accepted because in most cases, companies want developers not engineers. To add to it, the only thing stopping Software Engineers from becoming members of the above mentioned organizations is a code of ethics (and experience) - not knowledge or know-how.
- naasking 10y ago> Certification does exist....it's not widely used or accepted That's an understatement. Was speaking to a fellow engineer recently, and he claimed that there are really only two licensed software engineers in all of Toronto. We probably have tens of thousands of software developers.
- ohstopitu 10y agoThe only place where I've seen the certification as a requirement is govt jobs (and UfT I believe). Apart from those two, I've yet to find even a reference for it (let alone a requirement) - which is a cycle because one of the requirements of being a PEO is 12 months of work experience under a PEO (which won't happen as there aren't enough PEOs - the chicken and egg problem).
- Panini_Jones 10y agoCan you link to the U of T job with the cert requirement?
- KeytarHero 10y ago"Engineer" is a protected title in Canada (like "Lawyer" or "Doctor", although not as strictly enforced). You can't use it unless you're a member of your province's professional engineer organization. It's incorrect to say an engineer can "become" a member of one of these organizations, because you're not legally an engineer until you are a certified member.
- 2_listerine_pls 10y agoIf you take a look at the definition of engineer, nowhere does it say that you must have a license.
- eru 10y agoYou say that like it's a good thing?
- VLM 10y ago"I try to solve problems in a rigorous and maintainable way" The original linked article was written by someone who's never engineered anything and clearly has no social or cultural connection with any engineers, but I can see in one line that you and I are at least partially on the same page about what engineering is, which is not much of an endorsement for the article. The critical difference between science, engineering, and art/craft is engineering involves highly predictable well trodden ground where simulation always corresponds to measured reality. The predictive process is complicated and takes a long time and a lot of effort to learn and ingrain. The aesthetics and tradition don't matter as much (or at all) compared to the predictable performance and predictable cost. That's engineering. The difference between a science and engineering is an engineers output is optimized to minimal cost yet fits a predictable yet variable safety envelope. That column will not buckle with 99.999% odds over the lifetime of the building if built to commercial standards and my specs. Science is much less predictable and its criteria for prediction is much lower and generally not "safety of life" related and tends to be extremely abstract. Is that theoretical cosmological model interesting and not provably invalid? OK publish. Does that biomedical pharma experiment have more than 2 sigma of abstract statistical significance or whatever the statistical flavor is for pharma research today? OK publish. Science can of course eventually turn into engineering... A lot of chemeng make a lot of money turning lab bench scale processes into factory scale processes, they are engineers because they understand and predict scalability, unlike computer scientists who famously do not. The difference between craft/art and engineering is again safety of life and predictability but in craft/art you don't care about optimizing cost and safety as primary criteria. Does that custom bookcase have nice proportions? Is the wood grain clear? Is the stain too dark or too light or just right? Sometimes craftsmen such as framing carpenters need help from an engineer for a wide beam or similar weirdness but most of craft/art boils down to "grandpa put wall studs on 16 inch centers so I will too". Building codes for the building trades are written in human blood, not calculus math, for example. Somebody got electrocuted doing that, gets a line in the NEC or building code, we'd rather figure out the size of that weird beam using math rather than seeing if it collapses is structural engineering. Very few people write code in an engineering fashion where the entire process is predictable and heavily testable against reality and human lives depend upon it. Some embedded stuff like PID controllers in factories or anti-lock brakes are like that. Your average web framework CRUD app, not so much, who knows what it'll do, and when it fails thousands will not die in the crash/collapse.
- psyc 10y agoWe cannot retrofit these qualifications onto what have always been arbitrary titles, just because it sounds plausible. Imagine you are reading a candidate's resume. At one past job they were called "Software Engineer" and at another they were called "Software Developer". Nobody would presume to say to the candidate, "So, I see you did rigorous development with proper quality controls and metrics at Company A, but you did move-fast-break-things development at Company B?" You can't infer that from the job title, because the title is just whatever each company feels like calling programmers.