Let’s share stories where your automation efforts have been rejected and you can’t quite understand why! Here’s mine.

    • @DrakeRichards@lemmy.world
      link
      fedilink
      English
      210 months ago

      I’ve thought about it many times but can’t find a good way to implement it. I don’t have access to the company’s GitHub or any shareable network locations. Don’t want to upload to my personal GitHub either since there is proprietary information in some of them. Right now I have them shared in a OneNote notebook that I manually update as I revise the scripts.

      • Look, I can’t advise you to do one thing or another, but I’ll give you some career advice that has worked well for me: don’t ask permission. Most of the time, the documentation is out there on how to get what you want and you can do it yourself. I won’t have my work be wasted by someone else’s laziness. And if your direct report doesn’t like the idea, tell him you want to discuss it with his boss. Make your case to someone who cares. You have every right to make use of whatever tools will help you do a better job.

        What does making your case look like? It looks like making PowerPoint presentations, detailing a cost(man hours, oversight responsibilities, etc), detailing desired results, showing what impact this will have on the team, showing how long it will take to train your average joe on using these scripts, showing how much time can be saved.

        Your boss might be chilling because he’s waiting out the clock on his career. You’re not. Stand by your ideas, people will stand by you. But you will have to fight for your ideas, and you need to be comfortable doing that. I’m not saying it’s not hard, it is soul crushing to get your ideas shot down. But you can push through.