Brogrammer: “I can’t be bothered to change the words I use to discuss my profession just because it makes a few people feel included”
Same bro: “I have renamed this same function four times now so it properly conveys its purpose.”
Same bro: “I have renamed this same function four times now so it properly conveys its purpose.”
Words matter. Nuance matters. Naming is hard. But ultimately:
^ YOU CAN NOT BE GREAT AT SOFTWARE IF YOU DON’T CARE ABOUT HOW WORDS FORMS IDEAS IN THE MINDS OF OTHERS.
^ So if your take on “craftsman”, or “master/slave” or any other term that makes a colleague feel unwelcome isn’t “let’s find a better word!”, either you’re shit at software because you don’t get how important words are or you get it & you find the exclusiveness to be a feature.
^ Good Morning ☕️ 
^ If you enjoyed this tweet, you may also find this one to your liking:
^ This thread on the history of the word "craftsmanship" during the authoring of the agile manifesto in 2009 covers the specific controversy over that word at the time & gives a strong rationale for why it should never have been used. Please read 🙏
