A Punny Take on API Documentation and an Overqualified Mail Carrier

Description

A four-panel comic from 'WebDev Toons' titled '#114 - MISCONCEPTIONS 9: POSTMAN'. The comic illustrates a humorous misunderstanding based on a pun. In the first panel, a male developer with black hair sits at his desk, pondering, 'NOW HOW DO I WRITE THE DOCUMENTATION? MAYBE I SHOULD GET POSTMAN...'. In the second panel, a female colleague in a yellow dress excitedly sings the classic song lyrics, 'Stop! Oh, yes, Wait a minute, Mr. Postman!!!' as a literal mail carrier walks by. The third panel shows the mail carrier, now sitting at a desk, giving the developer expert advice: 'SINCE YOU'RE USING KUBERNETES FOR DEPLOYMENT AUTOMATION, YOU MIGHT WANNA USE A YML TO DEFINE ENDPOINTS, THEN...'. In the final panel, the original developer looks pleasantly surprised and confused, stating, 'WELL, I WAS TALKING ABOUT THE SOFTWARE BUT HE'S ACTUALLY PRETTY GOOD!', while his female colleague gives a thumbs up and exclaims 'YAY!!!'. The humor stems from the developer referring to the Postman API platform, while his colleague's reaction summons a real postman who, unexpectedly, is also a skilled DevOps engineer. It's a joke about the ambiguity of technical terms and a wholesome twist on the 'misconceptions' theme

Common Tags

API ApplicationProgrammingInterface DeveloperHumor PostmanCollections Documentation Kubernetes Yaml DeploymentAutomation

Comments

Anonymous ★ Top Pick The real test isn't if the postman knows Kubernetes, it's whether his YAML is properly indented. That's a special delivery

Anonymous ★ Top Pick

The real test isn't if the postman knows Kubernetes, it's whether his YAML is properly indented. That's a special delivery
Anonymous

Told the team to hand the API docs over to Postman; a literal postal worker showed up, white-boarded an OpenAPI spec, and reminded us that 400 ≠ “success but empty.” We kept him - first stakeholder who’s ever delivered on time
Anonymous

The real irony is that after 15 years of explaining REST endpoints, we still can't explain to non-technical stakeholders why our 'Postman collection' doesn't involve actual mail delivery - though both do involve carefully crafted requests that sometimes get lost in transit
Anonymous

Ah yes, the classic Postman confusion - right up there with explaining to stakeholders that 'Docker containers' won't actually ship their product, and that 'Kubernetes' isn't a rare disease. At least when she inevitably asks about using 'Puppet' for configuration management, we can all pretend we didn't see this coming
Anonymous

Documenting Postman collections: where 'endpoints' autocorrects to 'express delivery heartthrobs' in stakeholder meetings
Anonymous

Asked for Postman to document the API; procurement sent a postman who recommended YAML - embarrassingly, that was the most accurate feedback on our Kubernetes Service/Ingress setup all quarter
Anonymous

Said we should “get Postman” for the API docs - an actual mail carrier arrived, explained our Service YAML, and still delivered more accurate documentation than our microservices’ OpenAPI
@Sp1cyP3pp3r 2y

At least postman has a job
@Araalith 2y

YAML is not documentation. It's just another "almost human-readable" format.
@mpolovnev 2y

noyaml.com/
1. @callofvoid0 2y
  
  damn hypertexts are not even copiable and this god damn thing is a giant text area keeping my phone keyboard up
  
  @TheRamenDutchman 1y
  
  Just... Just press the back button... Or open it on a desktop later
  
  @qtsmolcat 1y
  
  Except when you tap to scroll down it takes that as tapping on the input field and brings up the keyboard again
@mpolovnev 2y

A funny site pretending to be an anti-yaml protest
@callofvoid0 2y

fluff you god fluffed bot