vøiddo devlog
ship every week. write about it.

Your commits deserve a blog post.

Paste your GitHub URL or git log. Get a blog post, tweet thread, and LinkedIn post in under 30 seconds.

// your git log
a3f9c1b fix: mobile nav collapse on scroll
7e2d884 feat: add Stripe webhook retry logic
c5891ba perf: lazy-load product images
f1a0372 fix: checkout button disabled state
2bd6c03 chore: bump deps, remove lodash
// generated devlog
BLOG POST
Week 14: Shipping the Boring Stuff (That Actually Mattered)
This week was less "feature drop" and more the invisible work that makes everything else hold together. Here's what shipped — and why it was worth it...
GitHub URL
Paste commits
Pro (unlimited)
Results emailed. Also viewable at your result link.
the process

How it works

Three steps. No onboarding, no accounts, no explaining your project to an AI.

$
01 / input

Paste a URL or git log

Public repos work without any auth. Or run git log --oneline -30 and paste the output.

~
02 / generate

We turn commits into narrative

Claude reads what you built and writes a 400-word blog post, 5-tweet thread, and LinkedIn post — all in one shot.

>
03 / receive

Content lands in your email

Three pieces ready to post. Takes under 40 seconds to generate after payment confirms.

what you get

Real output, not a template

Generated from actual commit messages. Every devlog is different.

Week 14 devlog · sample project
sample
Blog post
Tweet thread
LinkedIn
Week 14: Shipping the Boring Stuff (That Actually Mattered)

This week was less "feature drop" and more the invisible work that makes everything else hold together. No big headline. Just five commits that are going to quietly save a lot of headaches.

The big one: Stripe webhook retry logic. Our previous setup would give up if the first delivery failed. We've had three orders over the past month where payment succeeded but the order didn't fulfill. Fixed. Now we retry with exponential backoff and alert on repeated failures instead of silently eating them.

We also killed the full Lodash dependency. 71kb gzipped, and we were using exactly four methods. Replaced them with tiny inline equivalents. That's 71kb back in your browser's pocket.

The mobile nav collapse bug was a passive event listener conflict with our scroll handler. Three lines of code. Two days of debugging.

Next week: checkout test coverage, and finally the dark mode we've been promising since January. See you then.

1 / 5
Shipped a quiet week. No big features, just the work that makes everything else not break. Here's what actually happened:
2 / 5
Fixed: Stripe webhooks silently eating failed deliveries. 3 unfulfilled orders last month from this alone. Now retries with backoff + alerts. The boring stuff that costs real money when it breaks.
3 / 5
Removed Lodash entirely. We were importing 71kb gzipped to use exactly 4 methods. Replaced with 12 lines inline. Sometimes "just use a library" is the wrong advice.
4 / 5
Mobile nav collapse bug: passive event listener conflict with the scroll handler. 3 lines to fix. 2 days to find. The ones you remember forever.
5 / 5
Next: checkout test coverage + dark mode. If you ship weekly and hate writing devlogs, I use voiddo devlog — paste your git log, get a blog post + tweet thread + LinkedIn post. devlog.voiddo.com
Week 14 shipped. Here's what actually happened behind the scenes.

Not every week is a feature launch. This week was maintenance, performance, and fixing things that were quietly costing us money.

The most important fix: Stripe webhook reliability. Three orders fulfilled incorrectly last month because our handler gave up after a single failure. Now it retries with exponential backoff. Lesson: boring infrastructure work has a real dollar value attached.

We also removed Lodash entirely — 71kb gzipped for four utility functions. Worth adding three years ago. Not worth keeping today.

What's your approach to keeping technical debt manageable while still shipping? Writing weekly devlogs forces me to actually audit what I built, not just what I shipped.

pricing

One generation or unlimited

No subscriptions required. Pay per generation, or go unlimited if you write every week.

One-time
$9 / generation
One blog post, one tweet thread, one LinkedIn post. Emailed to you. Viewable at your result link for 30 days.
  • -> Blog post (300–400 words)
  • -> 5-tweet thread with hook
  • -> LinkedIn post (150–200 words)
  • -> Public GitHub repos supported
  • -> Or paste your git log
  • -> No account needed
One-time payment via Paddle
Pro — Unlimited
$19 / month
Generate as many devlogs as you want. License key emailed immediately — no checkout friction every time.
  • -> Everything in one-time
  • -> Unlimited generations
  • -> License key — no checkout per use
  • -> Cancel anytime
License key emailed immediately
questions

FAQ

Does it work on private repos?+
Public GitHub repos work directly via the GitHub API. For private repos, run git log --oneline -30 and paste the output. No OAuth needed.
How long does generation take?+
Usually 20–40 seconds after payment confirms. You'll get an email with all three pieces of content, plus a link to view anytime.
Can I edit the output?+
Yes. The output is plain text — copy it wherever you write. It's meant to be a solid first draft, not something you're afraid to touch.
What if the generation fails?+
Email hi@voiddo.com and we'll regenerate or refund. We track failures and fix root causes.
Is my code sent anywhere?+
We only read commit messages — not source code. Commit messages are sent to the Anthropic API for generation and not stored permanently beyond your 30-day result window.
How do I cancel the Pro subscription?+
Email hi@voiddo.com with your email address. We cancel immediately. You keep access until the period ends.