Shawn Simister

Shawn Simister

@narphorium.com

Building AI powered tools to augment human creativity and problem solving in San Francisco. atelier.dev Previously @GitHub Copilot, @Google, 🇨🇦

1.5K followers698 following456 posts

View full thread

Jev doesn't generate text, so I used Claude Haiku to turn the question into a logic query first. After that, this query took 100 Jev calls in 8.5 seconds, for roughly a quarter of a cent.

To match a goal against a fact or a rule, the interpreter asks Jev questions like: Could "Abe is the father of Y" and "Abe is Homer's father" state the same fact? Jev answers with a probability. The rest is ordinary proof search, written in code.

Shawn Simister reposted

"Software engineering has changed radically. It is now mainly about reading code. But reading code does not scale. We need to delegate to AI." I am glad you now recognize code reading as a problem. However, the broader problem statement is not quite correct and neither is the conclusion.

Shawn Simister reposted

Been tinkering with annotation "fusion": annotate a paper with ink; take a photo; markup is segmented, turned into structured data, and re-super-imposed on the clean original PDF.

Shawn Simister reposted

Replying to @observablehq.com

We reimagined how computational notebooks could work with agents as the primary interface. Our new agent-first notebooks, called chats, are radically different from our human-first notebooks and yet seamlessly interoperate with them.

Shawn Simister reposted

With Codex/Claude the bottleneck in software development is now expressing your intent. Writing the code is no longer the rate limiting step. This completely upends software development. Take issue trackers. The key problem they were solving was allocation of scarce coding resources to features.

Shawn Simister reposted

This week's #PaperILike is "People construct simplified mental representations to plan" (Ho et al., Nature 2022). People generate ("construe") simplified task representations on-the-fly. (Robots should too!) Also: awesome first paragraph. PDF: arxiv.org/abs/2105.06948

arxiv.orgPeople construct simplified mental representations to planOne of the most striking features of human cognition is the capacity to plan. Two aspects of human planning stand out: its efficiency and flexibility. Efficiency is especially impressive because plans...

"the phoenix must be reborn with its empty spaces intact — intent includes the intent to remain open, and “immortality of intent” is only half-achieved by a system that can’t carry a dodge through the fire." wtf you talking about fable? 😂

Every time an agent explores your code base it builds up its own mental model of how the code works, and then throws that model away when the session ends. Code walkthroughs turn that model it into a step-by-step guide to bring you up to speed on any part of the system.

View full thread

Atelier walkthroughs can use the Chrome MCP in Claude Code to build UI walkthroughs with live screenshots of the app. Grounding the walkthrough in execution exposes gaps in the implementation that you wouldn’t catch with code review.

Anything can be a walkthrough. It's just a views: walkthrough entry in the Markdown front matter and then every ## Subheading becomes its own step

Shawn Simister reposted

Replying to @interjectedfuture.com

What's new isn't the loop. It's that the controller is now expressive enough to handle unstructured goals: natural language specs, ambiguous tasks, open-ended iteration. That's the actual innovation. Not the feedback loop itself.

Every time an agent explores your code base it builds up its own mental model of how the code works, and then throws that model away when the session ends. Code walkthroughs turn that model it into a step-by-step guide to bring you up to speed on any part of the system.

I feel like over the years, we've sort of given up documenting our mental models of code and just accepted that everyone who reads the code builds their own model from scratch.

Now, with vibe coding we don't even do that. The agent is often the only one with a mental model of the code, and it throws it away after each session.

Shawn Simister reposted

What are users thinking during their interactions with LLMs? Introducing ThoughtTrace — the first dataset capturing what users think during real-world human-AI conversations. These thoughts improve user behavior prediction and model alignment, opening a new paradigm of user-centric LLM research.

Shawn Simister reposted

Most engineers stopped reading docs ages ago. But now, agents are reading them. What if you had a way to measure freshness on every PR? Is it as easy as implementing three signals, plus a Claude Code layer? Let's find out together!

go.dosu.devHow Fresh Are Your Docs? Score Documentation Freshness in CILearn how to score documentation freshness in CI pipelines to keep your docs accurate and up to date. Automate quality checks and catch outdated content before it reaches users.

I sketched this out a few years ago. The HTML vs Markdown debate is conflating substrate with information density. The real question is what kind of feedback an artifact actually invites. Hi-fi invites parameter critique. Lo-fi invites paradigm critique.

So now AI has made the high-fidelity artifacts cheaper and easier to create but that doesn't change the rest of the equation. If anything, it makes it easier to fall into the trap of confusing high fidelity with high confidence.

Shawn Simister reposted

For the past few years, humans have been doing “prompt engineering” to coax the best performance out of different LLMs. In this work, we explored what happens if we train an AI to do that job instead. Link to our #ICLR2026 paper: arxiv.org/abs/2512.04388 Thread:

Sakana AI@sakanaai.bsky.social

Introducing our new work: “Learning to Orchestrate Agents in Natural Language with the Conductor” accepted at #ICLR2026 arxiv.org/abs/2512.04388 What if we trained an AI not to solve problems directly, but to act as a manager that delegates tasks to a diverse team of other AIs? Thread: