I just like my stack, which includes Go. That stack is of course ever changing, but why would I make a drastic change if I’m already both happy and somewhat good?

I’ve been recruiting people and had exposure to small sample of generalists as an interviewer, but also in a team. Not too long ago, I’ve been briefly exposed to „staff” level Go developers who, I kid you not, would not follow ANY known and widely accepted as best practice Go convention (that I could identify). Obviously these were Java, C#, Python developers bringing habits from their last language to that project and boy was it bad. I suppose that was an extreme end of the spectrum (they were also incredibly toxic), but not once before were I in a team where new code was that bad. Of course, best practices are there to serve you and not the other way around, but each time I’d ask, they couldn’t explain why in a coherent way.

I suppose once you know programming it’s kinda easy to change the syntax, but imo code is just significantly better if people know what they are doing.