Kyle Casterline

CTO & Co-founder Barricade AI | professional entropy reducer

[Kyle Casterline @KyleACasterline]

@daniel_mac8 ling live competition

[Kyle Casterline @KyleACasterline]

something... something... human capital that cannot the offshored

[@jason @Jason]

They updated the most legendary chart on twitter

What stands out?

[Kyle Casterline @KyleACasterline]

@iScienceLuvr Probably not just the doomers. I would like to know what happens then all this AI generated bot sentiment on the web gets folded back into the datasets

[Kyle Casterline @KyleACasterline]

@elonmusk @AnthropicAI "The most entertaining outcome is the most likely"

...has apparently somehow become a recursively self fulfilling statement

[Paras Chopra @paraschopra]

AI bois be like:

[Kyle Casterline @KyleACasterline]

My wife asked me for some cute characters to paint on on mugs

[Google Research @GoogleResearch]

Introducing TurboQuant: Our new compression algorithm that reduces LLM key-value cache memory by at least 6x and delivers up to 8x speedup, all with zero accuracy loss, redefining AI efficiency. Read the blog to learn how it achieves these results: https://t.co/CDSQ8HpZoc

[Ujjwal Chadha @ujjwalscript]

Unpopular Opinion: We aren't building the future 10x faster with AI. We are just generating legacy code 10x faster.

Everyone is currently bragging about developer velocity. "I built this entire backend in a weekend!" "AI wrote 80% of my codebase!"

But here is the reality check we are ignoring: Code is a liability, not an asset.

If an AI tool spits out 1,000 lines of functional boilerplate in five seconds, that is still 1,000 lines that a human being has to read, review, secure, and maintain when the dependencies inevitably break next year.

We are treating code generation like a pure productivity win, but we are optimizing for the wrong metric. The bottleneck in software engineering was never how fast we could type. The bottleneck has always been comprehension, architecture, and maintenance.

If we don't shift our focus from "generation speed" to "architectural sanity," the tech debt of the next five years is going to be an absolute, unmaintainable nightmare.

[Kyle Casterline @KyleACasterline]

@sashimikun_void @bunjavascript Is anyone doing this yet for python?

[Muratcan Koylan @koylanai]

The problem is how memory gets into the context window and what happens when compaction wipes it.

OpenClaw loads MEMORY[.]md plus the last two days of daily logs at session start. Static injection. Everything gets stuffed into the context window upfront. When the window fills up, compaction fires and summarizes your loaded memories away. The agent silently writes durable memories to disk before compaction hits. But after the window resets, the agent can't systematically browse what it flushed. It runs search queries and hopes the right chunks surface. The memory exists on disk. The agent just lost the ability to walk through it.

This is a context delivery problem.

Everything is a file. Mount memory, tools, knowledge, and human input into a single namespace. Give the agent list, read, write, and search operations. Let it pull what's relevant per turn instead of dumping everything at boot.

Cursor validated this in production with their "dynamic context discovery" approach, which stores tool responses, chat history, MCP tools, and terminal sessions as files that the agent reads on demand. When compaction fires in Cursor, the agent still has the full chat history as a file. It reads back what it needs instead of losing it to summarization.

Markdown memory files exist in OpenClaw. SQLite-backed hybrid search exists. memory_search and memory_get tooling exists. What's missing is the abstraction layer that turns static file loading into dynamic file system access.

Here's what that actually means in practice.

All agent context goes under one predictable namespace. Immutable interaction logs at /context/history/ are the source-of-truth timeline, spanning agents and sessions. Episodic memory at /context/memory/episodic/ holds session-bounded summaries. Fact memory at /context/memory/fact/ stores atomic durable entries like preferences, decisions, and constraints that rarely change. User memory at /context/memory/user/ tracks personal attributes. Task-scoped scratchpads at /context/pad/ are temporary working notes that can be promoted to durable memory or discarded. Tool metadata lives at /context/tools/. Session artifacts at /context/sessions/.

This three-tier split (scratchpad, episodic, fact) replaces OpenClaw's current binary between "today's log" and "forever file." MEMORY[.]md conflates atomic facts like "user prefers dark mode" with episodic context like what happened in last week's project. Daily logs conflate scratchpad work with session notes. Separating them gives each tier its own retention policy and promotion path.

The agent gets explicit file operations at runtime. It can discover what context is available before loading anything. It can pull only the exact slice needed. It can grep by keywords, semantics, or both. It can persist new memory with retention rules and promote validated context from temporary to durable storage. Memory stops being a preload and becomes something the agent discovers, fetches, and evolves per turn.

Between the filesystem and the token window, you need an operational layer. Before each reasoning turn, a constructor selects and compresses context from the filesystem into a token-budget-aware input.

It queries recency and relevance metadata, applies summarization, and produces a manifest recording what was selected, what was excluded, and why.

When memory fails silently, there's no way to ask "what did the agent load and what did it skip?" During extended sessions, an updater incrementally streams additional context as reasoning unfolds, replacing outdated pieces based on model feedback instead of stuffing everything upfront.

After each response, an evaluator checks outputs against source context, writes verified information back to the filesystem as structured memory, and flags human review when confidence is low.

Here's why this changes memory behavior.

Compaction stops being destructive. After the window resets, the agent can still list and read context files directly. Search-based retrieval still works, but now it's paired with structured browsing.

Token usage becomes demand-driven. The agent loads only what the active task requires.

Memory gets a real lifecycle. Scratchpad notes graduate to episodic summaries. Episodic summaries harden into durable facts. Each transition is a logged, versioned event with timestamps and lineage. No more binary split between "today's log" and "forever file."

Human review becomes native. Not just "you can open the Markdown file and check." Every mutation is a traceable event. Humans can diff memory evolution, audit what was promoted and why, and inject corrections that the agent discovers alongside its own memories.

Context assembly becomes debuggable. The manifest records what the constructor selected for each turn. When the agent gets something wrong, you can trace whether it had the right context, loaded the wrong slice, or never found the relevant file.

If you're hitting the same problem, here's the upgrade path that doesn't break existing workflows.

Start by returning file references before snippets and emitting manifests that log what was loaded per turn.

Then expose context sources under /context/* paths and enable list and read at runtime so the agent can browse what's available without loading everything.

After that, shift boot-time injection to minimal preload plus on-demand fetch and decompose MEMORY[.]md into fact and episodic stores with separate retrieval.

The final step adds promotion, archival, retention policies, and audit logs so every state transition is versioned and reversible.

Your system needs to let the agent access context on demand instead of blindly inheriting it at startup.

[Andrej Karpathy @karpathy]

A few random notes from claude coding quite a bit last few weeks.

Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December. i.e. I really am mostly programming in English now, a bit sheepishly telling the LLM what code to write... in words. It hurts the ego a bit but the power to operate over software in large "code actions" is just too net useful, especially once you adapt to it, configure it, learn to use it, and wrap your head around what it can and cannot do. This is easily the biggest change to my basic coding workflow in ~2 decades of programming and it happened over the course of a few weeks. I'd expect something similar to be happening to well into double digit percent of engineers out there, while the awareness of it in the general population feels well into low single digit percent.

IDEs/agent swarms/fallability. Both the "no need for IDE anymore" hype and the "agent swarm" hype is imo too much for right now. The models definitely still make mistakes and if you have any code you actually care about I would watch them like a hawk, in a nice large IDE on the side. The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly sloppy, hasty junior dev might do. The most common category is that the models make wrong assumptions on your behalf and just run along with them without checking. They also don't manage their confusion, they don't seek clarifications, they don't surface inconsistencies, they don't present tradeoffs, they don't push back when they should, and they are still a little too sycophantic. Things get better in plan mode, but there is some need for a lightweight inline plan mode. They also really like to overcomplicate code and APIs, they bloat abstractions, they don't clean up dead code after themselves, etc. They will implement an inefficient, bloated, brittle construction over 1000 lines of code and it's up to you to be like "umm couldn't you just do this instead?" and they will be like "of course!" and immediately cut it down to 100 lines. They still sometimes change/remove comments and code they don't like or don't sufficiently understand as side effects, even if it is orthogonal to the task at hand. All of this happens despite a few simple attempts to fix it via instructions in CLAUDE . md. Despite all these issues, it is still a net huge improvement and it's very difficult to imagine going back to manual coding. TLDR everyone has their developing flow, my current is a small few CC sessions on the left in ghostty windows/tabs and an IDE on the right for viewing the code + manual edits.

Tenacity. It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. You realize that stamina is a core bottleneck to work and that with LLMs in hand it has been dramatically increased.

Speedups. It's not clear how to measure the "speedup" of LLM assistance. Certainly I feel net way faster at what I was going to do, but the main effect is that I do a lot more than I was going to do because 1) I can code up all kinds of things that just wouldn't have been worth coding before and 2) I can approach code that I couldn't work on before because of knowledge/skill issue. So certainly it's speedup, but it's possibly a lot more an expansion.

Leverage. LLMs are exceptionally good at looping until they meet specific goals and this is where most of the "feel the AGI" magic is to be found. Don't tell it what to do, give it success criteria and watch it go. Get it to write tests first and then pass them. Put it in the loop with a browser MCP. Write the naive algorithm that is very likely correct first, then ask it to optimize it while preserving correctness. Change your approach from imperative to declarative to get the agents looping longer and gain leverage.

Fun. I didn't anticipate that with agents programming feels *more* fun because a lot of the fill in the blanks drudgery is removed and what remains is the creative part. I also feel less blocked/stuck (which is not fun) and I experience a lot more courage because there's almost always a way to work hand in hand with it to make some positive progress. I have seen the opposite sentiment from other people too; LLM coding will split up engineers based on those who primarily liked coding and those who primarily liked building.

Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually. Generation (writing code) and discrimination (reading code) are different capabilities in the brain. Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it.

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. We're also going to see a lot more AI hype productivity theater (is that even possible?), on the side of actual, real improvements.

Questions. A few of the questions on my mind:
- What happens to the "10X engineer" - the ratio of productivity between the mean and the max engineer? It's quite possible that this grows *a lot*.
- Armed with LLMs, do generalists increasingly outperform specialists? LLMs are a lot better at fill in the blanks (the micro) than grand strategy (the macro).
- What does LLM coding feel like in the future? Is it like playing StarCraft? Playing Factorio? Playing music?
- How much of society is bottlenecked by digital knowledge work?

TLDR Where does this leave us? LLM agent capabilities (Claude & Codex especially) have crossed some kind of threshold of coherence around December 2025 and caused a phase shift in software engineering and closely related. The intelligence part suddenly feels quite a bit ahead of all the rest of it - integrations (tools, knowledge), the necessity for new organizational workflows, processes, diffusion more generally. 2026 is going to be a high energy year as the industry metabolizes the new capability.

[Kyle Casterline @KyleACasterline]

@itsandrewgao parallel sub-agents would be a killer feature. there are so many times I'd like to run lighter weight models to divide and conquer a large task

[Kyle Casterline @KyleACasterline]

@geoffreylitt "Here's something I clanked together"

[Kyle Casterline @KyleACasterline]

@patrickc Imo the world placed far too much value on things that are fictive / social constructs, and not enough value on things that are tangible / grounded

[Kyle Casterline @KyleACasterline]

@asmah2107 such tooling exists, it's an interpreted runtime abstraction for C and it's called CPython

[Kyle Casterline @KyleACasterline]

@arcprize @poetiq_ai 👀

[Kyle Casterline @KyleACasterline]

@AnthropicAI So if I'm understanding this correctly this is basically proposing giving the LLM a REPL with a remote interpreter vs. a bunch of APIs with bulky definitions?

[Kyle Casterline @KyleACasterline]

@lukehollis not sure what I did lol

[Kyle Casterline @KyleACasterline]

@elonmusk forbidden waffle maker