5 ms·
Programmers should not call themselves engineers (2015)
- ggm 3y agoThis is very dependent on where you study. British and Australian chartered engineering councils signed off on giving software engineers professional standing under charter, some time ago. it incurs costs, (CPD, amongst other things, and external degree compliance assessment) as well as consequences (professional indemnity, obligations in law for certain functional tasks undertaken in-role as an engineer) It's true the generic field of software engineering has some bogus stuff, but the actual quality of "you have standing against a professional board assessment" is actually there, and valuable (in my opinion) "You shouldn't call yourself a software engineer if you aren't chartered" might be a better take on it. My degree (1982) in computer science missed out on charter status by a year. I could have up-lifted but I was lazy. I do regret this sometimes. I would love to have been an engineer, purely as a personal achievement. I kept membership of the BCS until pretty much this year. Engineers in the BCS get a distinct grade of membership, with all the CPD and indemnity stuff, I was just a member. Humerous aside: There is a worshipful company of computer professionals in the UK, with official livery, and an order of precedence in the Lord Mayor's dinner, against the cutlers, the butchers, the goldsmiths. They do good works, Charity, and advance the cause of computer science. This is distinct from the British Computer Society.
- iaw 3y agoMy biased delineation engineering and everything else is whether you have to develop structure in the real world. Electrical Engineering and Computer Engineering definitely meet this criterion but Software Engineers rarely have to deal with anything but pure abstraction. It's like calling a Mathematician an Engineer IMO. At the same time the term is SWE so I'll go with it.
- robocat 3y agoThen most mechanical engineers should not call themselves engineers. Most electronic engineers shouldn't call themselves engineers. Follow the argument in the article, and most engineers in other disciplines are not engineers. Chartered institutes don't prevent damages nor help much with liability. Watch real disasters happen and work out whether (a) the registration of engineers prevented the risk or (b) whether engineers were the root cause. Use laws to hold people accountable for the safety of others - regardless of their academic tickets. It isn't as though engineers are the only discipline that can fail! In a modern world engineering and liability can easily cross international borders. Chartered institutions don't help much except within the borders of a country for home projects.
- bigyikes 3y agoTo me, engineering is about using math and science to solve problems by creating something under complex constraints. To exclude software from the field of engineering is baseless gatekeeping. I don’t care either way. I just call myself a programmer.
- jrockway 3y agoThe "Are we really engineers?" series really changed my mind on this: https://www.hillelwayne.com/post/are-we-really-engineers/ https://www.hillelwayne.com/post/are-we-really-engineers/ I put "programmer" on my tax return for years, but I say "software engineer" now. (I wish all I did at work was programming!!) It is all the same stuff. Someone has an idea, then you figure out how to make that a reality, along the way figuring out who does what, figuring out how long it's going to take, adjusting your plans when new information shows up, reacting to setbacks, etc. Whether you're moving concrete or bytes in RAM, the essence of what makes engineering engineering is the same. (Look at that building in San Francisco that is now tipping over. That's software engineering level of civil engineering! But it's all the same shit at the end of the day. A software engineer is surprised when Postgres doesn't hold up to their super cool new query that a million people want to run at once. A civil engineer is surprised when the geotechnical reports were wrong, they built their foundation the wrong way, and then their building starts tipping over. The common thread is that shit breaks and then we fix it.) I think people are salty because the stakes in software engineering are relatively low, but the potential to make money is nearly unbounded. Nobody is going to die if your ad targeting software has a bug, but you can make yourself billions of dollars if you get it right. Civil engineers are not so lucky. If your bridge collapses because you messed up the math, that's something you have to live with. And people will only pay so much money for bridges. So that's definitely "unfair", but them's the breaks. At least you can point at what you made and say "I made that". When it doesn't collapse, people are going to be a lot more impressed than the software engineer with really good ad targeting.
- MrJohz 3y agoI second the Hillel Wayne article, and the whole series he wrote on the subject. It's a really good exploration of what engineering looks like in different disciples, what software engineering can learn from other engineering disciplines, and what other discipline can learn from us. I think people hear engineering and jump immediately to a handful of big professions like aerospace, or civil engineering, and build their view of engineering entirely based on that: very controlled, very life-or-death, everything needs to be done correctly, etc. But that's kind of like assuming that what Google is doing is representative of all software engineering. And while it's true that software engineering is probably one of the less mature branches of engineering, there are things that we do a lot better than other disciplines, like change management (i.e. git), or automated testing.
- oldnewthing 3y agoPaywalled article but ... IMO: 1) Software Engineers should follow structured processes and methods to solve problems. They might look different: state charts, sequence diagrams, formal methods, SDLC etc. However, they often don't because expediency wins over correctness. Where it does matter such as process control systems, embedded systems, they do follow these processes rigorously. 2) That said, there are a lot of folks who may not be aware of these methods because they didn't receive formal training. That is the beauty of our field; you don't need somebody to certify you if you can invent solutions and solve problems. I will refer you to what happened to the author of strongtowns.org. https://www.strongtowns.org/journal/2023/1/30/lawsuit-update-engineers-minnesota-state-court-appeals#:~:text=Members%20of%20the%20Minnesota%20board,state%20order%20against%20Strong%20Towns https://www.strongtowns.org/journal/2023/1/30/lawsuit-update.... So, no, I beg to differ. We don't need a board of wise old men lording it over the rest of us. 3) We are conversing on, reading the article via, accessing content over the Internet. This is public infrastructure. Without the software engineers who invented/built BGP, TCP/IP, SNMP, etc., we would not be able to do this.
- nsonha 3y agoWhat I have a problem with, is "software engineers" calling themselves (just) "engineers". Sounds incredibly ignorant.
- sho 3y agoMeh, a lot of these kinds of articles seem to be written by civil engineers with a chip on their shoulder and defensive about the use of their title. I don't buy it. Yeah, we don't have certification and all that kind of stuff yet - because it's too new and no-one really has a final, bulletproof idea of "this is how X should always be done". But to me, engineers are people who build important stuff, that a lot of people rely on, and for which there will be severe consequences if it is built wrong. A lot of software falls into that category. Words evolve, I don't feel like I'm putting on airs describing what I'm doing as engineering (sometimes!), and hence I don't feel like some kind of pretender describing myself as a software engineer. Also, there's a quote I love, although I can't name the source: "engineering is about tradeoffs". Well so is software development, all day every day - in fact it's the mark of real experience knowing where, when and why to make those tradeoffs. Sounds like engineering to me.
- airbreather 3y ago"Build important stuff" - to predictable budget, schedule and safety outcomes is the bit you forgot. Dont care anout certification, but when you can "engineer" a solution that takes account those three factors you can call yourself a professional engineer. Certain engineering standards require managed competencies, eg functional safety and equipment for explosive atmospheres, certification is probably the easiest path. Most people who say, "meh but we are engineers because we make stuff" really don't have the first clue how engineers do engineering.
- m00x 3y agolol, predictable budget and timeline. McKinsey’s found that 98%+ of construction projects run ahead of timeline, and 80% run over budget. Software engineers also have those requirements, but we try to keep our estimates to small chunks instead of 5+ years. You're a P.Eng when you can pass your country's certification. That's it, it's just a title.
- vasco 3y agoI took EECS in university. I can work on power systems, electronics, communications, and I'd have a certification from my country's entity that regulates engineering. I can also work on hardware, software and generally programming, but for that side according to people like you I'd just be a dude flinging code around. But I have all the same training in both scenarios. Why would I be "better" at engineering if I'm looking at fiber cables or an AC generator but not python? I learned the same techniques, the same safety practices, the same thinking models.
- rurban 3y agoIf they are just hackers they should not. If they are doing engineering (with Hamilton being the first) they may. It's not a protected title thankfully. We are not in the middle ages anymore
- 000ooo000 3y agoAs a dev, currently I agree with the premise - I've gone back and forth over the last few years - but this article was kind of painful. Reads as more gatekeepy than convincing. The author is neither an engineer or software developer, so I'm not sure I trust his ability to assess it from either side, either.
- PrimeMcFly 3y agoI'm fine with software engineers calling themselves engineers, even better if they actually have some sort of license. It's only really a problem when you have, for lack of a better term, codemonkeys calling themselves engineers, because they are not engineering anything.
- deleted 3y ago[deleted]
- eduardojusti 3y agoIf software can be reverse engineered, we might as well call those who built it “software engineers”. However, I don’t mind if people refer to me as a “programmer” or “developer”.
- dave333 3y agoSoftware is often obsolete quickly and at the same time it's more complex than the design of structures like bridges.
- nicechianti 3y ago[dead]
- kazinator 3y ago> Though to me, engineers are people who build bridges and follow pretty rigid processes for a reason.” What are people who design a hairdryer or an engine block?
- kazinator 3y agoYou're an engineer if you burn some fuses in a FPGA chip to get a behavior. You're just a hacker if you write a program which does the same thing and write it into an EEPROM.
- kgeist 3y agoWhen people argue about precise meaning of words they often ignore the fact that words can be polysemantic (in fact, most words are). It's totally fine that the word "engineer" in "civil engineer" and "software engineer" has different meanings. Meanings of "engineer" according to Merriam-Webster: 1. a member of a military group devoted to engineering work 2. crafty schemer 3. a designer or builder of engines 4. a person who is trained in or follows as a profession a branch of engineering 5. a person who carries through an enterprise by skillful or artful contrivance 6. a person who runs or supervises an engine or an apparatus
- toxik 3y agoSo clearly 2 applies to Scheme, 3 game engine programmers and kernel hackers, 5 most of us, and 6 almost all of us.
- throwawaaarrgh 3y agoguess I'll start adding "Doctor" before my name now. if anyone questions it I'll say it has a different meaning when I use it
- z3dd 3y agoit's a thing already https://en.wikipedia.org/wiki/Doctor_of_Philosophy https://en.wikipedia.org/wiki/Doctor_of_Philosophy
- kgeist 3y agoEtymologically, "engineer" originally meant "one who designs, constructs, or operates military works for attack or defence". I guess at some point some folks were also grumpy that the word was generalized to people who had no relation to military :)
- ginko 3y agoI have a masters in computer science from Vienna University of Technology in Austria. This gives me the title “Diplom-Ingenieur” (diploma engineer) which according to Austrian law essentially becomes part of my name. I can (but don’t have to) add my title to my passport, drivers license etc. It’s also added in legal documents. To say I’m not allowed to call myself an engineer because my field is not rigorous enough just feels like a weird form of gate keeping.
- erikerikson 3y agoBeing an engineer means designing something in order to guarantee outcomes within operating conditions and the proper behaviors outside of them. There aren't a lot of engineers who work that way and even fewer managers that are willing to support it but we exist.
- acqq 3y agoAt least I am an actual computer engineer with a degree in computer science. I’m certainly not unique. What others do I care less.
- nathias 3y agowhy do US people have this magical relationship with language? like the concept doesn't matter but the actual term is very important ...
- chmod600 3y agoAs long as we're arguing about words, let's discuss the word "should". "Should" is often used as a way to express advice, as in: "if you are a programmer and want to make more money, you should call yourself an engineer". The HN title seems to be using a different definition of "should", or is perhaps expressing advice to those among us who don't care about money.
- nirui 3y ago> Traditional engineers are regulated, certified, and subject to apprenticeship and continuing education. Engineering claims an explicit responsibility to public safety and reliability, even if it doesn’t always deliver. The author probably don't know that the Chinese government actually demands similar terms too: you are not allow to sell a piece of software unless the software passes a few certifications, and you must hire enough employees graduated for few government recognized majors/professions in order to start a tech company that's allowed to request those certifications. So I guess China could be a dream country for the author of the article. Welcome BTW. Of course, the entire article was written by someone who has a half-knowledge on what's actually going on, resulted in a flamewere. The mentioning of data breaches can't cover the fact that most software (or digital control systems in general) worked very well, you don't hear from it because there are no people complaining. It can be very problematic if one judges things only based on headlines, because the resulted reasoning might collapse as soon as someone else applies the same logic elsewhere. Say, why a well-engineered dam, built by fully certified engineers with their state-of-the-art disciplinary knowledge, meticulous calculation plus simulation and rigorous construction still failed and caused many lives? Are dam engineers not engineers? The dam engineers would probably come out with some excuses such as real-world complexity, and they would be damn right. Handling a dynamic system is hard, and software engineering is full of it.
- okaleniuk 3y agoI've been wondering myself whether "software engineering" is a misnomer. We have so many of them in software engineering. What if creating software is closer to investigative journalism than to building bridges? Consider this, a small subset of professions falls under the umbrella of engineering. There are chemical engineers, mechanical engineers, electrical engineers etc. There are no sports engineers, law engineers, or literature engineers. Some people activities are just not engineerable. This doesn't make them any less important, so I deeply disagree with "programming cheapens engineering" statement. And it's not that software is a novel concept. In fact, the very argument that software is new and is not yet properly regulated is becoming old. Software is older than spaceflight, computer tomography, and mobile telecommunications, - all heavily if not excessively regulated. Somehow, creating software dodges most of the attempts to make it into an engineering discipline. Somehow, most of the norms and rules we invent don't pass the test of time. There is the SWEBoK, there are also ISO standards for computer languages, and their use, but the art of programming still remains orthogonal to the standardization effort. Most of the software outside safety-critical systems is still created by artisans and not engineers. And... it's ok. Maybe you don't need a license to write a yet another dating app. So maybe software engineering is indeed a misnomer. Like a racoon dog, a guinea pig, or MTV.
- KevinMS 3y agoI never thought of it as engineering. Its the act of describing to a computer exactly what you want, and simultaneously explaining to readers what is happening. Sounds a lot more like writing to me.
- okaleniuk 3y agoThere is a notion that programming is an extreme kind of poetry. Like with haiku, where there are rules, and the rules are formal, you can ratify an ISO standard on haiku rules; but they only support the structure and not the sense.
- drbig 3y agoMy take on this has always been that contrary to any other engineering field even the fundamentals change at a relative blink of an eye. A Roman-era civil engineer transported to _now_, a good 2000 years into the future, would still find gravity working exactly the same, concrete working the same, and will not find any of our modern architecture truly alien or incomprehensible. Computers? Take a programmer form merely 50 years ago and: CPU executes instructions one by one? Nope. You program starting from hardware? Nope. A JavaScript framework collection? Completely alien. Imagine best practices for bridge building if gravity was variable and susceptible to fashion cycles.
- codelikeawolf 3y agoI spent 4 years getting a degree in mechanical engineering while also working full time as a Manufacturing Engineering Technician (my company wouldn't drop the "Technician" in my title until I had the degree, even though my duties were the same). After I graduated, I got a job with the title Product Engineer, which was essentially mechanical engineering. When I moved over to the software world, I didn't really notice an appreciable difference from the work I was doing when I had "engineer" in my title. You're still solving complex problems, accommodating for edge cases, and translating requirements into deliverables. The only differentiator is that I went from producing something physical to something digital. So I call myself a "software engineer" without really thinking about it. Nobody ever blinked an eye when I said I was a mechanical engineer. Nobody dug into whether I was accredited or licensed. One could argue that distinguishing between a programmer and a software engineer is analogous to a drafter vs a mechanical engineer, but that seems wrong too. At the end of the day, you can call me whatever you want as long as the check clears.