Day 2: Why Working Harder Isn't Enough

Source: Dev.to

When I was a boy, I sold Scout‑O‑Rama tickets. The math was simple: knock on more doors, get more sales, win a bigger prize. Selling software isn’t that different—make more quality products, have a better chance of selling one.

The Math That Changed Everything

I did some math today that I can’t stop thinking about.

Over 90 % of indie products fail commercially. Most of their creators never ship another one.

If each product has a 99 % chance of failure, how many products do you need for a 99 % chance that at least one succeeds?

# P(at least one success) = 1 - (0.99)**n >= 0.99
# Solve for n:
import math
n = math.log(0.01) / math.log(0.99)
print(n)   # → 458.2

459 products.

I have 3 paid products, so that’s 456 more to go. With 67 working days left (no Sundays) that works out to 6.8 products per working day—nearly seven, every single day, for the rest of the challenge.

The Ceiling

Even with AI helping me all day, each product still needs architecture, building, testing, payment integration, store listings, and review. I shipped three today, pushing as fast and hard as I possibly can. That’s my ceiling: 3 products per day. The math needs 6.8.

It’s Not Just Quantity

The Scout‑O‑Rama math doesn’t account for one crucial fact: no one wants trash. I can’t churn out 6.8 pieces of junk a day and call it a strategy. Every product has to actually work, solve a problem, and be something someone would pay for. Quality isn’t optional—it’s the whole point. A hundred broken products are worth exactly zero.

Working Harder Won’t Fix This

I can’t write 459 quality products by hand—in 80 days, not even in a year. This is beyond prompt engineering or typing questions into ChatGPT. 6.8 quality products a day doesn’t come from working harder—I’m already at my limit.

It has to come from working smarter: building systems that do real work without me standing over them. I don’t know exactly what that looks like yet, but I know my ceiling, I know the math, and something has to change.

My Competition

My son has always produced the highest‑quality work. In a college game‑dev class, everyone got a prompt and five hours to finish. Most students didn’t even complete it. He not only finished—he did it correctly, and the professor showcased his work without warning him.

That’s who I’m competing with. He’s taking a focused, depth‑first approach: quality over quantity. Knowing him, whatever he ships will be polished.

I’m going breadth‑first: volume. The math play.

What keeps me up at night is that we both need to be faster and better. We’re already working as hard as we can. Working harder isn’t the answer anymore; we need to work smarter.

The Jabberwocky

My ceiling is 3 products a day; the math needs 6.8, and they all have to be good. When I was a kid, knocking on more doors was enough. It isn’t anymore.

I feel like I’m about to face my own Jabberwocky—knowing the fight looks impossible before it’s even begun. The numbers say I can’t win by doing what I’m doing now. But then again, the Jabberwocky was supposed to be unbeatable too.

What I Shipped Today

• CleanLinks – a Chrome extension that strips 127+ tracking parameters from URLs as you browse. $2.99 Pro upgrade. Currently in Chrome Web Store review.
• Inline Dependency Size – a VS Code extension that shows the gzipped bundle cost of every import right in your editor. $4.99 Pro.
• Dead Code Highlighter – a VS Code extension that finds unused functions, variables, imports, and exports across your entire project. $5.00 Pro.

I also rebuilt artizansoftware.com as a real storefront for everything.

Scoreboard

The math says I need to work smarter. Follow the series to see if I figure out how.

Series: Return of the Coder — In 80 Days
Tags: #buildinpublic #devjournal #programming #startup

Follow the series: Return of the Coder — In 80 Days
Website: artizansoftware.com