Category · 8 essays
Building Products
Why Most Side Projects Never Get Finished
Side projects usually die from scope, unclear feedback, and treating them like hobbies instead of problems worth solving. Finishing is mostly a systems problem.
I Stopped Waiting for Perfect Ideas
Good ideas are rarely perfect when they first show up. They become obvious only after you start building, testing, and paying attention to what people actually need.
What Building 5 Products Taught Me
Each product teaches a different lesson about timing, users, distribution, and what matters once the novelty wears off. The pattern is rarely what you expect.
The MVP Is Usually Smaller Than You Think
Most people overbuild the first version because they are trying to prove the product before they have evidence. The real MVP is usually a single sharp loop.
Why Every Developer Should Build for Themselves
Building for yourself is the fastest way to learn taste, urgency, and product judgment. You stop guessing what matters because you feel it directly.
Shipping Fast Doesn’t Mean Shipping Bad
Speed and quality are not opposites. The real issue is whether speed comes from focus or from skipping the parts that matter.
How I Decide Which Ideas Are Worth Building
I look for pain, urgency, leverage, and whether the thing would still matter after the novelty disappears. Good ideas survive contact with reality.
Why Features Don’t Build Companies
A feature can impress a user once. A system that solves a recurring problem can actually create a business. Companies are built on outcomes, not checklists.