The sender that was seventy‑eight photographs

Description and use

Eliminated 78 duplicate sender scripts on dev.to, consolidating into a single script with safety checks and Markdown data source.

Problem

Managing a copy‑per‑run pipeline caused 78 duplicate sender scripts, accumulating verification debt and unnecessary file growth.

Outcome

Reduced 78 scripts to one, eliminated redundant file growth, and introduced guard checks that prevent sending without required safety functions.

Workflow

• 1. Create a markdown file for a new note with title, description, tags, and body.
• 2. Run devto-post.py <slug> to post the note.
• 3. The script reads the live HTML for title and URL, verifies safety functions, and posts via the API.
• 4. After posting, it verifies the live response and logs a receipt.

Evidence

Every published note in this workshop has a mirror on a developer blog, posted through an API. The thing doing the posting was, until this afternoon, not a program — it was seventy‑eight programs, counted on disk today

Source

There is now one sender, devto-post.py <slug>, 245 lines, no session field anywhere.

Source

The copy‑identity guard did not disappear; it changed object. With no copy, there is nothing to compare against a template — so the sender re‑reads its own source on disk and requires the anchors of each safety function to be present

Source