[bryanrasmussen]

I agree that is what it looks like from the outside to people who have no experience at it, but I doubt that is what it looks like at all from the inside. Just as from the outside a programmer might look like a sweary toddler who keeps you from messing up his toys out of pique.

I may have told this anecdote before, if so here I repeat it:

There was a Friday meeting at a place I was consulting at, the C-level executives were outlining the way projects would run to the end of the year. It seemed in some ways less than optimal, they then in a rare bit of insight into their processes said 'I know this looks less than optimal but the reason why we are doing this is ---blah blah blah 3 sentences of finance technobabble'.

It was quite clear the suboptimal process had been chosen to maximize available moneys for projects due to accounting decisions and specific legal regulations. Although exactly how eluded me.

I was pretty sure that most of the people there understood as little on the matter as I did but everyone did that expression on their face to signify they did understand that people generally use with me when I describe how stemming/decompounding works and why this means we will have to take another way in structuring our data for the search engine.

But yes most of the time I would look at those people and say that they don't do anything.