this post was submitted on 05 Nov 2026
125 points (97.7% liked)
Programming
29329 readers
259 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I was introduced to it on a specific project where 3rd party integrations were unreliable. We could save and share specific requests and responses, and compare them over time. We built up a sizable library of what is expected output from each API.
It enabled us to be like: "hey dickheads you broke your API again." Essentially doing unit testing on their behalf. Technically not our job, but our customers didn't care whether it was our fault or 3rd party's fault. I was expected to fix problems, even if it wasn't my problem.
At some point Postman got really weird and confusing. You had to make an account, and it synced all your stuff to the cloud (offline only was no longer an option), and various other enshittification behaviours. At that time we switched to another tool, but I don't remember the name.