You'd need tremendous amounts of engineering for all those not to suck. And
engineering that's done by really experienced people. Too bad that people
desiging the "smart" part are from the same IT industry that thinks 3 or
5 years of experience qualifies as "senior".
I believe using a language "professionally" means being senior. Which is different from having a profession where you use said language.
On the one hand you're arguing you can't become "Senior" in 5 years, but at the same time you can become professional with 6 languages with little effort.
Your definition doesn't make sense. I've been labeled a "Senior Software Engineer". Does that mean that any time I write code in any language I'm using it professionally, while people who have been paid to write the same language for years but don't have senior in their title aren't using it professionally?
"The term also describes the standards of education and training that prepare members of the profession with the particular knowledge and skills necessary to perform their specific role within that profession."
Also from wikipedia, the second paragraph:
"In some cultures, the term is used as shorthand to describe a particular social stratum of well-educated workers who enjoy considerable work autonomy and who are commonly engaged in creative and intellectually challenging work."
The paragraphs you've pasted say absolutely nothing about the seniority of said professionals. And there is no indication that we're using the term as the described shorthand.
True, but it is also the price to pay when you use technology. You can't test everything. The TV, for example, is a new model from a big, quality brand (and in general it works well). Likewise, Call of Duty (the game that requires internet even if you play offline - not sure if this holds for all games in the series) is not a small title. So if these products by big companies have that shitty engineering, then most products with the same functionality probably will have similar problems.
It’s important not to excuse the business decisions behind that incompetence: someone knew about the problem and figured you’d buy it anyway because of marketing or everyone else cutting the same corners.
Not really. Usually the developers and mid managers are doing this to themselves, they say something like "we can't tell him or he will fire us" and the decision maker is not aware of any problems. What happens when I step in is that I tell them what problems do they really have and most of the time the decision maker really wants to fix them and isn't going to fire anyone (except for the incompetent mid-managers that caused these issues).
