The latest articles on DEV Community by PotatoLab (@potatolab). https://dev.to/potatolab https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3935412%2Fb6226b1d-b22f-41fb-82cd-197b2163e66a.png https://dev.to/potatolab en PotatoLab Sat, 16 May 2026 20:04:02 +0000 https://dev.to/potatolab/why-i-stopped-building-features-and-started-shipping-experiments-4hc5 https://dev.to/potatolab/why-i-stopped-building-features-and-started-shipping-experiments-4hc5 <blockquote> <p>An honest post about perfectionism, unfinished projects, and why my portfolio is named after a vegetable</p> </blockquote> <h2> The worst advice I ever got about building projects </h2> <p>"You should know it all before you start."</p> <p>You won't. You never do. And waiting until you do is just a more socially acceptable way of never starting.</p> <p>I have a graveyard.</p> <p>An Android SDK for image processing that never saw light. A logistics platform that got about 80% done before I move to different things. An e-commerce thing. Some indie apps I built sitting in a private repository.</p> <p>I'm a full-time software engineer. I know how to build things. So why couldn't I finish any of them?</p> <p>The answer, if I'm honest, is that I kept building the wrong version. Not wrong in the technical sense but rather wrong in the scope sense. Every project became the version that would handle every edge case and look perfect doing it. I never admitted that. But just kept building like that was the goal.</p> <p>It wasn't perfectionism in the classic sense. It was perfectionism disguised as engineering. "I'll ship it when the architecture is right." Meanwhile nothing shipped.</p> <h2> Then my wife suggested I call it 감자랩 as in PotatoLab </h2> <p>I laughed. Then I thought about it.</p> <p>Potatoes are not glamorous. They're lumpy, inconsistent, yet nobody ignores them. But if you know what you're doing with them, they turn into something completely different. Something good. The raw form doesn't matter; what matters is that you actually cook them.</p> <h2> So I made a rule for myself </h2> <p>A project that goes into the lab. It has to meet a small, specific set of requirements I define upfront not a roadmap, not a backlog, just: what does this need to do to be real? When it hits that bar, it ships. Not when it's perfect. Not when it scales. When it works well enough to be true.</p> <p>Shipped doesn't mean finished. It means fulfilled. A small promise, kept.</p> <p>The experiments on <a href="https://potatolab.cc/" rel="noopener noreferrer">PotatoLab</a> aren't impressive in scope. None of them are perfect. But they exist outside my laptop, which is more than I can say for the SDK that was going to change mobile image processing.</p> <p>Start lumpy. Ship weird. Cook the potato.</p> <p><em>In Part 2, I'll get into more details, and I don't know what I am going to write about but here we are...</em></p> devjournal productivity sideprojects softwaredevelopment