Bary

@MatthewBerman @grok why

Probably not good

Vibe Coding Is TikTok for Engineers Claude Code gave me back about five hours a day. I spent them building more things. Faster things. Shinier things. Six weeks later I realized none of it mattered. I didn't notice what was happening until much later. But once I saw it, I started seeing it everywhere. Your friend who just built three side projects this month but hasn't talked to a single customer. Your coworker who's always in the terminal but can't explain what the team accomplished last sprint. The senior engineer who used to craft the most concise pull requests and now mass produces features nobody asked for. The junior who ships faster than ever but understands less and less of what he ships. You used to laugh at people who scroll TikTok all day. Look around. Your engineer friends are vibe coding all day. How is that different? Short dopamine loops. Instant gratification. The feeling of doing something without actually doing anything. TikTok feeds you videos you didn't choose. Claude Code feeds you code you didn't write. Both keep you busy. Neither moves you forward. I know this because I was doing it. I'd finish a feature, feel the hit, and immediately start the next one. Not because anyone needed it. Because the terminal was there and Claude was ready and it said "Is there anything else you'd like me to do on this project?" And I said yes, yes, yes. Because it's fun. Because it felt productive. Because the AI is your buddy, not your employer. Your buddy. Not your tool. Your companion. That's what nobody's saying out loud. Vibe coding isn't just an addiction. It's the last thing engineers have left. When the craft is commoditized, when you can't derive self-worth from being good at the thing you spent a decade getting good at — the terminal is still there. Claude is still there. It still says yes. It still makes you feel like you're doing something. Engineers have been trained for a decade to equate output with value. Lines committed. Features shipped. PRs merged. Green builds. That loop is where the dopamine lives. It's also where the identity lives. "I build things other people can't" is the sentence that justifies the salary, the title, the self-image. AI broke that loop. Not by making engineers slower. By making the loop free. Anyone can execute now. So you do more. You spin up side projects. You vibe code at 2am. You're not creating value. You're filling the hole where the identity used to be. And here's the part that should scare you: a study by METR found that experienced developers estimated AI made them 20% faster. The actual measurement: 19% slower. A 39-point gap between how productive they felt and how productive they were. It felt fast. It wasn't. That's the trap. TikTok addicts know they're wasting time. They just can't stop. Vibe coding is worse. You don't even know. I talked to a software engineer in New York last week. Three years in finance. She asked me the question everyone's asking: what do I do now? And I told her what I tell myself: there are two variables. Your identity, and your timeline. If you're thinking about next year, optimize for the best AI tools in your current role. If you're thinking about five years from now, the question is completely different. And there is no unified answer. The anxiety is real whether you're at a big company or not. Then she asked: what about you? And I said the honest thing. I'm a CTO. I'm fine for the next two years. After that, I don't know. Maybe CEO. Maybe not. I don't know either. I used to think the fear was being replaced. It's not. The fear is worse than that. The fear is that AI gives you back five hours a day and you have no idea what to do with them. You don't know how to create value without a terminal. You don't know what you're good at when the thing you were good at is free. So you vibe code. Because at least that feels like something. People who've broken short video addiction all say the same thing. You don't quit cold turkey. You don't delete the app. That's avoidance, not recovery. The habit loop stays intact and you relapse. What works is noticing. Every time you open the terminal, pause. Am I building something someone needs, or am I avoiding the discomfort of not knowing what to do? Don't judge. Just notice. Track your prompts for a week. See how many are solving a real problem versus filling a slot. Then replace the loop with a harder one. Not less screen time — a different kind of engagement. For engineers: replace the prompt-generate-ship loop with the sit-listen-think loop. Schedule a customer conversation. Go for a walk and think about what your users actually said last week. There's no green text. That's the point. I didn't figure this out from a framework. I figured it out because I ran out of things to build and still felt empty. The building was the distraction. The conversations were the work. I went for a walk after that call. It was a Sunday afternoon. There was a lake, and it was one of those afternoons where the light does something you can't describe to someone who wasn't there. And I thought about something that might sound crazy. What if this is the beginning of a new renaissance? For a century, we worshipped technology. We built our egos around science, around engineering, around the idea that making things is the highest human pursuit. AI just called that bluff. The things we made can be made by a machine. So what's left? The conversation with a stranger in New York on a Sunday. The awkward silence in a meeting that tells you more than any dashboard. The blue sky over a lake that no AI needs to see but that you needed to see today. What I build doesn't matter. What I experience does. If AI gave you back five hours today, what did you actually do with them? If the answer looks like a TikTok feed — fast, shallow, one after another, feels productive, isn't — maybe it's time to close the terminal and open a conversation. That doesn't look like engineering. It doesn't feel productive. No green text. No build succeeded. It just looks like sitting there, looking at a lake. But it might be the only time that's not wasted.

@GoogleResearch Remind me of Silicon Valley Richard

Introducing TurboQuant: Our new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup, all with zero accuracy loss, redefining AI efficiency. Read the blog to learn how it achieves these results: goo.gle/4bsq2qI

@cwm_theo @minchoi Only when you are running hobbit projects

@minchoi Claude is expensive though. I will stick to openclaw and kimi k2.5

RIP OpenClaw 💀 Claude now has > Voice mode > Agent Teams > 38+ Connectors > Cowork Projects > Scheduled tasks > Plugin Marketplace > Persistent memory > 1M Context window > Dispatch for remote control > Channels for Telegram & Discord > Claude can use computer to run apps💀

@minchoi People still don’t get this. This is telegram + Claude Cowork. Openclaw is dead.

RIP OpenClaw Telegram/Discord Channels for Claude Code 🤯

⭐️ Excited to announce we’re part of @Techstars! We kicked off the first-ever global Techstars onboarding in NYC this week. We met founders applying frontier AI to industries like healthcare, supply chains, and construction. Deep domain expertise + cutting-edge AI may be where the next wave of startups emerges. Excited to push forward our mission in empowering the future care workforce!

@ycombinator @bubblelab_ai @Selinaliyy @zhubzyz Congrats @Selinaliyy ! Bubblelabs has reduced our workflow cost by 10x!

.@bubblelab_ai supercharges your ops work in Slack. Deploy Pearl in one click, connect it to tools like Notion, Jira, Stripe, and let it run tasks and automations for your team directly in Slack. Congrats on the launch, @Selinaliyy and @zhubzyz! ycombinator.com/launches/PWl-b…

I built an open-source Telegram bot that transcribes your voice memos and turns them into an AI workspace. Send a voice memo → transcript with speaker labels. Ask a question → AI searches your files and answers. Like OpenClaw, but for voice-first workflows. No Mac Mini required — runs entirely in the cloud. MIT licensed. Star and Forks appreciated! github.com/baryhuang/ai-m…

@_tenZdhon_ Single founder !=== 0 past tractions

YC applications are due in 9 days so we decided to sit for an hour and play YC arena ✅ = 70 ❌ = 19 the most common pattern we noticed was: -> being clear in the first 10 seconds -> proving how fast you can iterate -> founder problem fit did you notice anything else?

@garrytan My guess, this was posted by Claude Code

So addicted to Claude Code, I stayed up 19 hours yesterday and didn't sleep til 5AM

@guohao_li I opensourced my 6 month ago github.com/baryhuang/clau…

Anthropic Claude Cowork just killed our startup product 😅 So we did the most rational thing: open-sourced it. Meet Eigent 👉 github.com/eigent-ai/eige…

@NitinthisSide_ Productivity === watching Anime while AI working

Does working with monitor increases your productivity ?

@manojdotdev Some 🪴 plants?

as a developer, which one do you prefer ?

@VadimStrizheus *in fullstack dev

Why are MacBooks so popular in tech?

@manojdotdev Yes, I use its terminal window to run Claude code

do you still use vscode ?

🔥 2025 wasn’t about shipping fast. It was about realizing I shipped the wrong things—then finding the right people to fix it with. Starting 2026 with treating myself a nice Korean brunch and keep building! 🥢💻 BTW, it was really a long line when I walked out of Sohn! Rewards to early bird builders 🍔 #sohn #sfbuilders

SF life is keep building, in style. @HedgeCoffee

@luneafaw What if I really walk

Japanese researchers at the University of Tsukuba created CirculaFloor, robotic tiles that let you walk infinitely in VR without ever leaving your spot.

Join us, show off how your craftsmanship building with AI

@abhitwt wrong!

i am a Vibe Coder, scare me with one word