When they refuse to read the README | Code Infinity #shorts
Skills:
API Design70%
Key Takeaways
Laments the frustration of users not reading documentation, such as README files
Full Transcript
It's prando no p do cão. She comes, comes on the skin, not parabão with a cat with a lot of pressure. She's incredibly talented at mastering ballet. Angry cat [music] naughty. To mess with my head in peace. She's shaking her hips, playing the music without mercy.
Original Description
There is nothing quite like the feeling of pouring your soul into a Swagger UI page only to realize that nobody has ever clicked the link. It is the ultimate exercise in creative writing where the audience is just your future self during a post-mortem.
You try to make it readable. You add examples. You define every possible response code. And yet, the Slack message arrives anyway. It is not even a question about the logic. It is just the URL.
Drop a comment if you have ever been the person asking the question or the person who wrote the docs. Let us know your documentation horror stories.
What this Short is about:
• Setup: Me spending 72 hours documenting every edge case and error code in the new API.
• Punchline: Frontend dev: Hey man what is the URL for the post request?
More Code Infinity developer humor → like & subscribe for Shorts.
Watch on YouTube ↗
(saves to browser)
Sign in to unlock AI tutor explanation · ⚡30
More on: API Design
View skill →Related Reads
📰
📰
📰
📰
Your app has two caches. What if it only needed one?
Dev.to · Dencio
Run a Full JavaScript Website with AxonASP — No Node.js Required
Dev.to · Lucas Guimarães
A complete Laravel API with clean architecture in 30 seconds, tests included
Dev.to · Loic Aron Mbassi Ewolo
Pain point #2: Django’s ORM Performance Problem
Medium · Python
🎓
Tutor Explanation
DeepCamp AI