Stop Perfecting, Start Shipping: A Lesson From Football and Software

TLDR: Oskar Dudycz revisits a personal essay he wrote ten years ago about perfectionism and the habit of over-engineering ideas that never ship. Inspired by Amy Hoy's "Just Fucking Ship," the essay challenges the developer reflex to build perfect foundations before doing anything visible. The message lands just as hard today as it did then.

Summary:

The essay opens with a football memory. Borys had the best dribbling. Someone else bent it like Beckham. But Oskar? He kept his keepie-uppies to 20 or 30, not because he couldn't do more, but because ornament without outcome never interested him. Fundamentals matter. Getting the ball in the net matters. That setup is a metaphor, and it lands.

The self-portrait Oskar draws is painfully familiar to a lot of developers. Architecture first. Framework before features. Domain name before product. Best practices, design patterns, the latest tech, all chosen with great care before a single thing ships to a real user. He calls the result projects like icebergs: massive underneath, nothing visible above. The customers, in this worldview, are almost an inconvenience. And then the projects quietly die on the back of a hard drive somewhere.

What changed the frame for him was Amy Hoy's "Just Fucking Ship." He's clear that the book isn't groundbreaking and doesn't hand you a golden recipe. What it does is open a few mental hatches. The core insight is about sequencing: set a goal, set a deadline, then figure out the scope and the methods. Not the other way around. He uses a dinner party analogy that actually works: nobody postpones inviting friends over because they can't pull off a three-course meal with homemade liqueur. You adjust the menu. Why don't we do the same with software?

There's another observation in there worth sitting with. We fixate on the grand vision so completely that we never achieve any small satisfying milestone along the way. The lack of incremental wins drains motivation before the thing has any chance to exist. Standing on the ground floor wondering if you can make it to the top floor gets you nowhere. You take the stairs one step at a time.

He ends with a note that he originally wrote this in Polish ten years ago, when he was nearly 30. He's now 40, translating it and sending it out because the message still applies. He even admits he hasn't fully shipped everything he planned. That honesty is what makes it worth reading. He wrote it again in the context of the GenAI era: we're overfocused on doing rather than shipping things that matter.

Key takeaways:

Set the goal and deadline before deciding scope, not after
Over-investing in architecture and foundations before any visible output is a form of procrastination
Small incremental goals create the motivation needed to keep going
The "Just Fucking Ship" principle applies whether you're building a side project, a startup, or a feature

Why do I care:

This essay resonates in a way that most productivity content doesn't, because it comes from someone who clearly loves the craft and still falls into the trap. The instinct to get the foundations right before doing anything visible is not a flaw in a vacuum. It often reflects good engineering judgment. The problem is when it becomes a shield. When the architecture work becomes the project rather than the means to an end. I've seen teams spend months on infrastructure that was genuinely excellent, technically, and then run out of steam before shipping anything a user ever touched. Oskar isn't arguing against good engineering. He's arguing against using it as a reason to never finish. That's a distinction worth remembering every time you're tempted to refactor one more thing before the first release.

Borys had the best dribbling