3 ms·
Substitute "underlying causes" for "root cause" and be on your way. Yes, precision in language can be important, but letting it get in the way of being useful i
by grzm 7y ago
Substitute "underlying causes" for "root cause" and be on your way. Yes, precision in language can be important, but letting it get in the way of being useful is throwing baby out with the bathwater. You can see the same thing happen when people get hung up on precise definitions of agile implementations or pedantically quibbling over terms like "serverless". I personally get annoyed when people misuse the phrase "steep learning curve" when referring to something that's difficult to learn. But you know what? I still know what they mean, and that's the point. I set my annoyance aside, move past it, and decide to focus on getting something done.
- xapata 7y agoI can see your point, but letting those slide can cause trouble down the road. Today I had trouble with a codebase where the `Configurator` class was not doing any configuration. When the purpose changed, no one bothered to change the name. Careful naming prevents leaky abstractions, or at least they leak less. Call me a lawyer, but I appreciate precise use of language.