An application to Thally, for Senior Developer Experience & Documentation Engineer
Your product changed. I'm the one who goes hunting.
I'm Reet. Four years in developer relations, a docs drift detector I built myself, and a habit of fixing other people's quickstarts. So I ran my application the way Thally runs a merge.
Tracked repository · 1 connected
main · 4 years watchedMerged#2026
Apply to Thally as a docs engineer
main ← apply/thally
+4 years −0
- role: "devrel, between things"+ role: "docs engineer at thally"
Thally
- Reading what changed.
- Tracing references across seven surfaces.
- Six pull requests to open.
Connected surfaces · 7
- Docs guidesPR #2040 StarkWare and Polygon tutorials
- API referencePR #2041 docsParity, from the real API
- Code examplesPR #2042 Quickstart fixes, merged
- ChangelogPR #2043 Four years, in order
- Help centerPR #2044 Biconomy SDK support
- WebsiteNo change needed
- llms.txt & MCPPR #2046 A 30 minute llms.txt fix
Website: no change needed. reetbatra.com is already up to date. Thally would say so too.
Drift I've already caught.
This is the job before Thally. Run the quickstart, find where it breaks, trace it to the release that changed it, open the fix.
Mergedcyberwave-os/docs-mintlify#105
The quickstart crashed
- drone = cw.twins("dji/dji-mini-4-pro")+ drone = cw.twin("dji/dji-mini-4-pro")
The first example in the quickstart failed on its first call. For most developers, the quickstart is the product.
Mergedsarvamai/skills#17
A renamed parameter
- target_language_code="hi-IN",+ language_code="hi-IN",
Renamed in sarvamai 0.1.29 with no alias, so code copied from the skill threw on the old name.
Mergedsarvam-ai/ai-sdk#2
The empty stream
- { type: "text-delta", id, delta }+ { type: "text-start", id } + deltas
Every token arrived and the reply was still empty. Without text-start, AI SDK v6 dropped every delta.
I got tired of hunting, so I built the detective.
docsParity takes a repo and a docs site and tells you where they disagree, ranked by how much it will hurt a developer.
- 01.
Read the code
Pulls the repo's real exported API with the TypeScript compiler, plus extractors for Python, Go, Java and Rust.
- 02.
Read the docs
Crawls the docs site to clean Markdown, the main page first, then a small breadth crawl.
- 03.
Compare
The model only compares what the compiler found against what the docs say. It never gets to invent an API.
- 04.
Show the evidence
Each mismatch comes with the code snippet, the docs snippet and the fix, plus a button that opens a pre-filled GitHub issue.
The drift score is added up from the findings by severity, and a finding the model is unsure about counts for less. If someone asks why their SDK got a 7, I can show them the math.
Where it stops: it reads signatures, not behavior, so it misses a function that kept its shape but now does something else. Thally starts from the merged PR, which is how you catch that.
Four years of getting developers to working code.
Docs, tutorials, demos, support and community, mostly for developer platforms that were hard to start with.
- Wrote 12+ developer tutorials, demo apps and video guides that went into the official Starknet docs.
- Created and hosted the Starknet Builder Series, 4K to 8K organic views an episode, with hands-on demos of Starknet Foundry, Sasuke, Dojo and Cartridge.
- Took what developers hit on Discord and GitHub back to the product team as roadmap input.
starknet-docs#1572, the Windows install guide (merged) End to end dApp with starknet.js Game development with Dojo Session keys for gasless transactions
- Represented Polygon AggLayer at ETHIndia and ETHGlobal Bangkok with technical workshops, talks and live demos.
- Built Dabl Learn, a structured developer course on Polygon and AggLayer, from spec to launch.
- Integrated the Storyblok headless CMS into EF Academy end to end, in Next.js, NestJS and TypeScript.
- Supported developers on the Account Abstraction SDK across Discord and GitHub.
- Wrote 50+ pages of technical docs for SDK integration and smart account workflows, so the same questions stopped coming back.
- Led StarkCon: 11 events across India, 4,800+ developers, and India's first Cairo community.
- Ran a $21,000 grants program and a 5 week bootcamp with 600+ students.
Before that: technical content, bootcamps and starter kits for Rust and Substrate developers at Nervos.
The newest reader of your docs is an agent.
Stale docs used to mislead one developer at a time. Now a coding agent reads them and repeats the mistake in everyone's code.
Your docs platform wrote your llms.txt
A 30 minute checklist for the file your platform generated and nobody on the team has opened.
zcashlabs/zcash-skills#4
A CI job that fact-checks only the lines a PR changes, so agent skills stop drifting from the code. Merged.
openvm-org/openvm#3166
Their llms.txt returned a 404 because the docs plugin that builds it crashed. I traced it and tested the fix on a newer version.
What I'd do first.
- 01.
Use Thally on real repos
Mine first. Write down every place I get stuck, and turn each one into an issue or a docs fix.
- 02.
Make the quickstart finishable
One sitting, start to a working site, checked against the real product every release.
- 03.
Give developers a room
Office hours and a place to share what they built, and tell people when their feedback ships.
Nothing publishes without a human.
So this one's waiting on you. Approve it, or ask me anything first.
Reet Batra · applicationawaiting review