← shivamvashisth.com@svx2027

Case studies

The harder pipelines, end to end

Every pipeline I ship has a public, genericized repo. These are the write-ups behind the hardest ones: the problem, the design decision that actually mattered, and the platform quirk that would have quietly broken it.

Anonymized on purpose: the channels are real, the client is not named, and every number here is one already stated in the linked repo's own README.

02 · 4 min read

Nothing gets pasted into the tracker until two passes agree

A YouTube channel tracker that refuses to hand over a single row until a second, separately-written pass of its own pipeline reaches the same answer from a fresh fetch.

4 gated phases: discover, verify, format, QA note
2 independently written code paths that must agree before anything ships
33 tests, including one pinned to a midnight timezone boundary
Read the case study →

03 · 4 min read

Proving a bulk update worked without ever asking for the password

A batch rewrite of titles, descriptions, and tags across a whole YouTube playlist, authorized by the channel owner without handing over their login, and proven after the fact by reading the platform back, not by trusting the script's own log.

6 scripts, each safe to re-run on its own
3 metadata fields the YouTube API wipes on a write, with no warning
13 tests covering the retry and idempotency logic
Read the case study →

04 · 5 min read

A transcript that reads clean is not proof the audio is

A pipeline that turns a long bilingual livestream into short-clip candidates found that forcing a transcription model into one language doesn't make it fail on the other, it quietly translates over it, which is why every candidate clip gets re-checked before an editor ever sees it.

13 tests pinning the exact calculations an editor's clip depends on
2 independent transcription passes a window must clear before it's trusted
0 API keys or secrets needed anywhere in the pipeline
Read the case study →

More landing soon

Want the next case study when it ships?

Leave your email. One short note when a new write-up lands here, nothing else.

Just your email, stored on my own private database. Never sold, never rented. Reply to any email to unsubscribe.