In my humble opinion, being monocultural as a developer is a path to obsolescence. Be T-shaped: know your specialty really well, but also a bunch of stuff more superficially.
If you have a little hands on experience with Go on top of your Java expertise, you are imo more valuable to your employer. They may even be mid transition from Java to Go, where you would be very useful indeed.
Besides, it’s just healthy to keep learning new things.
I am a dev, and I enjoy the odd distraction. Sometimes. But not when I’m in the zone.
It’s not about being a dev or not being a dev. It’s about whether the tasks you are doing require you to hold a lot of state in your head. Sometimes you can’t write everything down. And when someone calls you in for a quick chat about TPS reports, all that state is thrown out and has to be rebuilt from scratch.
If I’m writing a short script where I can find my place again just by reading the screen, it’s not a problem. Me mentally refactoring code that goes across dozens of files and isn’t documented anywhere? Please, I’ll need some focus time. As a dev I’m not always in flow state, but when I am, I prefer if you let me finish what I’m doing.