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
- Adding The OpenEd API To The API Commons
- PR People For APIs
- I Will Be At API Days in Paris This Week, Will You Be There?
- Government Services Schemas With JSON-LD
- University of California Student Senate Submits Bill Stating Student Information Systems Must Have API
- Generating The Utility APIs I Need For Each Developer Portal
- An API For Your Github GeoJSON Stores
- Server Side API Templates On AWS Cloud Formation And OpenShift
- Hypermedia In The Wild: Amazon AppStream API
- API Search Endpoint Using Solr