First there was mansplaining, now there's devsplaining.
‘Mansplaining’ “You Keep Using That Word, I Do Not Think It Means What You Think It Means”
More clearly. I don’t think you know what mansplaining means.
A guide for how to talk to a developer
41–45 of 45 posts
Re: A guide for how to talk to a developer
#421. Is this for real? 2. Here are exactly two things that you need to memorize in order to make this sort of talk productive: a) I don't know what X is, sorry. Can you tell me what that is/Can you explain to me what it does? b) I'm not sure I follow. I thought X is [...]/does [...], what am I missing? 3. Did anyone who actually knows what these things mean review these definitions? E.g: Vanilla: "Plain or basic, often…
>This sort of matches what an API is in web land, if you squint a little. If someone were to ask me what that definition describes, "API" is about the last thing I'd say. I struggle with defining simple things like this, and I think what author offers is a good generic way to define API. This definition includes any actual way I can imagine one can get (programmatic) access to generic service that does not belong to…
A user interface is how a person talks to software. An API is how software talks to software.
An API is like a restaurant menu, but for software. A menu tells a person what they can request from a restaurant. An API tells a programmer what their software can request from other software.
Re: A guide for how to talk to a developer
#43Earlier quoted context omitted.
>This sort of matches what an API is in web land, if you squint a little. If someone were to ask me what that definition describes, "API" is about the last thing I'd say. I struggle with defining simple things like this, and I think what author offers is a good generic way to define API. This definition includes any actual way I can imagine one can get (programmatic) access to generic service that does not belong to…
A user interface is how a person talks to software. An API is how software talks to software. An API is like a restaurant menu, but for software. A menu tells a person what they can request from a restaurant. An API tells a programmer what their software can request from other software.
Excellent definition.
The second part is true when there is a documentation.
Re: A guide for how to talk to a developer
#44Earlier quoted context omitted.
Except for the part where a bunch of the definitions are wrong, misleading, or woefully incomplete.
>Except for the part where a bunch of the definitions are wrong, misleading, or woefully incomplete. Examples?
Have you read this thread? I personally stumbled hard on the definition for Firebase ("essentially equivalent to AWS" -- I might be paraphrasing slightly since it's been a day).
Re: A guide for how to talk to a developer
#45First there was mansplaining, now there's devsplaining.
‘Mansplaining’ “You Keep Using That Word, I Do Not Think It Means What You Think It Means” More clearly. I don’t think you know what mansplaining means.
> More clearly. I don’t think you know what mansplaining means.
That is unnecessarily hostile comment.
I don't care what you think. I know what it means and you have exactly zero reason to publicly doubt that.