I thought why have both codex pro and claude max together at the same time so cancelled my claude max recently , but then this hype of claude fable 5 came yesterday and just took claude max again for the fable 5 only to see this shi today morning .. man its so annoyingg.. do i have to take a fucking 2000$ flight to SF to just use claude huh...

Just found about this -> around 1M$ in startups credits , If you are a startup owner or vibe coder whos building something meaningful and grinding hard this is for you.. startupperks.xyz/

I was using claude cowork to fix and security test client workflows and it gave me out free 3 invites of claude cowork for a week.. Feel free to redeem it if u guys wanna , cowork is godly imo. claude.ai/referral/Ts6ZR55Sv…

this is awesome man.....

The start. Where it all began. It's been 2 years since I got an idea called Hollerlabs and started it with my business partner @devautomates @Saisharan0099. But we ended up building a trend-following business one that changed based on whatever was popular in the market. After 2 years of that, we realized we weren't really building anything. We were just taking ideas that weren't ours, adding a prompt, and shipping them. So we decided to stop. 6 months ago. One of the best decisions we've ever made because we actually started thinking instead of following. If you look at my profile, my favorite quote says it all: "Building without thinking is just assembly." We finally started working toward what we actually set out to achieve. Proud of what the last 6 months have looked like. Genuinely grateful. The reason I'm writing this if you ever feel like you're not doing something you love, just stop and think. Most of the problems that stay on your mind have the simplest solutions.

chasedesk.app in beta now

Things are moving too fast.. nowadays u can do anything and everything with claude(wish i could cook food with claude code as well....)

What are best agents to use in claude code ?

Why Vibe Coding with Claude changed how I build in 2026 I used to fight with prompts. Now I just describe the vibe I want and Claude gets it. My daily flow: • Start with the feeling (“clean, calm, fast”) instead of technical specs • Let it think step-by-step like a thoughtful senior dev • Iterate naturally in conversation • Use agents to handle testing, refactoring, and edge cases The code comes out better. I move faster. And honestly… coding feels fun again. This isn’t hype. It’s just the new normal for me. Anyone else fully in vibe coding mode with Claude or other agents? What’s one thing that surprised you?

most people using claude code are leaving 80% of the tool on the table. this thread is the 80%.

i used claude code wrong for 3 months straight then i read how anthropic engineers use it internally wrote 23 pages so you don't have to figure it out the hard way the stuff nobody talks about 🧵 __ CLAUDE.md is the whole game you put your architecture, client rules, and conventions in one file claude reads it every single session automatically every dev skips this. every dev wonders why outputs are inconsistent __ there's a context window death spiral nobody warns you about 70% full → claude loses precision 90% full → it starts making things up you don't notice. quality just quietly gets worse fix: /compact at 70. /clear at 90. that's literally it __ reply CLAUDE and i'll dm you the full 23-page course free covers mcp servers, agent teams, ultraplan, hooks, headless mode all the 2026 features. all with code examples if this hits retweet it - someone you know is building with claude code and getting it wrong

Most automation devs over, engineer. You match tool to problem, not ego to resume. The real edge is knowing when a Zapier zap beats custom code. That decision alone saves clients more than the automation itself.

most companies automate high, volume tasks while the messy handoffs that actually slow teams stay manual. Coinbase had clean data infrastructure. most don't. when does automation create more coordination tax than it saves?

I'd flip that. you're testing versus scaling. codex writes the script fast, but n8n gives you version control, error handling, and a visual map when someone else inherits it six months later. the real question is whether you're building a one, off or maintaining it.

the friction isn't approval, it's the context switch. mid, flow popup kills momentum, so you approve blindly just to keep moving. physical button keeps hands flowing while brain stays locked in. turns interruption into rhythm, not a full stop.

most teams automate first, diagnose never. you're flipping it, mapping the breakdown before touching a tool. that's the difference between a feature that sits there and a system that actually changes how work gets done.