Expelee

New week. New repo. Same mission: → build lean → ship fast → learn loud

Let the ideas come. You don’t have to ship them all today. Write. Rest. Build when it’s real.

Taking Sundays off is not a weakness. It’s how you keep building next week without burning out.

The founder grind is romantic until it’s Sunday and you’re debugging a bug introduced by a Friday night idea.

3 signs a dev partner is legit: → they challenge your scope → they simplify your flow → they ship without drama

@jacksonurano Don't tell anyone.... I am an intern not a founder.

@0xExpelee Don’t tell anyone.. I wouldn’t call myself a technical founder either lol

Hey non-technical founders, What do you even do?

@jacksonurano Well it's more of the job being ensuring everything non technical is in order for the dream to turn into reality.

@0xExpelee Your job becomes “convince others to build my dream"

@chandlerjward This is the mindset most of us need, but most people start their projects for the funding and to turn it to a company, but if your project is good enough, that will happen on its own.

You don't need to be accepted into an accelerator or residency to stop calling your project a company. You don't need investor capital to grow. You don't need permission. Just build things.

@ayteksokmen I can build it my way, and maybe my way is better?

How do you keep coming up with new ideas? How do you stay motivated even when you realize that the thing you want to build has already been built ten times?

@itsanirbanroy Mostly followers, but maybe these connections help you land clients? You never know, so the best is to keep posting and keep growing on X, while not expecting anything out of it.

Just wondering have you ever got any customers from Build in public community or only followers

@shipitabhi Listen to people around you, you'll find some problem whose solution you'll be able to build, maybe under some 7 year old long aah reddit thread lies an idea worth building upon.

I’m a software dev (~1 yoe), built solid things at work, but now I’m trying to explore building outside the corporate bubble. The hard part? I don’t know what to build. I’m stuck on finding ideas worth building. If you’ve been here a while, any tips for someone just starting out?

@webpnkdotdev Around 80% of the popular posts here are shit posts, the rest 20% consist of people asking actual doubts their builds, and sharing their wisdom, which gets buried under the shitposts unfortunately

Funny thing - I don’t see a lot of folks actually BUILDING here. They write motivation posts, share their wisdom, debating, asking cursor or claude. It’s all good but I think we’re missing the whole point

Shipping is easy. Explaining why it matters — that’s the hard part. Clarity > complexity.

Code is cool. But knowing when to not code — that’s power.

Tech maturity is realizing most bugs aren’t bugs. They’re design decisions with side effects.

Feature bloat feels like progress until you try to ship it.

Things that save founders money: → Clear scope → Fewer features → Faster feedback → Saying ‘no’ earlier and maybe some embezzlement here and there

Some weeks you sprint. Some weeks you refactor. Some weeks you just hold it all together. They're all progress.

If your product needs a paragraph of explanation, it's not ready. Simplify the promise, not the ambition.