This Entry is an Experiment in creating a definition of what stateful agents are along side Opus 4.6. It's based on a technique I read about in Andrej Karpathy's Post: - Drafted a blog post - Used an LLM to meticulously improve the argument over
Now It Codes, Deploys and Debugs Full Stack Apps. It's the full loop. I'm doing it through a deployment harness I created that I call Loki. You can find it here: https://github.com/inceptionstack/loki-agent I think this is a new pattern. maybe a "
embedrock is a tiny Go proxy I created (ok, my agent did) that translates OpenAI's /v1/embeddings API to Amazon Bedrock, so your existing AI tools work with Titan and Cohere models on bedrock. This was created mainly becuase OpenClaw doesn't have native integration into bedrock
I asked OpenClaw with opus 4.6 to deep dive into its source code and create a detailed architecture document. I like the output for this and I think others could find use for it since I didn't see it described in this detail so far.
As an architect, I love doing diagrams. I think visually. In the past I loved using Miro, mermaid, and a bunch of others, but only recently (past week!) did I try and experiment with drawIO and its XM files format. This whole post is just about a fun late night
What better time is there to try out a new tool or service than when joining a new company? Well, I just recently joined AWS as a Sr. Solutions Architect. Yay! And that's my opportunity to try out a bunch of stuff that I get a chance to
A common thing for me and other developers I see do (I was first alerted to this by Harel Coman) . We work mainly with cursor but a few use claude code. But a common pattern is this: Start chat, then: 1. Enter Prompt 2. Choose model for this prompt 3.
A while ago I wrote about Zero-Touch Algorithm Handoffs: How We Ship ML Algorithms to Prod Without Rewrites (or ML Engineers) and a few weeks ago I got the chance to speak about this topic at the BuildStuff conference. Here's the video: Summary In this video I break
In a previous blog post I wrote about RepoSwarm: Give AI Agents Context Across All Your Repos . A few weeks ago I spoke at BuildStuff conference about this tool including a deep dive into its architecture and what you can do with it. Here's the link to the
My colleague, Harel Coman, wrote about a new AI-driven code review pattern he's been implementing lately called Red Queen Code Review. I like this idea. If I had to put it in a sentence: Every Code Review "issue" must change either your code, or the AI
I don't know when or how I'll use all of these, but I love the scripts listed here. Some that caught my eye: boop (an alias, not a shell script) makes a happy sound if the previous command succeeded and a sad sound otherwise. I do
I've been slowly getting back into public speaking, as I've been "in the trenches" for the past few years (working on my own startup was a huge journey). Anyway here's what I'm planned to speak about in 2025: * Nov 25