Laurita

New in Claude Code: Remote Control. Kick off a task in your terminal and pick it up from your phone while you take a walk or join a meeting. Claude keeps running on your machine, and you can control the session from the Claude app or claude.ai/code

this is wild. had to create another max account, and rant out of tokens in <3 hours. Anyway, that led me to try codex. Let's see.

What a great feeling it is to try a new model on a bug that's been bugging you for weeks, and have it work perfectly. Im a fan Opus 4.6 @AnthropicAI

Me cago en to me cogió opus 4.6 launch sin tokens 😂

Introducing Claude Opus 4.6. Our smartest model got an upgrade. Opus 4.6 plans more carefully, sustains agentic tasks for longer, operates reliably in massive codebases, and catches its own mistakes. It’s also our first Opus-class model with 1M token context in beta.

wild

Anthropic just took a big swipe at OpenAI's decision to put ads in ChatGPT. Anthropic is airing ads mocking ChatGPT ads during the Super Bowl, and they're hilarious 😅 Anthropic is also committing to no ads in Claude theverge.com/ai-artificial-…

Dear @Meta, please create an MCP to post ads.

Update 🚨 Aparecen billboards en Puerto Rico de Uva Si el día del 🏈🏆 se canta la parte de “Uva Uva 🍬”, el UVA App va a activar artículos a $1 mientras dure el show o hasta que se agoten (lo que ocurra primero) *T&C aplican*

nvm. llegué tarde al pari skills.sh

remotion skill is wild

Thank you, Claude.

The world belongs to the fast

~80% of my Claude Code prompts invoke at least one plugin. Mostly using Anthropic’s, Expo’s, and Vercel’s. Any must-haves I’m missing?

I have only 30+ years of experience as an entrepreneur, but I too agree. The only way to truly know whether an idea is good or bad is to test it. Good news is that it's easier to test ideas now than it has ever been.

Hire out of pain. Don't hire because you think you'll need someone soon or maybe sometime later. Wait until you or your team are actually hurting: working weekends, missing family dinners, dropping balls. That pain is the signal that the role is real. I learned this the hard way after watching founders (including myself) hire ahead of need and end up with people in roles that weren't fully formed yet. When you hire out of pain, you know exactly what the job is because you've been doing it yourself. You can evaluate performance because you know what good looks like. And the new hire knows you'll step back in if they fail, because you were just doing it last week.

Glimpse of a world of fully generative interfaces. AI → JSON → UI: github.com/vercel-labs/js…

I'm just a girl in the world

John Collison: We only had 50 users two years after founding Stripe “We started working on Stripe in the Fall of 2009, and we launched Stripe in September 2011,” John Collison reflects. “I remember right at the beginning when we were starting it I said to Patrick [Collison], ‘Yeah let’s do it. How hard can it be?’ Which gives you a sense of our mindset. And the answer was: two years of difficulty. We had not predicted that.” John remembers feeling dejected when Stripe only had 50 users two years later: “When you spend two years getting 50 users, it doesn’t feel like a whole lot of progress. It feels like things are going pretty slow.” But this is one of the challenges of startups, he argues: “If you’re working on a startup that’s a bad idea, it’s going to feel like slow-going. But if you’re working on a startup that’s a good idea, it may feel like slow-going too.” Yet slow growth has a silver lining: “I think the thing that allowed us to take off in the subsequent years was the fact that since we were spending so much time on each one of those users; since we were hyper-focused on building a great product; and since we weren’t dealing with problems of scale yet, that allowed us to build the product that we wanted. Part of the culture that set in really early on was taking abnormally good care of those early users.” The Stripe founders would get an email or phone call anytime a user ran into a bug. When they sent the customer an email moments later alerting them that the bug was now fixed, people’s minds were blown. They set up a Campfire room that any customer could join and use to message John and Patrick at any hour of the day or night. And if a user was based in the Bay Area, the founders would invite them to come by the office and help integrate Stripe for them. In the Stripe dashboard they would prompt their customers for feedback and feature requests. Then the Stripe founders would reply to that feedback within 10 minutes. “What this meant was that even though the user growth was happening quite slowly in the early days,” John explains, “it actually had a pretty surprising viral effect where people had a good experience, they told their friends about it, and we were able to spread entirely through word-of-mouth even to this day.” Video source: @ECorner (2015)

I wonder... does the “we will not train on your data if you pay for it” apply here?