Comments on: Intellects Don’t Appreciate Intelligence

By: Mike

Mike — Tue, 20 Oct 2009 17:29:34 +0000

My opinion is that these people, who dont appreciate intelligence, are NOT intellects. ANYONE can take an opposite position on any topic. And many do, just for fun it seems.

It doesnt make them an intellect. In my opinion, it makes them a-holes because they’re too hung up on their insecurities to admit they’d be interested in learning something. I grew very tired of listening, openly, to others’ experiences – trying to learn from THEIR fortunes (or misfortunes), alike.

I dont have all of the time in the world to make mistakes – why not learn from others’ mistakes – right?

Sadly, most people are not like that and will take every effort to cut you down. This is why I no longer work in captive employment. I work for myself, out of my house, alone, and surround myself with whom I chose to. Folks at the same and better experience and intelligence levels. I will never continue to learn if I spent 90% of my day trying to convince others that 2+2=4 when they’d much rather take personal gain from disputing such.

By: FlorianO

FlorianO — Tue, 13 Oct 2009 18:31:53 +0000

Its way more difficult. Every Person has a different state of personal development. But its not a linear kind of development! Its more like a huge disc with 20.000 different areas. (imagine this!) And in each of this areas one has a certain development. If you are never gone through configuration hell you cant understand grails awesome-ness. If you never defined logic in XML, you cant appreciate Maven/Gradle! Thats the main point i discovered while working with smart people. They cant value your work because they didn’t have your experience! Even if you explain something totally logical to them, they cant value it. They have mostly a different perspective on IT.
Thats the reason why it is so important for me, to keep contact with the handfull of guys which have a similar perspective and similar experience!

By: Reedo

Reedo — Tue, 13 Oct 2009 12:18:10 +0000

One effect of intelligent work that’s really under-appreciated is the avoidance of problems and/or the reduction of risk. It’s intelligent to double-check critical code for logic bugs, include handling for anticipated error conditions, and attempt to never leave data in an inconsistent state. Not all “intellects” appreciate these tasks.

By: Philip

Philip — Mon, 12 Oct 2009 17:42:09 +0000

I disagree with your base assumption – the one you say “it’s true, but why?” about. another question is “is this true?” I say not really.

It’s People, not “intelects”. Most people seem not to appreciate the journey taken to discover truths that seem self-evident in hindsight. Or even things that seem semi-obvious, or even mostly correct.

The big differences are, that people you consider “smart” are more likely to see the correct answer as obvious.

The *actually* smart people I’ve had the pleasure of working with actually grasp your journey when you give the answer. Not only do they respect it, but they understand why you are making the assumptions you are.

There is also the political aspect to consider- admitting you worked hard to come up with a good solution is damaging compared to implying “I could have told you that”. Working in a place that fosters this kind of subconscious reaction is harmful for you and the people you are writing about.

By: Max Pool

Max Pool — Mon, 12 Oct 2009 13:41:12 +0000

@DGentry –

Actually, I don’t see that being the other side of the coin at all. My view of the situation is that they only respect their own ideas and are frequently complaining that ideas aren’t heard because there is work going on around them that they didn’t dictate.

Now I am thinking I need to write a post about control freaks… :)

By: DGentry

DGentry — Mon, 12 Oct 2009 10:46:14 +0000

Do you have any thoughts on the flipside of this problem, the developer who publicly complains that their co-workers do not pay enough attention to their ideas? (i.e. frequently complains).

I worked with such a person. He was incredibly corrosive to the team dynamics, expecting any discussion to end the instant he proposed a solution. These were not issues that he had studied in depth to analyze, he simply believed his initial brainstorming was always optimal.

He is actually the source of one of my new mantras: No one is so indispensable that they can be allowed to destroy the morale of the team.