https://kau.sh
9 posts
Tech
Subscribe via RSS
Everyone says they’re rebuilding their company in an AI-native way. But what does that mean? Most companies look at what their existing employees do and try to automate it with AI. That’s not it. That’s dabbling. A truly AI-native company rethinks every role and tears down the walls between them. None of us can 8-ball this but here’s my sketch. It’s not exhaustive but hopefully it sparks something: Role changes # Quality Assurance ## The QA team typically finds bugs and dutifully files them in…
Loop engineering convinced me. Not because it’s clever — because done right, it doesn’t bankrupt you. This post captures where I’ve landed: a responsible way to run loops at scale without burning a hole in your pocket. Naysayer → Believer ## I’ve been a vocal naysayer. Not because the approach doesn’t work — it works. The costs never justified it. No surprise — the people singing its praises usually aren’t the ones paying the API bills. But when Peter & Boris tell you something, you look…
Every time I switch or try out a new font, I track it in my my-new-programming-font series. Some of the popular ones: IBM Plex Mono, Recursive, Commit Mono, Berkeley Mono. This time’s a little different. It’s one I’ve “made” myself, and I’m calling it Moxy. Built on strong bones ## Moxy is built on top of Recursive. It’s a stretch to call it a new font — it’s Recursive with a set of opinionated character choices and a few fixes to the original. There’s two things I love about Recursive: it’s…
In this post, I’d like to talk about some power user tips for OpenCode - an open source, model agnostic harness that more people should be using. Hopefully some of the advanced use cases convince you to give OpenCode (and OpenChamber) a shot. intermediate to advanced tips only I am specifically choosing to talk about some advanced tips in this post. If you’ve never used an agent harness or are looking to learn how to use OpenCode, this post can be useful but reader beware. Unleash the leader…
My 2026 Jan AI tool stack. Six months since my last post and the whole list has turned over. Models ### Kimi 2.6 has become my overall workhorse model. By default I start most AI sessions with Kimi 2.6 now. GPT 5.5 remains my coding model of choice. My detailed planning, creating of exec-plans1, code review, simplification, and one-shot feature changes, reliably happen with GPT 5.5 (high). Opus 4.8 for deep thinking, writing and overall hard tasks. It’s been four days since the release, so my…
Linus Torvalds recently said1 AI will be to code what compilers were to assembly — freeing us from writing it by hand. Around the same time, I talked with Jesse Vincent (creator of one of the most popular agent skills out there — superpowers). Something he said stuck with me: Specs are going to be the new code. I realize those two ideas snap together a little too neatly. Agents are compilers2 and specs will become code. Software engineering is moving up another level of abstraction and we’ve…
Most multi-agent coding setups I see today look like task parallelism. You split the work, hand each piece to a different agent, and merge the results at the end. That is useful. I do it too. But I’ve been trying a different approach and really liking it: Put two agents on the same problem and make them argue constructively before I trust the plan. The manual version is simple: I spin up Claude Code with Opus 4.7 and ask it to draft a plan: my-plan-claude.md. Then I spin up Codex with GPT-5.5…
The role of a software engineer is shifting. Not toward writing more code but toward building the environment that makes agents reliable. Think about what you actually do with Claude Code or Codex today: you configure AGENTS.md files, set up MCP servers, write skills and hooks, build feedback loops and tune sub-agents. You’re not writing as much of the software anymore. You’re engineering the harness around the thing that writes the software. Mitchell Hashimoto first coined the term harness e...
I host and edit a podcast1. When recording remotely, we each record our own audio locally (I on my end, my co-host on his). The service we use (Adobe Podcast, Zoom, Skype-RIP) captures everyone together as a master track. But the quality doesn’t match what each person records locally with their own microphone. So we use that master as a reference point and stitch the individual local tracks together. This is what the industry calls a “double-ender”. Add a guest and it becomes a “triple-end...
