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.
"Software development has become too complex to do it without third-party frameworks."
Scale it
It depends.
I would say this does not have to be thought terminating.
Really it depends.
It’s a trade-off. Whether or not you qualify what it depends on.
It is opensource so if you need a fix do it yourself.
"It is best practice." or "It is industry standard."
“It is required in enterprise”
It's 90% complete.
Think holistically or You are not seeing the bigger picture
I don't think this is thought-terminating; unlikely to be the end of a discussion.
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.
These are more like lies developers tell themselves out loud, but I have heard them frequently enough they may as well be cliches:
* 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 saved your comment into my library.
Because it's harder and older it's better.
FAANG does it that way so it's best practice.
FAANG built the framework/language so it's going to be the market standard.
"Use the right tool for the job"
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.
My objection to this phrase is that it is tautological. By definition, there's never a time when you should be using the wrong tool for the job!
It is good only if the phrase is followed by a discussion about why tool X is right for the job.
”Responding to change over following a plan”
“Everything old is new again”.
Not always inaccurate, but often used to overlook nuance.
Lets make a spike for this
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
- “We’re going to try it our way and if it doesn’t work, we can always go back and do it your way”
- “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”
-
Kubernetes is cool
‘It’s too late to start over’
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.
Oh, poor men explaining the obvious in loud authoritative voices, believing they’re experts on any topic after 5.3 seconds of consideration.
(I am a man)
It's increasingly used to dismiss a man's perspective, regardless of if they're right and regardless of their tone.
In this interesting video from a 2016 Australian Senate committee, a minister objects to a female senator describing him as "mansplaining".
https://www.youtube.com/watch?v=TJyQpRfaGnw
"Use some common sense."
"Premature optimization is considered harmful", therefore, don't fix inefficient designs as long as they technically work.
"Don't reinvent the wheel."