November 26, 2025
Reply-All to Deploy
After 15 Years, I Use Outlook as My Build Pipeline
Developer ships code via Outlook—hero to some, hazard to others
TLDR: A developer routed code changes through Outlook emails to dodge slow internal access, triggering a firestorm. Commenters split between praising scrappy brilliance and blasting security risks, sharing war stories that show how red tape pushes people into risky shortcuts—highlighting the eternal battle between speed and safety.
A burned-out engineer just confessed to using Microsoft Outlook to move files into a system—yes, email—to beat company red tape, and the internet is eating it up. In his dramatic post, he jokes about praying to the “machine overlord” and wiring a Python script to watch his inbox and auto-send attachments to a server, all because a teammate still can’t get the right access after two weeks.
The comments instantly split into rival camps. One hardliner thundered that if your setup is more than a tiny script, you’re a fraud who shouldn’t touch real systems. On the opposite end, a cheer squad crowned the author a legend for doing what bureaucracy wouldn’t. Security worriers chimed in too, clutching pearls over “enormous” risks and begging for end-to-end (E2E) encryption—basically, messages only readable by sender and receiver. Then came the war stories: a CTO bragging about email-based builds decades ago, and someone admitting they once shoved a Microsoft Access database on a shared drive to bypass months-long delays.
The vibe? Equal parts roast, toast, and group therapy. It’s scrappy ingenuity versus professional standards, with a chorus chanting the author’s message: shoddy automation beats no automation—at least until it bites back.
Key Points
- •A coworker lacked server endpoint access for two weeks, prompting a workaround to avoid manual file handling and deployment steps.
- •The coworker’s code automatically sends emails with attachments to a designated Outlook inbox folder using a specific subject line.
- •A Python script runs every minute, filters for the latest unread matching email, parses the attachment, encodes it, and forwards it to a server endpoint.
- •The server saves and publishes the file, after which the author uses a front-end GUI to verify behavior.
- •To mitigate security risks, the entry point is protected by a shared secret codeword; the solution is intended for non-production use.