#software-engineering

A short post on a simple framework for AI-assisted coding, credited to an engineer on the author's team — brain, then AI, then brain — so engineers delegate implementation without letting their judgment atrophy.

The first "brain" step is understanding the problem well enough to judge the agent's output, since without it AI can steer toward the wrong problem entirely. The last step is making the work reviewable before it reaches anyone else: read the diff, question whether the complexity is earned, and write a real PR description. The rule of thumb is that if you can't explain what changed and why, it isn't ready for review.

A Substack essay exploring how CRAN's reverse dependency checks — which block a package update if it breaks any downstream package — embody a "monorepo mindset" that makes breaking-change authors responsible for their entire dependency graph.

Contrasts CRAN's culture of author-owned migrations with PyPI/npm's publish-at-will model. The author argues CRAN's approach, while slower for individual releases, produces better outcomes for the ecosystem — a point reinforced by their experience at Databricks, where centralizing breaking changes (rather than federating them to consumers) led to faster, more complete migrations with fewer regressions. Particularly pointed for Python ecosystems where library churn and silent breakage are routine.