What does user experience mean for Go code?

What does UX mean for Go code? The short version is, we should write code whose general intent is understood after a quick first read by any competent programmer.

Did that sound a bit like hand waving? Yeah, it might be hand waving. It's a standard problem with solving problems in any creative endeavor; you know it when you see it, and you feel it when it doesn't exist. Perhaps the main reason it is so hard to define is that the definition of competence varies significantly based on the members of the team and the environment. Similarly, the reason it is often hard to achieve is due to the fact that code inherently makes more sense to the author than anyone else.

But first, let's look at some simple principles to start off in the right direction.