|
-
November 19th, 2008, 05:40 PM
#31
Re: Thread topicallity, accuracy and integrity....
 Originally Posted by TheCPUWizard
* Say "The Heck with it"
* Inform BOTH the original novice and the person who jumped in of the ramifications of the information
If the second novice employee works for someone else, then it might be out of line to correct them.
In my opinion, the person receiving the information is going to have to make a bit of a judgment call on whose information that want to accept and use. They are to take it as advice and not necessarily as absolute truths.
One of the points your argument leaves out is... what if the senior person is wrong and the other novice person actually -is- correct? All of the sudden, where the Sr. person thought they were doing a good deed results in obfuscating the entire issue and making a situation even worse.....
Last edited by gstercken; November 19th, 2008 at 06:34 PM.
Reason: Added closing tag
-
November 19th, 2008, 09:31 PM
#32
Re: Thread topicallity, accuracy and integrity....
 Originally Posted by Brad Jones
If the second novice employee works for someone else, then it might be out of line to correct them.
That is true, but "in the real world" I would then go to their boss, or a peer person in that chain of command or a common supervisor. I believe that when a company hires someone they deserve the best, and this includes pointing out even "potential" bad information (see important info at end of post!!)
In my opinion, the person receiving the information is going to have to make a bit of a judgment call on whose information that want to accept and use. They are to take it as advice and not necessarily as absolute truths.
This gets back to the matter of "trust". Obviously no one can control what information a person accepts or rejects.
One of the points your argument leaves out is... what if the senior person is wrong and the other novice person actually -is- correct? All of the sudden, where the Sr. person thought they were doing a good deed results in obfuscating the entire issue and making a situation even worse.....
I am very open with clients and teams that I work with. I tell them up front that I have probably made more mistakes than any (small) group of them. These days, most of them are caught before someone else is even aware of the mistake. The ones that do "leak" into the wild, are typically incredibly stupid, embarassing or both. [Imagine standing on the desk of a naval vessel having just watched the crew in near-panic after the main gun just rotated violently and slammed into the desk (Dutch M-Frigate 1992) and going "Oops....me bad"]
TheCPUWizard is a registered trademark, all rights reserved. (If this post was helpful, please RATE it!)
2008, 2009,2010
In theory, there is no difference between theory and practice; in practice there is.
* Join the fight, refuse to respond to posts that contain code outside of [code] ... [/code] tags. See here for instructions 
* How NOT to post a question here
* Of course you read this carefully before you posted
* Need homework help? Read this first
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|