This is something that if you do it right, no one knows. It works for me, because usually I forget what the secret was in the first place and you can’t tell someone something you forgotten.
If you explore why telling one person is a bad idea is because you can assume that that one person is going to tell one other person. If you tell no one, then you can assume that the connection ends with you and goes no further.
I like to think that perhaps, there is a possibility that the person telling me something in confidence probably is giving me a different story than the truth. Kind of what George did with Star Wars and telling Darth Vader to say something different than he what was in the script. In this case, there is a really good chance that if your version gets out, that you’ll probably be labeled untrustworthy.
The second reason is lost opportunity. It is better to assume that either a commercial or paid project is none of your business to discuss, unless it is your project or given permission.
Example:
Blog: hey, Waz up b1tches. I got this new jig where I write an application that will take over the world for an slightly evil (don’t ask, the last person that did, ended up in lava) dude.
The Next Day: Slightly evil boss dude throws blogger guy in lava.
I don’t know about you, but I would rather not be thrown in lava. That has to hurt, like nothing else.
Possibly Related Posts:
- Bullet: E-Book Library Management and Content Server
- Using ZendFramework 2 beta1 For Directory Project
- The Way of Kings and Cosmere Theory
- “In Time” Movie Premise Flawed
- Completing HTTP Library For PHP
Interesting post. What sparked this post? Don’t throw me in lava.