Proof point → A one-person brand competing with teams has one option: infrastructure. I built mine, rebuilt it, and rebuilt it again as the platforms changed.

🩻 Problem

A solo music brand (MelodicJeanious) needs daily presence across Instagram and Twitter - research, formatting, posting, reposting - hours of manual work that produce nothing durable.

🔨 Solution

Eight tools across five years, automating the entire posting operation:

Architecture Overview

  1. views-api (2020, the anchor) - a content-curator bot: Express + Mongoose + Puppeteer with cron-driven jobs, account/platform/post/record models, SendGrid notifications, and Sentry - a real service, run for over a year.
  2. tweetagram (2021) - fetch the latest tweet via RSS, screenshot it, queue it for Instagram reposting - a cross-platform content bridge in the house Express MVC style.
  3. twitter-uploader (2024) - the reliability peak: a macOS launchd-scheduled batch uploader (3pm/6pm/9pm) with missed-run catch-up via a run log and idempotency via processed-folder state - unattended operation engineered properly, with the full plist/venv setup documented.
  4. Supporting cast - hashtag research notes, caption/hashtag-templated schedulers, tweet filtering/formatting, username checking.

The same problem, four rewrites, two languages - the repetition is the evidence: this was sustained operational need, and each rewrite shows the craft maturing (the 2020 scraper’s skeleton became the formal boilerplate).

📜 Philosophy

Automation as leverage for one person doing a team’s job. Design for unattended reality: scheduled, idempotent, self-recovering. Ship the script that posts today.

🎓 Key learnings

  • Reliable unattended job design - cron/launchd, missed-run recovery, processed-state tracking - the patterns that make automation trustworthy.
  • Browser automation and its limits against platform APIs and terms - friction known firsthand, which is how you later design systems that don’t need it.

📈 Output & impact

  • The documented operating infrastructure of a real brand’s social presence, 2019–2024.

🌍 Why this matters

Original Tools & IP · The Founder Journey. Every brand, program, or institution that must publish consistently faces this exact problem. Five years of solving it - alone, reliably, on a shoestring - is how you learn to make content operations scheduled, recoverable, and unattended.

🚀 Hire me

Need your content operation to run itself? Let’s talk → · See also: Chrome Tools · The thesis