kcexn

The grading rubric for all engineering units here in Australia require that students develop an understanding of ethics and professional practice. There are a number of units dedicated to teaching project work, legal, and business aspects of engineering.

Typically the software engineers also do more maths than CS students. Reasoning from first principles is an important skill for professional engineers to have.

Huh. This reminds me of the asymptotic equipartition theorem. Samples taken from higher and higher dimensional spaces will concentrate into a typical set.

Does model performance also concentrate into a 'typical case' where things work pretty well and a non-typical case where it's completely unpredictable as the number of parameters increase?

That's also plausible.

No. The official report seems to suggest that software in IMS core (the subsystem that controls VOIP signalling in the mobile network) bugged out after the time was shifted back 20 years. That doesn't narrow down the specific failure that stopped calls from going through very much. IMS core is full of timers, but it could also have been a license server issue for all the report said about it.

I think most of these problems could be solved through contracts.

A contract for purchasing Parent Co.'s HR, legal, and compliance expertise for child co.

And a contract for sharing technology infrastructure.

The terms and pricing of the contract would likely be strictly regulated to prevent preferential treatment and encourage a clean separation over time.

I'm not a lawyer though, so who knows.

It's still impressive, but it's not enough.

Australia's bar for skilled employment is pretty low and deflates wages as well. That's before we get into the prevalence of exploiting working holiday visas for practically slave wages.

You can't really force someone to work for X years at a place they don't want to. I don't know if what you're describing is an enforceable contract term.

I mean. That's how profiteering works for the most part. Extracting wealth from people who don't know better is many times easier than creating more wealth for everyone.

Most hardware tinkerers are not EE's. But will rely on EE's to certify that their electronics are safe.

You don't need to be an "Electrical Engineer" to do simple design work like this.

Professional Engineers are qualified to take on more liability than just creating a design. So you don't need an Engineer to design a product, but (depending on jurisdiction) you will need an engineer to certify that your product won't hurt or kill people.

If you do a lot of design work, then you may want to hire a Professional Engineer in-house so that your company has more confidence that they will produce compliant designs with fewer iterations.

Engineers are often the best people to work with if you need to do things that are done infrequently since theoretically, they're trained in the prerequisite first principles so they can make judgments that are rooted in rigorous analysis in addition to their practical experience.

If you can call yourself an Engineer if you feel like it, then it's not a protected title.

"Doctor", is for instance a protected title. You can not advertise yourself or your services as a doctor unless you're a qualified and practicing medical professional. I believe some kinds of legal practices are the same.

I don't think Software Engineers in the US would sign any documents that expose them to legal liability as a professional engineer either.

It's still not clear to me from this discussion whether the term "Software Engineer" is legally protected in Germany (or any other European country) or if it's just a cultural convention.

The distinction is basically, if a software developer started a consultancy developing custom software solutions and called the company XY Software Engineering, would they be penalized for false advertising if they didn't have professional engineering qualifications?

In which countries are Software Engineers not allowed to call themselves engineers unless they are professionally qualified engineers?

I think most people who write code are the latter and not the former. The industry has diluted the term "engineer" so much that they maybe don't even realise that traditional engineering projects are about more than just implementation work.