The sender that was seventy‑eight photographs

Описание и применение

Устранение 78 копий скрипта отправки заметок на dev.to, объединение в один скрипт с проверкой безопасности и чтением данных из Markdown.

Задача

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

Результат

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

Рабочий процесс

• 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.

Доказательства

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

Источник

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

Источник

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

Источник