Posted on 04-09-2013
How To Get Your Grandma, Mother, Daughter and Sister to Understand APIs? You stop using gendered approaches when explaining what an API is. I’m not going to cite any of the past or recent examples of this (you know who you are). And I don’t care "how you didn’t even mean to do this", when you wrote your API example. There really isn’t a line between sexism and ignorant sexism.
If you really want everyone to understand what an API is, provide well written, plain english examples, that are framed around solving a problem your grandma, mother, daughter or or sister will understand--using problems they truly face in their lives.
It really is that simple. As long as you are using gendered terms to describe what we are doing, you are raising the barrier to entry. And when you do this, you are talking down to a person and making them feel small, stupid and all the other power trips that go with sexism. And yes, those thing are still there even if you "didn’t mean to do it".
So let ‘s make sure and keep API examples about solving problems and putting the valuable API resources to use, and not about gender, and get EVERYONE on board.
End of story! And if ever step over this line, call me out. I welcome it, cause I'm not perfect or exempt.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Swagger Visualization Layer Using D3.js
- Establishing Common Dictionaries That Industries Can Use In Their API Design
- Top 5 Most Popular Themes On API Evangelist In 2014
- Query Parameter Determining Which Fields Are Queried For API Call
- Now Our Development Environment Is Now Containerized And Scalable Like Our Production Environment
- Guest Post: Let Our Sponsors Blow A Little Smoke Up Your Ass
- API Discovery Continues Its Move Into The IDE With Eclipse Che
- Evolving Beyond Just Resources Towards A More Experience Based API Design
- Another View of The API vs. Data Download Model
- If You Have A Publicly Available Mobile App You Have a Public API