Well, I notice strong fears of being judged (and other emotions that I have determined to be from status concern) surrounding the correct use of grammar and such, so I thought there was a chance that other people would share it. That seems like a point.
I was also thinking that if I were actually not concerned about status I probably would have stopped capitalizing things at all and I would have considered making other changes. That probably isn't true, though, because the instrumental value of grammar is still really high if it's a status concern for other people.
I would.
Subscribe to RSS Feed
= f037147d6e6c911a85753b9abdedda8d)
Some relevant skills, off the top of my head:
Really, there must be lots of specific sub-skills, as the three I listed overlap to a large degree.
I initially thought I would be able to list lots of skills specific to software, and of course there are many, but they're relatively unimportant for being a good sidekick generally. For example, being able to provide clear instructions on how to reproduce a bug is incredibly valuable, but that's really just an example of the general skills I listed above, i.e. providing info that's unambiguous about what's wrong (and ideally why), not providing info that's irrelevant, and providing enough info so that they can most efficiently fix the bug.
Generally, being a good sidekick requires sufficient empathy and self-awareness. Empty because you have to know the mind of your hero to know how to best help them. And self-awareness because you have to know whether your hero's cause is really yours too. Tho, of course, some sidekick's cause is ultimately serving a specific hero.
In fantasy terms, a good sidekick delivers obvious monsters that the hero can slay.
In table top gaming terms you just described a good GM. I find it very interesting that there would be such a particular overlap.