SDG retweeted
6.2 Astra is here. I’ve been testing it for awhile.
I think this is the worst model OpenAI has ever released.
I’ll share more soon.
RT @cramforce: The TL;dr is that static credentials leaked through stolen LLM transcripts that contained the transcripts.
The only real fi…
This quoted post is unavailable.
bring your bot to meetings!
it's a great way to let them gather their own context, making your bots smarter. or if you're about to board your flight without Starlink, your bot can still attend on your behalf and take notes
to get started, just ask your bot!
one of the best ways to get the most out of grok bot is with our many connectors. the more context and tools your bot has, the more helpful it can be to your work and life!
try asking bot to look at messages from your family and update your calendar for important events
or look at messages from potential clients for your small business and help manage your bookings
SDG retweeted
Self-hosted Claude Managed Agents is now in private beta.
You can host the agent harness, sandboxes, and session history, in your own cloud or on-premises, and choose where requests to Claude are sent.
while i'm quite bullish on formal methods, i think it's worth tempering expectations and doing your own research on it (disclaimer: i am not an expert in it). it cannot guarantee your code is bug free, only that it matches the spec under certain assumptions, and the specs come from what people want, not math. as long as we build software for humans, nothing can prove that your spec is right, only you can judge.
i created the /statechart skill in pstack primarily because it helps make the state machines implicit in your code more obvious and legible to you, so you can shrink the review surface and review the work at a higher level: does it actually match your intent and goal? i used this skill a ton while building my game tibo.dog, below you can see the statechart for story mode where i was able to find many bugs with it.
in that sense, i think model checking (eg TLA+ with TLC) is quite useful for understanding and checking properties of your system e2e, and you don't have to write tons of new verification code for it. the spec isn't your actual code so there's always a risk of drift, but so far i've had good experiences finding actual bugs with it. i tend to pair it with empirical verification (running the code) also to confirm it's real
other types of formal verification like proving theorems (eg Lean, Dafny), bounded model checking (eg CBMC, Kani) etc have their own tradeoffs. proofs cover every possible input, but only for the properties specified, and it takes a lot more code/work. bounded model checking can run on your actual code, which avoids drift, but it only checks up to a certain number of steps, so it's better at finding bugs than proving there aren't any
so i think in the near-medium term you'll still need to layer your codebase: constraints and guardrails (types, lint rules, api design, refactoring), empirical verification (tests, evals, real usage), and formal verification for the parts that really need it. none of these catch everything on their own, but layered together, they catch a lot more and shrink what's left for you to review
but also maybe in the limit, the bitter lesson will prevail and flawless code will just be printed out perfectly every time with no bugs. even in that scenario, /statechart still seems very helpful in confirming that the agent understood your intent correctly. give it a try if you haven't already!
github.com/cursor/plugins/tr…
SDG retweeted
I sometimes wonder how grilling has changed my brain
Probably a huge benefit - being able to reach a shared understanding about a topic is hard, and practice is good
SDG retweeted
Everything's changed. Here's what I would do if I were starting from scratch getting into software engineering.
How I'd Get Into Software in 2026
If I were starting from scratch in software today, here are the two skills I'd work on right now, and the durable skill that stays valuable no matter how good agents get.
maybe a hot take but i now consider adversarial reviews mostly a waste of tokens. far better to use those tokens on empirical combined with formal verification. i have updated pstack to use the interrogate skill less, and eventually i think i may remove it altogether
i have found very little value with code review in the abstract, agents tend to just get lost in the nitpicks and yagnis
SDG retweeted
Replying to @mattpocockuk
@mattpocockuk deserves some sort of award for all the skills he is sharing with the world. If he isn't already he should totally be a @github star or something.
SDG retweeted
Super excited to be interviewing @poteto, live, in ~48 hours on YouTube.
We'll be nerding out about skills, high-velocity software factories, and learning SOTA techniques for shipping with agents.
This Friday - 9AM PT. Don't miss it!
youtube.com/live/MN9dGgmLyso
SDG retweeted
Still can’t believe some people consume 100k+ in inference in a month and produce absolutely nothing of value with it
SDG retweeted
Anthropic has no small models that are worth using right now.
OpenAI has no large models that are worth using right now.
Google has no models that are worth using right now.





















