Building a system for AI-assisted engineering
How a .ai/ directory and project constitution turned ad-hoc AI coding sessions into a repeatable engineering workflow.
! networking, automation, and the occasional LLM experiment
How a .ai/ directory and project constitution turned ad-hoc AI coding sessions into a repeatable engineering workflow.
AI agents are starting to look like operating systems. The LLM is the CPU, the agent is the OS, and skills and MCPs are the applications — here's why that analogy holds up.
A practical walkthrough of using NotebookLM, Claude Code, Obsidian, and Craft.do with MCP to build a personal knowledge management system that actually keeps up with the pace of tech.
The Pragmatic Engineer interviewed Mitchell Hashimoto about his new way of writing code. The bit that stuck with me: always have an agent running in the background. Don’t wait for it to finish — kick off a task, context-switch to something else, come back when it’s done. Treat agents like background jobs, not pair programmers.
It’s a subtle shift but it changes how you structure your work. You stop thinking sequentially and start thinking in parallel — like managing async workers instead of typing code yourself.
Worth watching: The 5 Levels of AI Coding. A solid framework for thinking about where you actually sit on the AI-assisted development spectrum — from basic autocomplete all the way to fully autonomous agents. Honest about what each level demands from the engineer and where the real productivity gains (and risks) live.
Most of us are somewhere in the middle and kidding ourselves about it. Good gut check.
Watched the Cisco Live 2026 Amsterdam opening keynote. Cisco is going full AI mode — no surprise there, but interesting to see how they’re positioning it across the portfolio. Will be following the rest of Cisco Live remotely to catch the technical sessions and see what’s actually substance vs. slide deck hype.