Thing is - it works. Both online and in-person. I'd much rather be honest about how little I know (and often am when I'm working long-term with someone), but I've found it's a losing strategy in most situations. If you do know your stuff, you'll just get shouted down by idiots. Better to shout the idiots down first and then do the research to make sure you're not wrong. If you screw up everything, you'll probably get another chance simply by virtue of confidence (look at John Meriweather, who nearly brought down the global financial system three times and is still managing money), but if you appear timid and then screw up, people are all like "I knew he didn't really know what he was talking about..."
Prisoner's-dilemma problem: being honest about your level of confidence is better for everybody, but if other people aren't doing the same, it's worse for you.
An important example. Chutzpah beats expertise in that domain.
My favourite people are still those who state their conclusion, but will happily rattle off the list of assumptions they used to get there as well as how confident they are in that conclusion. But those people are pretty rare.
The same goes for why we may like extroverted people more than introverted types. Because with most extroverts, you're getting a relatively good impression of what they're about...because they're putting themselves out there (expressing their opinions); whereas with introverted types, you're using mental cycles trying to figure out what's their view/what do they want
There are no shortage of extroverts who aren't going to let not having anything to say stop them from saying it. On the other side of the equation, if you manage to persuade your introverts to share their conclusions, you can get a beautiful signal-to-noise ratio.
One might think that bullshitting only works with people, and that if you act over-confident/over-optimistic with the computer, it won't be impressed - but it is. When I've approached programming problems is an aggressive way, I learn more, see better solutions and perform better. There's still a need to clean up the disasters afterwards, and it does make me feel dumb to make mistakes - but it's a more effective way of learning. For me, timidity is a mistake.
Being so timid that I don't try anything until I understand it 100% perfectly is not as effective. But I do like timidity. It's more authentic and accurate.
PS: @nostrademons: that confirms something I wondered about you... :-)
I mean, become a cocky bastard who also knows his/her stuff, and have all the fun, rather than whining about how the cocky bastards have all the fun.
There's nothing wrong with being self-assured in what you do know, and honest about what you don't, but cockiness does seems to be a good indicator of an individual's ignorance of his (or her) own ignorance.
This is an interesting topic from a geeky point of view, since geeks tend to be the opposite of cocky guys like this. Geeks tend to be meek and have bad posture and avoid boasting. The downside of this is that some geeks manage to avoid ever being in a position where they have to stretch themselves to live up to their boasting. Competition and arrogance drive a lot of achievement.
As you point out, hacks only work if you iterate on them. You can't unit test social graces you can only have good exception handling. And good exception handling may come down to experience handling situations earned by actual trial-and-error and as this article says - a certain amount of cockiness.
At least if someone is confident and then wrong you can learn not to trust them. Someone who always hedges may never be quite as wrong, but is far less useful to a manager.
In an organizational structure it's not about one person being right, it's about the organization making a decision.
"A good plan, violently executed now, is better than a perfect plan next week."
-General George S. Patton
In short, he was the most arrogant, buzz-word filled SOB I ever had the displeasure of meeting,
After he finally got booted when people realized he didn't know a damn thing about technology I flat out asked the VP of engineering: "What did you ever see in him?".
He said: "You know, you're going to think I'm crazy, but he was exactly the same in the interview as he was around here daily, and I really thought that cockiness would mean he would take the lead on issues and be able to guide the younger guys".
So remember that kids, if you want to be seen as leadership material, thoughtfulness and pensiveness are not the way to go about it.
Just look at CTOs at companies you respect for further proof and see how many timid figures you find.