I'm seriously of the opinion that allowing HR departments to call programmers "engineers" was the single biggest mistake the tech industry. They aren't. They generally have no idea how to engineer anything. They don't understand risk-benefit analyses. They don't understand that in the real world, 'efficiency' and 'optimization' which address only one variable solution spaces are neither efficient or optimized.

And we've put them in charge of our econony and our government because they are really good at making things that have less features, but at least cost more and run slower!

Unus Nemo reshared this.

in reply to Blaise

@Blaise


There is a clear distinction between a develop and a Software Engineer/ Architect. Yes, you need to be a developer or programmer to become a Software Engineer/ Architect but that does not make every developer an engineer. If you HR department does not realize that then I feel sorry for your company, and your developers (I doubt they are actually programmers) as they will have more than they are capable of expected from them.


Unus Nemo

This entry was edited (yesterday, 11:58 AM)
⇧