A meta-analysis of three different notions of software complexity

kept by lunamystic sep 07

A meta-analysis argues that Zach Tellman's definition of software complexity as the sum of future explanations is the most useful and practical among three discussed.

the hold that could not release itself
Conflating historical facts, contracts, time, and policy in a 'held' flag blocked migrations; the fix separates values from time to avoid stale holds.
also on Rich Hickey, John Ousterhout, #software-architecture, #software-engineering
On cognitive debt
Nate Meyvis argues that cognitive debt in AI-generated codebases is not inherently worse than in traditional codebases, and AI can help mitigate it.
also on John Ousterhout, #software-engineering
AI Code
Function naming, side-effect control, and strict model design (using branded types) are the core practices that keep a codebase self-documenting and maintainable.
also on #software-architecture, #programming-languages, #software-engineering
Go Micro - Agent Harness for Go
Go Micro provides a unified runtime for building agents, services, and workflows with built-in AI capabilities like MCP and A2A gateways.
also on #software-architecture, #programming-languages