Remix.run Logo
fathermarz 2 hours ago

I think there is a fine line. YouTube is not critical software and no one’s life depends on the safety (putting mental health aside) of the code running. Some software engineers do however write code that is critical, but to your point, I don’t think they are ever considered liable.

I went through an acquisition as a Canadian software developer getting acquired by an American company. They wanted us to be called engineers like the rest of their SWEs but in Canada it’s a protected namespace. It’s illegal to call yourself an engineer without having the ring and the papers. Which personally I can appreciate.

m00x an hour ago | parent | next [-]

Youtube should consider their engineers responsible for the software they write. Big companies these days are just bureaucracy tricks and politics. There's a small handful of real talent, but they're quickly moving to new startups.

Also, I'm Canadian as well, and almost everyone calls themselves "software engineer" these days. You just can't say P.eng. in your title. You could be forced to remove it from linkedin/etc if you're called out, but it rarely happens.

cess11 15 minutes ago | parent | prev [-]

Once I worked in a company that had an ex-Googler on the board, who insisted on calling us engineers and wanted us to call ourselves that. In swedish, of course, 'ingenjörer'.

It's not a protected title in Sweden, but we still refused, because we were nothing like engineers. We were a minuscule team of mostly self-taught hackers who happened to be employed to solve business problems in a system for managing other companies and their customers. I had some idea of the rigour of engineering but my colleagues did not, still, they also weren't willing to appropriate the title.

This lead to meetings with this person being quite uncomfortable at times, embarrassing even. To me it was an obvious sign that they were unfit for managing roles. Two thirds of the team, me included, resigned at the same time after they had been increasingly active in the management of the technical department.

Since he was on the board the CEO could not get rid of him even though he knew that this person was destroying the dev team.