i kept building because launching scared me

over the last couple of weeks, i worked on more ideas than i ever have. not because i was trying to start 11 companies. i just had ideas that i couldn't stop thinking about, so i started building them.

some turned into working products. some stayed unfinished. some were mostly ideas that never became more than a repo, a rough prototype, or a direction i wanted to test.

here's what came out of my head:

• summon — pokemon go, but with real animals and on-chain collections.
• creativity — a place to capture ideas, work on them, and prove you actually shipped.
• cluch — live prediction battles with friends during sports matches, settled on-chain.
• learn-to-code — help people write their first 1,000 lines of rust.
• read — an offline, distraction-free reading app.
• veil — trade privately, settle publicly.
• signal — embedded ai inside all crypto protocols.
• shadow fuzzer — a private sandbox for on-chain agents to simulate transactions without getting front-run.
• latent-tech-news — a telegram bot that reads hacker news and sends short ai summaries of the best ai stories.
• friday — an ai that helps distribute your product.
• scout — a better way to find real yc jobs and generate cold emails worth sending.

looking back, i'm happy i touched all of them. every project, prototype, and idea taught me something new. some made me learn new tech. some made me think differently about products. some were just really fun to explore.

but i also made the same mistake again and again. most of these ideas never made it outside my mac. sometimes i built the interesting part. sometimes i only got a rough version working. sometimes it stayed as an idea. then another idea showed up. the new one always looked cooler. so i jumped.

i never really launched most of them. i never put the unfinished ones in front of real people. i never stayed around long enough to see which ones actually deserved to become products. that's probably the biggest lesson i've learned.

code doesn't make a product.
users do.

another thing i learned is that my first idea is almost never the final idea. what i build first is usually just a rough version of what's in my head. it still needs a lot more thinking, a lot more work, and most importantly, real user feedback.

i've realized that i can't decide what's good just by sitting in front of my mac. people use products in ways you never expect. they point out problems you never noticed. sometimes they even use it for something completely different than what you imagined. that's why launching matters. not because the first version is perfect, but because it's the fastest way to learn what the product should actually become.

another thing i realized is that i genuinely enjoy this. i like coming up with ideas. i like starting from nothing and turning it into something that works. i don't think i'll ever stop doing that.

but i also learned something the hard way. i can't bootstrap every idea i have. right now i don't have a job, so every product costs time, money, and attention that i don't really have. even if i could build ten products, i definitely can't grow ten products.

(if you're hiring, or if someone in your network is looking for someone who loves building, i'd genuinely appreciate an introduction.)

so instead of trying to build everything, i need to pick one and give it a real chance. the rest can wait. they're not bad ideas. they're just ideas for another time.

i don't regret building any of these projects. if anything, they helped me understand myself a little better. i'm someone who loves building.

now i want to become someone who also finishes, launches, and sticks around long enough to see people actually use what i build.

i think that's the next chapter.