3980.2
TFLOPS
dhruv3006
86
followers
·
61 following
None yet
reacted
to
their
post
with 🚀
about 5 hours ago
Switching between API Client, browser, and API documentation tools to test and document APIs can harm your flow and leave your docs outdated.
This is what usually happens: While debugging an API in the middle of a sprint, the API Client says that everything's fine, but the docs still show an old version.
So you jump back to the code, find the updated response schema, then go back to the API Client, which gets stuck, forcing you to rerun the tests.
Hours can go by just trying to sync all this up (and that’s if you catch the inconsistencies at all).
The reason? Using disconnected tools for specs, tests, and docs. Doing manual updates, stale docs, and a lot of context switching.
Voiden takes a different approach: Puts specs, tests & docs all in one Markdown file, stored right in the repo.
Everything stays in sync, versioned with Git, and updated in one place, inside your editor.
Download Voiden here: https://voiden.md/download
reacted
to
their
post
with 🔥
about 5 hours ago
Switching between API Client, browser, and API documentation tools to test and document APIs can harm your flow and leave your docs outdated.
This is what usually happens: While debugging an API in the middle of a sprint, the API Client says that everything's fine, but the docs still show an old version.
So you jump back to the code, find the updated response schema, then go back to the API Client, which gets stuck, forcing you to rerun the tests.
Hours can go by just trying to sync all this up (and that’s if you catch the inconsistencies at all).
The reason? Using disconnected tools for specs, tests, and docs. Doing manual updates, stale docs, and a lot of context switching.
Voiden takes a different approach: Puts specs, tests & docs all in one Markdown file, stored right in the repo.
Everything stays in sync, versioned with Git, and updated in one place, inside your editor.
Download Voiden here: https://voiden.md/download
reacted
to
their
post
with 👀
about 5 hours ago
Switching between API Client, browser, and API documentation tools to test and document APIs can harm your flow and leave your docs outdated.
This is what usually happens: While debugging an API in the middle of a sprint, the API Client says that everything's fine, but the docs still show an old version.
So you jump back to the code, find the updated response schema, then go back to the API Client, which gets stuck, forcing you to rerun the tests.
Hours can go by just trying to sync all this up (and that’s if you catch the inconsistencies at all).
The reason? Using disconnected tools for specs, tests, and docs. Doing manual updates, stale docs, and a lot of context switching.
Voiden takes a different approach: Puts specs, tests & docs all in one Markdown file, stored right in the repo.
Everything stays in sync, versioned with Git, and updated in one place, inside your editor.
Download Voiden here: https://voiden.md/download
View all activity
view post
Switching between API Client, browser, and API documentation tools to test and document APIs can harm your flow and leave your docs outdated. This is what usually happens: While debugging an API in the middle of a sprint, the API Client says that everything's fine, but the docs still show an old version. So you jump back to the code, find the updated response schema, then go back to the API Client, which gets stuck, forcing you to rerun the tests. Hours can go by just trying to sync all this up (and that’s if you catch the inconsistencies at all). The reason? Using disconnected tools for specs, tests, and docs. Doing manual updates, stale docs, and a lot of context switching. Voiden takes a different approach: Puts specs, tests & docs all in one Markdown file, stored right in the repo. Everything stays in sync, versioned with Git, and updated in one place, inside your editor. Download Voiden here: https://voiden.md/download
See translation
Moondream3 and Salesforce GTA-1 for UI grounding in computer-use agents
