|
|
|
|
|
by alex_c
5676 days ago
|
|
I agree that definitions are important, but most people's definitions of terrorism involve something going boom. I'm not as interested in coming up with my own definition as I am in using the terms and definitions that are least likely to be misinterpreted by the largest number of people. That in itself is a loaded topic... trying to redefine a term is usually either a losing battle (because people won't listen), or an underhanded strategy (because people won't notice). We don't always have the luxury of attaching a glossary to a conversation ;) |
|
The first thing you have to do, if you're programming inside a business, is come to agreement on terms. The initial thing most people try is some sort of dictionary approach, but after a while you end up realizing that a critical part of a project team's work is to create working definitions of common concepts. This is called the problem domain language (insert long talk which includes Ludwig Wittgenstein here) Words mean something because of the semantic web they are presented in. They have no meaning on their own.
So "Customer" or "Account", while sounding like clear terms, are actually the same problem as "terrorism" Unless you come up with (and own) a definition, analysis will be impossible because of contradictions.
Sorry. Slipped into teacher mode.
This is just stuff I do all the time, so I don't have a problem with creating working definitions, no matter what the topic is. I'd much rather be considered an oddball with my own definitions than circling my tail trying to pin down what things like "war" or "terrorism" is. Because if I'm creating my definitions, I can ensure consistency. Can't do that when you turn that job over to somebody else. Language is extremely slippery.