Heddle Founder

Joined August 2013
356 Photos and videos
// Lofty retweeted
Move over Grit, sley is slaying
Git: lighter, faster, and smaller đź‘€ heddle.sh/blog/sley-vs-git
1
1
26
// Lofty retweeted
SpaceX has exercised the option to acquire @cursor_ai in an all-stock transaction with the goal of building the world’s most useful AI models. For the past few months, SpaceXAI has been jointly training a model with Cursor, which will be released in Cursor and Grok Build soon. We look forward to working closely with the Cursor team to advance our frontier AI capabilities
Apr 21
SpaceXAI and @cursor_ai are now working closely together to create the world’s best coding and knowledge work AI. The combination of Cursor’s leading product and distribution to expert software engineers with SpaceX’s million H100 equivalent Colossus training supercomputer will allow us to build the world’s most useful models. Cursor has also given SpaceX the right to acquire Cursor later this year for $60 billion or pay $10 billion for our work together.
1,452
3,605
31,554
17,937,566
big if true
1
2
175
Feels like @maria_rcks should have a lakebed app that lets you guess which model wrote something
Hot take: a lot of people wouldn’t be able to tell the difference if they were randomly routed between gpt-5.5, opus-4.8, or fable-5 for their day to day work
33
// Lofty retweeted
Here are my 7 phases of AI-powered development. I've been thinking that the pre-PRD phase needs more structure. You need to figure out the shape of the design tree first, before then walking down it with higher-fidelity prototypes. In other words, /grill-with-docs needs to change again IMO
97
187
2,661
186,120
// Lofty retweeted
Heddle needed a better embedded git implementation, so I built it. Very promising so far, it doesn’t just beat other libraries, it’s beating git 🔥🔥
maybe rebuilding Git from scratch wasn't such a bad idea after all đź‘€
1
1
50
maybe rebuilding Git from scratch wasn't such a bad idea after all đź‘€
1
2
92
Nobody else has a model so good that a world superpower called dibs
I’m a Codex users, Why should I switch to Claude?
1
87
// Lofty retweeted
last one
159
2,673
47,150
982,508
Fable is very smart. Smart enough that its output plans can raise the quality of other models just by handing off work. So no, we can’t agree. Fable measurably produced better, cleaner code from other models (especially Opus and Sonnet, 5.5 needed some massaging for Fable to figure out how to prompt it but we got there after a couple tasks)
Please be serious about Fable: for day to day coding, can we agree it doesn't change a lot and the hype is 10x the real value or no?
1
38
New life goal. Build something so good that a world superpower calls dibs.
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Claude models is not affected. We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible. Read our full statement: anthropic.com/news/fable-myt…
1
1
45
// Lofty retweeted
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees. The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance. Access to all other Claude models is not affected. We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible. Read our full statement: anthropic.com/news/fable-myt…
12,608
25,784
88,144
90,276,291
Well this aged like milk
Fable 5 just changed outbound. All you need is: - A laptop - A Claude Max subscription - 10 minutes to install once That's enough to run a complete outbound stack covering prospect, research, sequence, CRM, enrichment, deliverability, and pipeline review. No expensive sales tools. No building prompts from scratch. No remembering which skill handles which task. Most people still use Fable 5 for one-off prompts... But the engineers pulling consistent pipeline are quietly using Fable 5 to: - Build a prospect list from ICP filters in under 2 minutes - Research any account and return a ready-to-use brief before every call - Write a 5-touch sequence calibrated to the specific signal that triggered the outreach - Run a pipeline health check and flag every deal with no next step, no recent activity, or a close date that has already passed - Route any outbound task through one router skill that chains the right skills automatically without you remembering what anything is called Usually, I sell this 89-skill bank for $97... But today you can get it FREE. Inside you'll discover: 89 skills filtered from the full sales-skills/sales repo for engineers doing outbound and pipeline work — everything not relevant has been cut The /sales-do router skill that takes your objective in plain language, asks a few multiple-choice questions, and returns a detailed copy-paste prompt with your full context loaded Platform skills for Salesloft, Apollo, Lemlist, Smartlead, and Instantly with prompts calibrated to each tool's native workflow CRM skills for HubSpot, Salesforce, Attio, Pipedrive, and Close covering deal inspection, pipeline hygiene, and forecasting Multi-step workflow chains that take you from a company name to a prospect list, enriched and verified, to a reviewed ready-to-send sequence in one session Want it? Like this post Comment "SKILLS" Follow me to receive it in DM Available FREE for 48 hours only.
23
Imagine how good GitHub would be if their incident reports looked like this
Jun 12
Our deepest apologies for the downtime today between 13:17 and 14:18 UTC. Tens of thousands of businesses trust Polar with their billing, and an incident like this should not happen. We'll publish a full post-mortem in the coming days and take actions to make sure it does not happen again. In the meantime, here's exactly what happened. We rotate secrets frequently as a security policy. Today we rotated our database credentials – but a flaw in our config, where the credentials were tied to the database's Terraform resource, caused Terraform to trigger a full resource replacement. Our production database was replaced. It took us an hour to restore and bring everything back. Was any data lost? No. We run point-in-time recovery with remote backups, hosted on Render with enterprise support. We immediately began a PIT recovery, replaying WAL up to the moment before the Terraform change applied. Recovery completed at 14:16 UTC; we confirmed full data integrity and brought infrastructure back online at 14:18 UTC. A few edge cases we're reconciling now – none involve lost data: — Our API stayed up for ~50s after the latest point in time recovery point and kept accepting event ingestion (which we double-write into Tinybird). A few hundred events landed there; we're going to replay them. — We received 3 Stripe webhooks for in-flight transactions as we went down. We're resolving these and reaching out to the affected customers directly. — After restore, our webhook worker was properly restarted to point to the recovered database. That's fixed; it's catching up now, so webhook delivery is delayed but recovering. Polar is fully operational. The only residual effect was delayed webhook delivery while the worker catched up, which it has now. No action is required on your end. Our post-mortem will detail the full timeline and the guardrails we're adding so this class of failure can't recur, and we’re truly sorry it happened in the first place.
2
7
2,075
So now you can stack codex limits?? And you get to pick when they apply?? Exactly how much compute does OpenAI have sitting idle all the time? This can’t be sustainable.
1
39
// Lofty retweeted
Worktrees are brittle and require careful scripting and care. If you’ve figured them out, more power to you. Heddle brings you threads. All the power of a worktree with none of the headache.
Am I the only one who thinks git worktrees are fucking confusing?
1
1
1
49
Agents tend to drift towards hyper focused engineers, iterating on a small scope problem until they brute force the solution. I’m starting to find that these loops need to have an orchestrator AND a “big picture” agent to make sure proper architecture decisions are made. @mattpocockuk skills are a great start but the thing that has helped my long-running agents build cleaner code is having a high level agent gently guiding things with.
31
Be like @elonmusk, don’t let little things like the laws of physics get in the way of your dreams
I’m old enough to remember a few months ago when the timeline was filled with “data centers in space don’t work because physics” takes
2
3
51
Hot take: model benchmarks depend heavily on the user doing the prompting rather than just the intelligence of the model.
Been fighting a bug all morning with Codex 5.5 and Opus 4.8 just fixes it in 3 prompts with proper debugging. I’ve come to the conclusion that no one knows what model is best. The whole thing is just vibes because it’s fundamentally impossible to measure.
1
1
35