| Words are easier once you recognize that the official title of a person, product or organization actually communicates very little to people outside of the organization. Working in communications, I've seen many instances of groups using acronyms and catchy titles to brand (or rebrand) themselves. For example: - After much deliberation, a health care center decided to call its members "HARP," which stood for Health Advocacy Resource Personnel, to emphasize that they were focusing on preventative care. - A law enforcement unit changing a job title from Community Outreach Officer to Street Worker in an effort to show that they were concentrating on gangs in high-crime neighborhoods. Not surprisingly, no one outside of health care ever found out what "HARP" meant. And former gang members didn't build relationships with the police because some of them were called Street Workers. My point is this: changing a title can entice someone to learn more about your organization and its members, but the title itself cannot - and will not - communicate all the nuances of a position. That's the responsibility of a messaging campaign. I like that Hacker School has distilled the nuances of its members' roles into a blog post. The next step should be to develop focused messages that paint a picture of these students / hackers / developers / HackerSchoolers and what makes them unique. |
The primary reason to have a word is that we can have something to refer to ourselves (where "we" are members of the Hacker School community). I think most communities come up with words to refer to their members. It certainly happened in ours: there are a handful of words that people at Hacker School use to refer to themselves and new ones come up regularly.[^1]
The things to consider when figuring out what to call someone who does Hacker School is not what the outside world will think, but whether people who do Hacker School will feel comfortable wanting to use the word to describe themselves and whether we would be alienating anyone who would otherwise enjoy coming to Hacker School.
[^1]. The question of how much we as facilitators should try to influence that process is probably out of scope for this discussion. Let's just assume we've decided that we want to have some input. I can't resist footnotes, even in comments. Yeesh.