Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

IT'S NOT THAT HIS FABLE 5 IS MORE CAPABLE THAN YOURS. IT'S THAT HE LETS IT KEEP WORKING. MOST PEOPLE BUY AN AI BUILT TO OPERATE FOR DAYS THEN SHUT IT DOWN AFTER A FEW MINUTES. Nine out of ten users open a chat, assign one task, and close...

21,945 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

ANTHROPIC'S PRODUCT CHIEF HAS USED CLAUDE FABLE 5 FOR MONTHS BEFORE ANYONE ELSE. HERE'S WHAT HE LEARNED ABOUT THE MOST POWERFUL MODEL YET Mike Krieger co-founded Instagram and now runs product at Anthropic. He's had Claude Fable 5 for two months before the public, and his takeaway is that it changes how you have to work, not just how much you get done. Here's what stood out, and what to actually do with it 1. It holds the whole project, so stop chopping tasks small. The old habit was breaking work into model-sized pieces and stitching them. Fable keeps the whole thing in context. What to do: stop pre-slicing your prompts into tiny steps. Hand it the full goal and the intent behind it, the way you'd brief a senior engineer, and let it sequence the work itself 2. Delegate big, async, and overnight. He sets it on a hard task at night and wakes to it finished, including the model getting itself unstuck when a service died, scaffolding a workaround, and documenting it. What to do: stop babysitting one prompt at a time. Kick off long jobs and walk away. Run several sessions at once instead of one you watch 3. The skill is planning now, not typing. His day moved to long architecture conversations up front, then execution in chunks. What to do: spend your first prompts planning, not building. Then ask it to output an HTML page or markdown doc of the plan so your team aligns before any code is written. That early alignment is the new leverage 4. Match the effort level to the task. Fable's range is wide, so a heavy reasoning pass on a tiny UI tweak is overkill (and pricey). What to do: dial effort down for small jobs, save the deep thinking for hard ones. And don't use your most expensive model for quick questions, keep a fast model for those 5. Verification is the real bottleneck now. The hard part isn't getting output, it's trusting it. What to do: make every change ship with proof. Have Claude attach a screenshot or video of what it built, so you can see the result instead of reading the diff. Then stand behind the decisions yourself before you merge 6. Cost is per-result, not per-turn. Fable is expensive per call but often one-shots what other models need ten turns to get right. What to do: judge cost by what it takes to finish the task to your satisfaction, not the price of a single message. Give it a real task and see how far it gets before you jump in His bigger point: software engineering isn't over, it's different. The craft moved from writing code to owning intent, taste, and what actually ships. The floor rose so anyone can build, and the ceiling rose so experts go further than before Bookmark this

Yarchi

30,958 Aufrufe • vor 3 Monaten

A developer in Hangzhou runs an AI that remembers everything about him for $0.40 a year. No vector database. One file that never grows past 4,000 tokens. He published the whole schema. His version starts from the opposite idea. Memory is not storage. It's a write policy. Six fields. Rewritten every time, never appended: > IDENTITY - who you are, what you build. 300 tokens. Changes monthly at most > STATE - what you're on right now. 400 tokens. Rewritten daily > DECISIONS - what's already settled, so nothing gets re-argued. 800 tokens > CORRECTIONS - every time you said "no, not like that." 600 tokens > PEOPLE - names, roles, who's waiting on what. 500 tokens > DEAD - tried and abandoned, so it never comes back as a suggestion. 400 tokens Three thousand tokens. Ceiling of four. When a section fills, the model rewrites it shorter. Nothing is ever added. Only replaced. Kimi K2.5 bills $0.10 per million cached input tokens. Four thousand tokens a turn is $0.0004. That's 2,500 turns for a dollar. The free tier hands you 1.5 million tokens a day. 375 turns before you pay anything at all. CORRECTIONS is the field nobody builds, and it's the one that does the work. A model that remembers being wrong stops repeating it. Everyone else is paying to search their own history. He pays to keep it short. The bill stopped growing when the file did. Your memory system isn't defined by what it stores. It's defined by what it agrees to delete. The article below is the full build - schema, rewrite prompts, the compaction rule that keeps it under the cap. Save it. You'll want it open in the other tab.

wast3

15,862 Aufrufe • vor 28 Tagen

To be a successful founder, you have to believe that what you're working on is going to work — despite knowing it probably won't! That sounds like an oxymoron, but it's really not. Believing that what you're building is going to work is an essential component of coming to work with the energy, fortitude, and determination it's going to require to even have a shot. Knowing it probably won't is accepting the odds of that shot. It's simply the reality that most things in business don't work out. At least not in the long run. Most businesses fail. If not right away, then eventually. Yet the world economy is full of entrepreneurs who try anyway. Not because they don't know the odds, but because they've chosen to believe they're special. The best way to balance these opposing points — the conviction that you'll make it work, the knowledge that it probably won't — is to do all your work in a manner that'll make you proud either way. If it doesn't work, you still made something you wouldn't be ashamed to put your name on. And if it does work, you'll beam with pride from making it on the basis of something solid. The deep regret from trying and failing only truly hits when you look in the mirror and see Dostoevsky staring back at you with this punch to the gut: "Your worst sin is that you have destroyed and betrayed yourself for nothing." Oof. Believe it's going to work. Build it in a way that makes you proud to sign it. Base your worth on a human on something greater than a business outcome.

DHH

96,644 Aufrufe • vor 1 Jahr

BREAKING: Anthropic just dropped Fable 5.1—and CLAUDE IS SO BACK. We’ve spent the last week testing it at Every 📧 across coding, writing, and knowledge work. Our verdict: It's finally Fable for everyone. It’s the strongest coding model we’ve used, but now it's fast, token-efficient, and CRUCIALLY actually speaks like a normal person. Here’s our vibe check: - A monster at coding. Kieran Klaassen rebuilt a working version of Proof, our document editor, from one prompt. It added useful details he hadn’t requested, and it handles enormous coding jobs that run for days at a time. It built a computer use Mac app for me called Hands in one-shot that other models failed at. - A Claude our writers want to use again. It has clearer prose, fewer AI tells, and it takes an edit without arguing. It's a significant upgrade over Opus 5. And won Katie Parrott's heart back. - About half the tokens as Opus 5, and much faster. In our Slack-agent tests, it delivered comparable results to Opus 5 using about half as many tokens, in about 60% of the time. - Knowledge work you can delegate. It can produce great knowledge work—like slide decks—end to end without making slop. And flew threw hammer's tests with flying colors. - It now supports zero-data-retention agreements. Now businesses can actually use it! A big barrier to Fable adoption is gone. Net Result: It's obviously an Opus 5 killer. If that was your daily driver you should switch today. If you're using GPT-5.6 in ChatGPT for Work, it's spinning the wheels on for big delegated tasks. I still use ChatGPT for Work more day to day, but I use way more tokens in Fable 5.1. I send it off at the beginning of the day to do big programming projects, like end to end MVP builds, and check in every once in a while. State of Play: The big knock on Anthropic was they built a supergenius in a datacenter that was almost unusable. It was too slow, argued back, and talked in technical gibberish. They've managed to solve those problems and more with Fable 5.1!

Dan Shipper

204,342 Aufrufe • vor 18 Tagen