A New Home
Moving to an Astro based new home for my personal blog. And a new location.
Archive
All posts, including hidden.
A Tale of Two Harnesses
Adding tool calls to Parley on a flight, watching Claude make a mess, then drawing the architecture boundary for Claude and watching it execute flawlessly within it. The eureka: Claude Code is the execution harness, Parley is the interface for human to inspect and influence — both running on the same shared filesystem state.
WhatsApp GDPR Fine
A close read of the EDPB's €225M WhatsApp fine. The fine is a catch-22 for technical companies, that you need to write your privacy notice concise and easy to understand enough for laymen, yet need to be comprehensive enough to cover all basis. An extremely bad example of regulatory overreach, lacking resemblance of proportionality
Loom workflow system
A parley sketching "Loom": after parley, issues, and vision, a fourth repo-native tool for recurring agent-driven routines — the morning health check, the weekly oncall report. Together they form a kind of operating system for how a startup actually thinks.
Vision alignment tools
A parley on bridging business and tech vision. Mermaid is great for structure but weak for magnitude — Wardley Maps and Graphviz with weighted nodes do better. The deeper move: stop being the human translator and become the maintainer of a shared YAML schema.
what is "Graphviz (DOT language)"
A side-trip into Graphviz's DOT language: a declarative graph format from AT&T Labs where node width, color, and font size let you encode magnitude — exactly the dimension Mermaid lacks. The recommended pipeline: YAML domain model, Python script, DOT, SVG.
AI Workflow Evolved, One Year Jouney
Reflecting on a year of tinkering and adapting to the ever changing world of AI. After a year and 400+ commits on Parley.nvim, I'm convinced the future is humans setting up the environment, with full automation of the coding inside it. Here's my journey so far.
Conversation: further on the ideal of log.md
A follow-up parley: log.md is the least controllable file in an agentic issue structure because it depends on the model voluntarily writing during execution. Drop it. Let git history and plan.md diffs serve as the log instead.
Conversation: agentic state management
A parley conversation on why agentic coding state — issues, plans, logs — wants to live inside the repo, beside the code. Single-threaded topological execution as the sane default; minimal files per issue beat reinventing Jira on disk.
Personalized Software
When agentic coding lets a vim user write a custom mouse-aware floating picker because Telescope couldn't do that. The implication for SaaS: programmability stops being a nice-to-have, it becomes the moat.