If you're designing a bridge, this is pretty obvious work and it's pretty isolated. What I mean by that is that A) you're not going to go off and design bridges in secret and then sell those designs to someone who will build it in secret such that the public will later make use of the bridge. At some point someone in the government is going to ask why there's a new bridge over that river. And B) there isn't a huge world wide market for bridges that has near infinite sub niches in nearly every market imaginable.
So having a professional engineer license for bridges makes sense because if the license is lost, then it really does mean the end of your career.
Software is often an engineering artifact, but it's also like mathematics. And it's also like literature. You might be able to stop someone from selling their services directly, but you can't stop them from writing code altogether without forming a terrifying oppressive distopia.
So the Professional Software Engineer might not care about losing the license because they can still sell their skills to companies on the other side of the world where there is no regulation. Or they can create their own product that contains software and sell that product. Or they can publish their software on github and somehow make enough from tips that they don't need another job. Or they can get a job that doesn't require software development but can be highly augmented by it. Or they can make websites technologically unsophisticated users.
Losing the license doesn't mean that their career is over. It is only a slight annoyance. There's always going to be enough software engineers that aren't afraid of losing a license that the ones that are afraid won't prevent anything problematic from happening.
There are 10,000 virtual wires in the PLC that nobody cares about excepT for me and my coworkers in the same role, but the 30-40 physical relays and 1000 physical conductors in the power plant represented on schematics are reviewed by the customer and stamped by a Professional Engineer, because everyone understands they are expensive to change later.
Customers don't want to pay the additional cost to have their software stamped. They don't want to be told I can't fix that mechanical or civil design flaw in software because I don't want to open myself up to be liable for trying to help the customer get or keep their plant running despite some problems wiTh equipment supplied by others. People have this idea that software is easy to change. We can fix that later! Why decide now? It is a battle to arrive at the plant wiTh a complete, tested, documented control system, commission it and then shut the door and walk away. I have to be a really insistent about getting the information require to really complete my deliverables and then be very particular when other people's designs don't match what they delivered or work as intended. It is counter to my nature of wanting to solve problems instead of creating them or passing the buck, but that is what is required.
Sometimes I feel like this is cave drawings compared to other more mature fields. But maybe that's what boilermakers felt like 150 years ago.
As an aside, how does one get into a field like yours?
It is probably different on larger projects or when working for public utilities. All of the ones I have worked on are less than 50MW and are owned by corporations.
I think a lot of the automation field is learned on the job. you can take a PLC programming course but all you learn is the specifics of how to program that platform. It doesn't tell you what to program. That depends on the process you are controlling. I got in to hydro by working for a utility that owned a power plant as a student and then when looking for work after university sought out any opportunities for someone who liked programming and power plants. There are lots, but the catch is having the experience to get the job. I got in the door of a power plant by helping to program their datalogging and alerting system and then learned how to program the machines from a consultant who graciously provided me the on the job training and an owner who was willing to let me make mistakes.
Your base assumption that other countries than <your country> would not have regulation might be true at first, but probably not for long, and something is better than nothing.
I agree that people cannot be banned from writing software outright, but I think it is reasonable that in many situations it is reasonable that a company or agency is held to a standard that they only deploy software that has been produced through some set of engineering practices, similar to GAAP.
This is false. Bridges are large and have failure cases that managers and government officials understand.
Software is invisible and has failure cases that are completely incomprehensible.
Hiring a bridge designer from another country who is really keen on avoiding the background check will raise some eyebrows.
Hiring a nearly anonymous software engineer from who knows where is business as usual for many large companies.
Bridges have pretty limited use cases. There really isn't that many places to hide if your banned.
Software is in everything. Software is used by everyone. Right now it's big enough that people can make it through an entire career without actually knowing how to program (just make sure you move jobs every few years). It's only going to get bigger. Losing a license just means that it's time to job hop again. Maybe shift gears and become a process consultant. Losing a license in software is not a deterrent.
> something is better than nothing
We have a lot techniques to evaluate what a good way is to build a bridge. Right now with software the best thing we have is code smells. It just smells bad to me. We have no ability to objectively encode what makes code good or bad. We just "know it when we see it". Something can most definitely be MUCH worse than nothing.
They only think they understand.
> Software is invisible and has failure cases that are completely incomprehensible.
Which are becoming increasingly comprehensible with better tooling and data collection.
> Hiring a bridge designer from another country who is really keen on avoiding the background check will raise some eyebrows.
It does in software too; at least with serious companies.
> Hiring a nearly anonymous software engineer from who knows where is business as usual for many large companies.
These typically come through staffing companies because most large companies are awful at hiring technical talent. They have a long-term relationship with the staffing company and expect the staffing company to ensure the competency of the workers. I actually think licensing software developers would put an end to this; as it would give HR departments a relatively high-fidelity signal to sort the professionals from the hobbyists (by far the hardest thing for a non-technical person to do in hiring developers IMO).
> Maybe shift gears and become a process consultant. Losing a license in software is not a deterrent.
"Processes" are rapidly converging into off-the-shelf SaaS products, and the industry is actually starting to slow down quite a bit. Trust me, the Big 4 and similar management consulting firms are in for a world of hurt over the next 5 years as AWS, GCP and Azure start to hone in on the ERP systems and reference process space. Companies today would rather spend $1M and 2 months to implement a non-customized, off-the-shelf solution that can be maintained by cheap offshore resources than spend $30M and 2 years to build something custom that requires a dedicated support and maintenance team. Maybe there's some vendor selection and strategy up front, but all those companies that used to do process consulting just become system integrators (for guess what -- software!)
This data is generally fudged and hidden though by management in closed software products as well as being mislabeled.
And finally, users are not informed on how to report software issues and trained to normalize deviance - ignore problems and apply workaround.
Imagine for a moment, a world in which every git commit requires a permit from the county planner.
Also: You will not get agreement on what the GAAP practices of software are. This industry isn't that mature.
Hear, hear.
This point cannot be overstated enough. People have been building bridges for thousands of years. Software Engineering has only really been a thing for a few dozen years. We do not know what we're doing yet and it's going to be a very long time before we do.
Different domains almost definitely need different guidelines. Different ways of thinking might even need different guidelines. Anything we try to enforce now will be seen as embarrassingly dangerous in the future on the order of using radium for wrist watches.
Also, the cost of building a bridge is many orders of magnitude higher than the cost of designing it. The cost of producing software, by contrast, is almost entirely the cost of designing it. This matters. Legal regimes that don't respect the laws of economics (which are, after all, just corollaries of the laws of physics) are bound to fail.
You are making a huge strawman.
Further, losing your license is not the only or the worst consequence. (https://scholarship.law.edu/cgi/viewcontent.cgi?article=3165...) You also assume a civil liability which would be hard to prosecute for a non-licensed software engineer.
(And yes, if the 737 MAX 8 thing is officially reported to have a significant engineering failure, some DER is going to have a very bad day.)
Boss: "You know Mike, I think you might be right. We'll get Ken and Joe to take a look at it and see if they can't figure out a way to make it safe. After all, they saved the day with the last big project."
Ken and Joe proceed to hack something together that's super dangerous. Mike is isolated such that he won't notice what's actually going on with his previous project and then never given another raise again.
For bonus points make sure to put your engineers on projects that you don't mind cancelling and then asking them to do something dangerous. Isolate the ones that seem nervous or raise objection and give bonuses to the ones that are fine with being reckless.
The evidence shows that you cancel projects that Mike tells you are unsafe. And the record shows that Ken and Joe have a history of saving the day. "I had no idea that Ken and Joe were cutting corners. I'm not a software person, so I rely on my experts to tell me when things are unsafe. It's all Ken and Joe's fault."
The engineering law is very outdated, though (last modified in the 80s), but we're working on it. Some proposals I've seen would require a P.E. for safety-sensitive code in the automotive and aerospace industries.
The only time I heard of engineering licenses was that one Engineer in Oregon who fought a city and got fined for calling himself an engineer.[1]
[1]https://ij.org/press-release/oregon-engineer-wins-traffic-li...
For different PE domains: https://ncees.org/engineering/pe/
I do not see any EEs, MEs, or SEs.
"Every state exempts from licensure engineers whose practices fit within one or more of five categories: (1) engineers working under the supervision of a licensed engineer who takes responsibility for the unlicensed engineer’s work; (2) engineers employed by public utilities; (3) engineers employed by the federal government; (4) engineers employed by a state government; and (5) “in-house” engineers employed by a manufacturing or other business firm (known as the “industrial exemption”)." [0]
Many states don't differentiate the title of PE based on discipline (although you test with a specialty). If you search in the sos website, you'll notice all are just listed as a "Professional Engineer" license. It's up to the licensee to use professional judgement on whether they are capable of signing off on a specific system (e.g., while a ME may be legally allowed to sign off on an electrical design, they should know better than to do so)
[0] https://digitalcommons.liberty.edu/cgi/viewcontent.cgi?artic...
The result was not that nothing was done, but instead medical substances are used by non medical staff, doing unethical operations.
I think the same basically happens in the software industry: some of us have a pledge, but it just means little to nothing as anyone can replace us on the iffy parts, and we still build libraries that benefit any use.
It also reminds me of the “don’t use for evil” bit in the json license, where IBM kindly requested a special license to do whatever it wants with it.
I know there's lots of IEEE standards that cover good practices, but they don't seem to be as adhered to as, say, ASME codes in the oil/gas industry.
Maybe there's a slow change already happening. I know controls engineer licenses have become more common and NCEES now offers a software curriculum.
Compared to the alternative of protecting the engineer, that seems like a rather dystopian way to encourage doing the right thing.
However, because losing your whole career is such a horrifying prospect, companies are going to have a very hard time finding an engineer willing to break the rules. When you need an engineer to sign off on something, but no one is willing to, you might re-evaluate your stance.
It's the same as trying to find a lawyer willing to break the law, in a sense. As an engineer, you're beholden to the public first, and your employer second.
When asked to do something unethical, the P.E. has a choice: they can refuse, in which case they might lose their job; or they can comply, in which case they might lose their license altogether (and thus their job).