ED

Introducing: Build In Public: → Claude Code for building in public Marketing is dead for builders. The ones winning are documenting their work and turning it into distribution. 👇Here's how:

@tdinh_me buildinpublic.so

If you have a side project, share below. I'll retweet some interesting ones to give you more attention 😄 I'll do this every month to encourage more people to build side projects and escape 9-5.

@bbeigeworld oh wow that's mad

@eddspire their api keys been for sale at least

am I missing out for not looking into clawdbot or is it just FOMO talking?

@bbeigeworld have people been hacked already?

@eddspire too many permissions can leak your keys etc, better wait out

built onboarding that starts before you even sign up. landing page hero section = first micro-commit. type one ship moment right there. no account needed. then when you hit onboarding? same data's already waiting for you. psychology trick: get people to micro-commit. They convert better. stole this from checkout flows. works for saas too.

my new content workflow: 1. ship feature 2. custom claude code skill writes commit message (build in public style) 3. buildinpublic.so generates content from it 4. publish takes 5 minutes total. used to spend hours wondering what to post. now i just build and the content follows.

@starter_story not enough if I'm being honest, just some direct outreach in DMs I'm on it 🫡

@eddspire what about my 2nd question? :)

It's the 2nd Saturday of 2026. I have two questions for you: 1. what did you ship today? 2. what did you do to get it in front of 100 people?

I'm building Claude Code for build-in-public: try FREE for 7 days no CC required: buildinpublic.so

i'm building my first mobile app with 0 experience shouldn't take more than 3-4 days • firebase • react native • express backend recently i launched claude code for building in public and instead of talking about what it does i'm gonna building something new in public using it to prove it works let's see how this plays out

i'd ship every day but post... never 9pm. just finished coding. brain is fried. "i should tweet about this." but then i'd have to: explain what i built. why anyone should care. who it's even for. fuck it. too much thinking. i'll do it tomorrow.

ran a family fast food business doing £5k/week. zero profit. spent 2 years thinking revenue meant success. it didn't. the system was broken from day one. business eventually died. that failure taught me more than any win: surface numbers mean nothing. systems are everything.

3 years ago a single rejection could kill 2 weeks of momentum. i'd spiral. overthink. rewrite everything. convince myself i wasn't good enough. yesterday i got rejected by someone i really wanted to work with. read it. shrugged. moved on in 30 seconds. what changed? i stopped treating each no like a personal attack started treating it like what it actually is: one person's opinion on one day. the game is volume. always has been. remember: you're not getting rejected. you're just finding your people faster.

@ElitzaVasileva you forgot to mention you gotta be a woman lol

Guide on how to go super viral on X : 1⃣ Take a selfie with your laptop - bonus points if there’s code on the screen 2⃣ Post it when normal people don’t work - weekends, late evenings 3⃣ Write about how hard you hustle (apparently the algorithm loves that) 4⃣ Share it in the Build in Public community 5⃣ Prepare for a dose of hate and cringe comments 6⃣ Sit and wait - in ~24 hours it will explode Yes, this is self-irony! Anyway. Next post is probably me grinding on a Saturday 😂

@t_k_d_4444 while I agree to the last part, bip is definitely not stupid it's helps you "making it" and you're not building the skill of building in public but organic marketing, content, storytelling, consistency etc...

@eddspire building in public is stupid no one cares until you've made it then they wanna know how you did it

Introducing: Build In Public: → Claude Code for building in public Marketing is dead for builders. The ones winning are documenting their work and turning it into distribution. 👇Here's how:

building in public sounds easy. "just share what you're working on" but here's what actually happens: • you ship a feature. • you forget to post about it. • 3 days later you can't remember what you built. so you post nothing. the gap between building and sharing kills momentum. then when you finally do share , you need: - storytelling - banger hooks - good packaging most builders give up here. so i built something that does both — captures what you ship, and writes the content for you.

you know that feeling when you fix a bug? and the solution is so obvious you want to delete your github account? just spent 3 hours hunting a "silent failure." endpoint returning 200 but not working. turned out my response interceptor was unwrapping data. so response.data didn't exist anymore. i was checking a field that literally wasn't there. changed 2 lines. everything works now. this is what building feels like when you're learning as you go.