Ask HN: What are some thought-terminating clichés in the software industry?
https://en.wikipedia.org/wiki/Thought-terminating_cliché
* You can’t write JavaScript without jQuery (this one is dying).
* You can’t write JavaScript without a framework. Doing so will just create a new framework.
* You can’t write applications or get hired without writing classes/inheritance.
* Security certifications are worthless for security hiring.
* JavaScript is slow.
* The DOM is slow.
* Virtual DOM is a web standard, not some unnecessary thing created for the React framework.
* Accessing the DOM without querySelectors is like writing assembly.
* Complaining about querySelector speed is premature optimization.
* I don’t need to performance test because my application is fast.
* WASM will replace JavaScript... any minute now.
* WASM will gain full DOM access to the containing page.
(I am a man)
FAANG built the framework/language so it's going to be the market standard.
Not always inaccurate, but often used to overlook nuance.
- “That’s how the user wants it”
- “That’s how the boss wants it”
- “If it ain’t broke, don’t fix it”
- so called principles : KISS, DRY and so on
- “eval is evil”
- “early optimization is the root of all evil”
-
I swear to god if I hear one more "agile" buzzword from some washed out PM who has no reason to be employed....
So glad I don't work in devops or SWE
(Unless someone is really saying "use the right tool for the job, and for this job the right tool is always X". That I can see as terminating thought.)
It is good only if the phrase is followed by a discussion about why tool X is right for the job.