AI Twitter kills me 🤦🏻 New AI product drops and suddenly everyone has been “testing it for weeks.” Bro you were glazing the competitor yesterday 😭 Every. Single. Time. Come on guys 😂

Saw @nitishkmrk's morphing discovery bar (via @alibey_10) and thought "okay I have to build this too" 😅 So I vibed code in a few hours and shipped it as an npm package gooey-search-tabs — morphing search bar with animated tabs for React - Tabs pill → search input morph animation - Spring physics with 4 presets - Gooey blob effect connecting tabs + bar - Keyboard shortcuts, full a11y npm install gooey-search-tabs Demo & docs: gooey-search-tabs.vercel.app GitHub: github.com/anl331/gooey-sear…

clipped a 30-minute video in under 1 minute no editing software no manual cropping no cloud uploads paste a url, AI finds the best moments, frames the speaker, and adds captions works with YouTube, Twitter, TikTok, Twitch, and 1000+ other sites free + open source github.com/anl331/vid-clippe…

Been heads down the past few days building out the automation engine for @useTCT. Finally wrapped it up today. Free users now get a 21-day conversion flow — push notifications, emails, promo codes — all triggered automatically based on behavior. What went into it: → Visual flow builder for drip campaigns → Deep linking — CTAs navigate directly to specific parts of the tool → Auto-generated promo codes via WHOP with countdown timers → Polished the notification system (rich text, badges, banners) → Runs on a 6-hour cron cycle, no manual work Building a Chrome extension is wild because you can't just send a push notification like a mobile app. You have to build the entire notification system yourself, from zero. The boring infrastructure nobody sees but makes everything work. Retention > Acquisition. If your free users aren't converting, the problem isn't traffic. #BuildInPublic

v0.2.0 shipped 🧈 initially I was thinking more knobs ≠ better library. so I stripped out squishDelay, expandDelay, expandDuration, collapseDuration from the API. now just two controls: 1. bounce (0.05 to 0.8) for spring intensity 2. displayDuration for visibility what's new: - center positions (top-center, bottom-center) - hover pauses the dismiss timer - hover a collapsed pill to re-expand it - action button morph-back ("Copied!" pill) simple > configurable. goey-toast.vercel.app

4 months building TCT full-time: 650+ users 62 paying customers ~$600 MRR No ads. No influencer deals. Just a Chrome extension and a Discord server. Growth is slow but every week someone new tells me they can't trade without it anymore. That's the signal I keep building on. @useTCT #BuildInPublic

Building a trading tool taught me something about traders: They don't want another chart indicator. They want something that makes them STICK to their own rules. That's what @useTCT is. A tool that asks "did you check everything?" before you enter a trade. Simple, but nobody was doing it. #BuildInPublic

Spent the last two weeks refactoring the entire @useTCT codebase. Split god components, killed dead code, centralized utilities. Not the fun kind of work. Nobody sees it. But the extension was becoming impossible to maintain at the pace I'm shipping. Now adding a feature takes minutes instead of hours. #BuildInPublic

Had my AI assistant set up to scan support tickets automatically Today at 3:30 it pinged me: "Found a bug report" By 3:51 — fix deployed. 21 minutes. And I was driving the whole time. The AI: • Found the ticket • Analyzed the codebase • Located the bug • Wrote the fix • Replied to the user explaining the issue + that a fix was already pushed I pulled over once to review the code and hit merge. Full support loop handled while I was on the road. Building @useTCT with @OpenClaw 🔧

Found an old Twitter account from a previous business today. ~10K followers, completely dormant. The followers have nothing to do with what I'm building now (@useTCT, a trading tool). Repurposed it anyway. Changed the handle, fresh start. Dumb move or underrated hack? Curious what others have done with old accounts. #BuildInPublic

Was researching auto-sync for broker journaling in @useTCT today. Wanted to poll users on which brokers they actually use. Realized we didn't have a poll feature. So I built one and shipped it this morning. Sometimes the feature you need is the one that helps you build the right features. #BuildInPublic

Been working on @useTCT for over a year now. Started as a tool for a private trading group. Now we're at 633 users and 59 paying members. The product is solid. Distribution is the hard part. Time to actually start talking about what we're building. #BuildInPublic

Two users account for like 80% of the features in my latest update. One wanted negative values for directional bias scoring. The other wanted editable trade notes. Shipped both. Small user base = you can actually listen to everyone. #buildinpublic

Starting to build @useTCT in public here Built a Chrome extension for traders last year. Launched to a small community, got my first paying users, then... life happened. Didn't touch it for 6 months. Came back in October, rewrote most of it, added a free tier. Where I'm at now: → 633 users → 59 paying customers → $595 MRR → 15% churn (working on it) I can build. Marketing and distribution? Still figuring that out. #buildinpublic