This is a 24-hour open-source log, not a myth. The goal was never "one-shot perfection." The goal was a maintainable v1 — something someone else could read, run, and extend.
Step 0: cut scope
I kept four things, and four only:
- A working main path
- Clear feature boundaries
- Basic async tests
- Readable docs
Anything that would slow delivery without affecting first-version usability — out. Not deprioritized, not "later." Out.
Hours 0–6: execution path first
Make input → output traceable. Don't reach for clean abstractions yet. Early abstraction usually just hides bugs under nicer-looking surfaces. I'd rather have ugly, traceable code than tidy code I can't reason about.
Hours 6–10: OAuth timing
This was the real puzzle. Which errors should fail fast? Which should prompt the user toward a recovery action? Which states should I leave intact for a retry to pick up?
Working through this told me something I wasn't expecting: authorization is not a side feature. It's the usability foundation. If the auth flow is sloppy, nothing downstream feels reliable.
Hours 10–14: quota lives in the main flow
Quota does not get bolted on at the end. If you add metering late, it almost always drags pricing logic and error semantics into the rewrite with it.
So I put a small KeyValueStore-backed per-feature counter directly in the request path. No DB, no cron. (Wrote it up separately as part of this same series.)
Hours 14–18: the unglamorous cleanup
Async test coverage on the happy path and the obvious failure modes. Exception paths. Naming boundaries that won't bite a future contributor. None of this is exciting. All of it prevents the first wave of post-launch issues from being existential.
Hours 18–21: README + MIT license
MIT matters for indie builders in a very practical way: it removes the "can I actually use this?" friction. Collaboration is more valuable than control, especially when you have zero stars and need the door wide open.
Last 3 hours: stranger's-eye review
Read the repo as if I'd never seen it. Run the project from scratch following only the README. Check that nothing private leaked into commits.
This is the easiest step to skip and the most reliable way to catch your own blind spots.
What I'd say to a past me
- Speed isn't typing fast. Speed is deciding fast what not to build.
- Open-source quality isn't zero bugs. It's "visible, reproducible, fixable."
- The auth layer is the foundation, not a feature. Get it right early or pay forever.
What I'd say to a past me
- Speed isn't typing fast. Speed is deciding fast what not to build.
- Open-source quality isn't zero bugs. It's "visible, reproducible, fixable."
- The auth layer is the foundation, not a feature. Get it right early or pay forever.
Source: foxck016077/apify-gmail-inbox-intel — MIT, refresh-token-only OAuth, async per-feature router.
Companion path (if you don't want to self-host OAuth): Freelancer Gmail Client Tracking Pack — $9 on Gumroad. 30 Gmail labels + 12 filters + 5 follow-up templates + Apps Script. Same SLA-breach detection workflow as the Actor, manual version — 20 min setup.
Question for you: when you ship an MVP under a tight clock, which step do you cut first — tests, docs, or polish? Curious how others balance it.
Update (May 19): Day 6 of this experiment. The Actor is live at apify.com/foxck/gmail-inbox-intel — paste 3 OAuth fields (gmail.readonly scope), get stalled threads ranked by SLA breach age. Source at github.com/foxck016077/apify-gmail-inbox-intel (MIT). The freelancer companion PDF that grew out of this is now pay-what-you-want from $1: foxck.gumroad.com/l/freelancer-gmail-tracking-pack. 30% affiliate at foxck.gumroad.com/affiliates if anyone wants to share.
Day 7 update (later May 19): I shipped a product pivot — the Gumroad listing above is now a Self-Host Bundle for engineers (full Actor source + docker-compose.yml + 5-min OAuth setup), PWYW from $5 suggested $19. The original PDF still ships inside as a bonus. Same URL.
Day 7 write-up with the funnel audit that triggered the pivot: funnel audit found 7 of 9 articles had no buy link, then I pivoted the product.
Sample report preview: Friday Triage gist — anonymized 10-thread example of the $99 Done-For-You triage output. Grounded in r/sales 1tdngew (49 comments on re-engaging cold prospects) and r/smallbusiness 1td0827 (60-comment thread, top reply at 61 score: "holding 50 open loops in your head").
More from the shop:
- Claude Code Mastery: The Reverse-Engineering Guide — $49, 19 pages, every env var / hook event / settings key extracted from the v2.1.90 binary
- 5 n8n Workflows that Save 10+ Hours/Week — $29, the bundle
- AI Lead Auto-Responder — $39, Gmail → instant AI-classified reply
Read the latest checkpoint: Day 16 — +51 reader spike in 85 min, 0 sales
Day 18 — pbot v1 dev preview shipped
After 18 days of this ZERO-TEN cold start: $9 PDF killed at Day 17, pivoted to pbot — a one-click personal knowledge bot you install on your own machine. Talk to it from LINE / Telegram / Zalo on your phone.
v1 dev preview is real: 93 MB macOS .dmg packaged, 15k-chunk SQLite FTS5 queries in 0-3 ms, Anthropic real calls with source citations, daemon auto-start on boot. Day 18 deep dive: the 7-line bigram fix for Chinese search.
Top comments (0)