SOFTWARE  ARCHITECT
— pinned —
WRITE

The LLM Smell Problem

Someone said my blog has LLM smell. They were right about the writing. They were wrong about where the knowledge came from.

Mar 28, 2026
Read this post →
 The Second Brain That Publishes Itself
scroll
Numbers
→
0
architectural principles in the Constraint-Driven framework
→
0
open-source projects in the NanoClaw ecosystem
0
performance bottlenecks catalogued and targeted
→
0
.NET projects unified into a single monorepo
WRITE Mar 28, 2026
ai-agentscareerwritingknowledge-management
7 of 7
The Breed

The AI era didn't create new knowledge. It created an expression layer for people who already had it. This is for that breed.
WRITE Mar 28, 2026
knowledge-managementmetricsworkflow-automation
6 of 7
Three Months of Capture

What the vault actually looks like after three months of PARA and three weeks of automated routing. Real numbers from a real system.
BUILD Mar 28, 2026 5 of 7
The Output Layer

Where the vault speaks back. The pipeline from captured knowledge to published content — and why the blank page problem is gone.

active
BUILD Mar 28, 2026 4 of 7
Lyra — The AI Pipe

What the AI in this system actually does — and what it doesn't. Obsidian holds the knowledge. Lyra moves it.

active
DECISION Mar 28, 2026 3 of 7
Context: Sixteen years of professional knowledge with no expression layer. Five tools tried — EverNote, OneNote, Notion, Twos, and two years of unstructured Obsidian experiments — none solved the fundamental problem. The knowledge accumulated. The words never came out right.
Why PARA. Why Obsidian.
→ PARA applied to Obsidian on January 6, 2026, for structure. NanoClaw connected on March 9, 2026, for access. Plain Markdown files as the substrate — readable by AI agents without any API, authentication, or rate limits.

Consequence: Capture became zero-friction via WhatsApp. The knowledge base became programmatically readable. The expression problem dissolved: instead of sitting down to write, I describe what happened. The vault routes it. The structure holds it. The AI layer expresses it.
BUILD Mar 28, 2026 2 of 7
The Capture Layer

How a WhatsApp message at 11pm becomes a structured knowledge base entry by morning — the raw input layer of the second brain.

active
WRITE Mar 26, 2026
ai-workflowimage-generationgeminicloudflare-r2
5 of 5
An AI Pipeline That Reads Your Post Before It Draws the Picture

How to generate blog cover images that actually reflect your content — using a three-tool pipeline built around visual metaphor, not stock photo logic.
WRITE Mar 26, 2026
ai-toolsdesignclaude-skillsux
3 of 5
Five World-Class Designers in Your IDE

Design Council is a Claude Skill that activates five distinct philosophical lenses on demand — Ive, Rams, Hadid, Ingels, Norman — each asking a different question about the same design.
WRITE Mar 26, 2026
ai-workflowdev-toolsclaude-codebmad
4 of 5
The Dev Workflow That Follows You Everywhere

How NanoClaw, the BMAD Method, and Claude Code Remote Control combine into a single workflow that goes from late-night insight to shipped code — regardless of what device you are on.
BUILD Mar 25, 2026 2 of 5
Claude Skills

Open-source Claude Skills for design, architecture, and developer workflows.

active
WRITE Mar 22, 2026
architecture
6 of 6
Constraint-Driven Architecture: Five Principles for Building in the Real World

Architecture advice assumes you start fresh. You never do. Here are five principles for designing software when constraints are the starting point, not an afterthought.
WRITE Mar 21, 2026
personalarchitecture
6 of 7
The Architecture Happens in the Shower

The best architectural decisions happen away from the keyboard. The discipline is having a system that captures them before they fade.
WRITE Mar 19, 2026
architecturemigration
5 of 6
What a Twenty-Year-Old Codebase Could Become

The architectural north star worth holding when a monolith has outlived its original design.
WRITE Mar 16, 2026
aiengineering
1 of 5
Giving AI Context in Large Brownfield Codebases

AI generates plausible but wrong code in large legacy codebases — not randomly wrong, but wrong in ways that quietly erode conventions. Here's how to prevent it.
WRITE Mar 12, 2026
architecture
4 of 6
When Git Submodules Make Sense in a Monorepo

The textbook answer is always a full monorepo merge. But in large codebases with independent release cadences, the right answer is often a stepping stone — and submodules can be that stepping stone.
Explore the full archive →

Software Architect. The work speaks.