"what other "myths" have you found consistent across the various development teams and companies you've worked for?"
That the technically best solution or tool is chosen. Almost every time, what tools that a team gets to use are chosen by 1) cost of license, or should I say the lack thereof, eliminating things like SQL Enterprise or ReSharper even when they're a clear win, or 2) cost of (re-)training people, or hiring new people who know the new tech. Maybe Vue or Svelte or even native web components are the best tool for a project, but business will look at how hard it is to hire people who know those vs React, or how hard it is to train everyone on such a thing. Just as no one ever got fired for choosing IBM, no one ever got fired for choosing Facebook's framework.
I recently worked somewhere that resulted from an almost 3-way merger of companies. After the resulting elimination of redundant personnel, we found we had more React devs/codebase than Angular, and that's why we chose React. It had nothing at all to do with technical reasons.
(I'm not trying to paint any of these decisions as bad -- these are sensible decisions. But they're the kinds of decisions that may rub devs the wrong way if they don't know enough how a business must operate.)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"what other "myths" have you found consistent across the various development teams and companies you've worked for?"
That the technically best solution or tool is chosen. Almost every time, what tools that a team gets to use are chosen by 1) cost of license, or should I say the lack thereof, eliminating things like SQL Enterprise or ReSharper even when they're a clear win, or 2) cost of (re-)training people, or hiring new people who know the new tech. Maybe Vue or Svelte or even native web components are the best tool for a project, but business will look at how hard it is to hire people who know those vs React, or how hard it is to train everyone on such a thing. Just as no one ever got fired for choosing IBM, no one ever got fired for choosing Facebook's framework.
I recently worked somewhere that resulted from an almost 3-way merger of companies. After the resulting elimination of redundant personnel, we found we had more React devs/codebase than Angular, and that's why we chose React. It had nothing at all to do with technical reasons.
(I'm not trying to paint any of these decisions as bad -- these are sensible decisions. But they're the kinds of decisions that may rub devs the wrong way if they don't know enough how a business must operate.)