In general I would agree. But I have seen this used by leaders, which tends to end the conversation because what they are actually saying is "I'm in charge and I know better than you". Your holistic view has to be the same as their holistic view or you're wrong.
I'm going to disagree on this one. To me, this is telling you to think about which tool would be best. That's doesn't terminate thought; it demands thought.
(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.)
I usually see it when people are comparing two tools and can't come to an agreement. In that context, I feel it ends up being tautological in a way that stops people from digging into the real differences that make something the right or wrong tool.
Not specific to programming, but I've seen the thought terminating cliche "mansplaining" used more and more in the industry to completely dismiss a man's point of view.
35 comments
[ 3.7 ms ] story [ 81.6 ms ] thread* 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.
FAANG built the framework/language so it's going to be the market standard.
(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.
Not always inaccurate, but often used to overlook nuance.
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
- “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 am a man)
https://www.youtube.com/watch?v=TJyQpRfaGnw