Comments on: TSQL Tuesday #052 – Argue Against A Popular Opinion https://clarkcreations.net/blog/tsql-tuesday-052/ Life at the Osburn Hideaway Sun, 16 Mar 2014 18:40:53 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: T-SQL Tuesday #52 Round-Up: Argue Against a Popular Opinion - SQL Server - SQL Server - Toad World https://clarkcreations.net/blog/tsql-tuesday-052/comment-page-1/#comment-12551 Sun, 16 Mar 2014 18:40:53 +0000 https://clarkcreations.net/blog/?p=938#comment-12551 […] Don’t Be That Guy […]

]]> By: T-SQL Tuesday #52 Round-Up: Argue Against a Popular Opinion | Michael J. Swart https://clarkcreations.net/blog/tsql-tuesday-052/comment-page-1/#comment-12550 Sun, 16 Mar 2014 18:02:04 +0000 https://clarkcreations.net/blog/?p=938#comment-12550 […] Don’t Be That Guy […]

]]> By: Les Noland https://clarkcreations.net/blog/tsql-tuesday-052/comment-page-1/#comment-12546 Wed, 12 Mar 2014 16:46:59 +0000 https://clarkcreations.net/blog/?p=938#comment-12546 All good points — nice job. In particular, I would like to stress the importance of #9. Admitting that one was wrong in both good for the soul and good for business. Context is important — if you work for a manager who fired the last guy who wrote a piece of code which deadlocked, you might want to use some caution in revealing your shortcomings. If you work with reasonable people, however, it’s an excellent idea:
1. Admitting you were wrong is liberating. You’ll feel better. Honest.
2. It gets you to “Right” so much faster.

When I discover that I made a mistake on something, generally:
1. I admit it quickly;
2. I fix the problem;
3. I apologize to those who were counting on what failed.

On occasion I have not admitted a mistake up front because it was such an epic-fail that I was too embarrassed to let anyone know. Generally, though, I owned up in the end — one thing I hate more than being wrong is being a wuss.

]]>