Yeah. It was pretty awful early in my career. The good news is that "The person with an opinion has no power over the person with an experience."

As I've built up years of my own work experiences, I don't spend as much energy on each new idea I encounter.

Now I'm just proud that I still, once in awhile, significantly change the way I work, thanks to new information.

But, since what my team is doing works well already, I have to encounter the same advice from several trusted sources. And then we put it through a test sprint with a thoughtful team retrospective, after.

It's possible to find a happy balance, but it takes experience to get there.

Edit: So to answer the obvious question - what advice stuck with me?

1. Host team retrospectives. The rest of Agile is optional. Effective retrospectives are mandatory, because they're what tunes everything else correctly for my team and my organization.
2. Cherish plain text under version control. I've slept soundly many nights when others were up and working late, thanks to the simplicity and clarity of the process of reviewing what changed in plain text files. Any time a tool supports being setup with plain text files under version control, I advocate for that option.
3. Pick one thing that matters for today. It helps me focus, and forces me to really decide what matters, today. It helps me say "no" to requests that need to wait. And it helps me choose to give myself a break after I get that one thing done. One important thing per day adds up to awestriking levels of annual productivity, given reasonable opportunities.