How to Get Shot as a Messenger: A Developer's Guide

How to Get Shot as a Messenger: A Developer's Guide

Famous messengers in history were celebrated for their bravery, but delivering bad news can feel like dodging bullets in the tech world. If you're ready to share the glory of being a shot messenger, look no further! Here's a foolproof guide to ensure you deliver bad news in the worst possible way:

Step 1: Ignore the Art of Reframing

Don't bother with that "growth mindset" nonsense. When you find a bug, emphasize its disastrous nature. Remember, a bug isn't an opportunity for improvement—it's the apocalypse!

Step 2: Hoard Information, Protect Your Territory, and Be Vague

Keep everyone in the dark and hoard information like a dragon hoards gold. Let them know your knowledge is your domain. And when you have no choice but to share, be as vague as possible.

Step 3: Make Sure They Know It's Personal for You

Channel your inner drama queen and ensure your colleagues feel the doom and gloom. When they ask how the project's going, hit them with, "Well, we're one bug away from ruining my life."

Step 4: Threat Them! Personally!

Fostering a sense of safety within your team? Pfft! Make sure everyone's on edge, dreading the moment they have to report bad news. Tell them, "If this bug isn't fixed, I'm holding you personally responsible for the catastrophe!"

Step 5: You can shoot yourself if they don't

Don't wait for others to shoot you down. Take any rejection or feedback as a personal insult to ensure you don't miss the glory of being a heroic messenger.

Step 6: Foster More Death-Defiant Messengers Like You

Encourage others to join your ranks of fearless messengers. Together, you'll strike fear in the hearts of the fainthearted. Let the timid minds quiver in fear as your clan conquers the entire tribe!

Sounds like a plan.

In fact, most legendary messengers in history successfully delivered messages that benefited their communities without getting hurt. Legendary stories like to emphasize the daring aspects of their approach. But that doesn't mean messengers don't get shot day to day. As we call for more messengers in our modern organizations to enable the flow of information, how do we train them to survive and thrive?

要查看或添加评论,请登录

尹哲的更多文章

  • Sprint and Iteration

    Sprint and Iteration

    In modern software development, "sprint" and "iteration" are terms often used interchangeably. Both represent timeboxed…

    1 条评论
  • Learning by Failures vs. Learning from Failures

    Learning by Failures vs. Learning from Failures

    SpaceX is celebrating its rocket explosion. In the world of software development, various attitudes toward failure…

    4 条评论
  • The Limitations of GPT and GitHub Copilot in Real-World Programming

    The Limitations of GPT and GitHub Copilot in Real-World Programming

    I'm writing this without having access to GitHub Copilot X. I'm not sure my understanding will be any different if I do.

  • Solution Wanted: Code for Cloze Question

    Solution Wanted: Code for Cloze Question

    A cloze question is an exercise used to help test a student's knowledge of a subject. It involves a passage of text…

    3 条评论
  • Meeting People at Agile Singapore 2016 Conference

    Meeting People at Agile Singapore 2016 Conference

    I work in the Odd-e Singapore team. My teammates Stanly, Stuart and Bas have been actively contributing to the Agile…

社区洞察

其他会员也浏览了