cat ~/ai4se/README.md
## Methodology • Process • Tools • Harmony • Measurement
Notes on how AI4SE / Agentic Engineering reshapes methodology, process, tools, human–agent collaboration, and productivity measurement.
man -k ai4se
Methodology — SDD, Agentic Engineering, AI4SE system
Process — human–agent workflows, review pipelines, loop design
Tools — MCP, Harness Engineering, browser automation
Harmony — HITL/HOTL/HOOL, Planner/Generator/Evaluator
Measurement — DORA, SPACE, DevEx, agent effectiveness
grep -r "featured" ~/notes/
In multi-repo or submodule SDD, teams often argue whether specs belong inside one submodule or beside them all. A better test is ownership: shared boundary behavior belongs in a planning layer; per-repo implementation stays local. OpenSpec Stores make that topology concrete.
Two closed-door Thoughtworks retreats with Martin Fowler, four months apart, form one argument: engineering migrated, verification became the scarce discipline, and human judgment is now the asset organizations are most likely to optimize away.
A merged compilation of the two Thoughtworks Future of Software Engineering retreat reports (Utah, February 2026 and Engelberg, June 2026), reproduced verbatim from the source PDFs with minimal cleanup.
The Cordis preprint from DeepSeek-affiliated authors is long, but its core fits two dimensions of spatiotemporal composability: revertible side effects and reactive dependencies. This piece critiques length and jargon, then explains the mechanisms, confluence, and validation limits in engineer language.
A first-principles abstraction of AI Harness as function composition: freeze the foundation map M(x), orchestrate the outer chain H. Single-turn is strict multi-layer composition; multi-turn fuses composition with a state machine. Optimize H, not weights by default.
After AI enters software engineering, efficiency comparisons often become apples-to-oranges. This article proposes three anchors—comparability (fixed backlog / team / window), separability (freeze the complexity baseline), and honesty (expectation, not fake measured ROI)—plus reading rules for throughput, cycle time (speed framing), and paired aggregation, with common anti-patterns.
dpkg -l | grep ^i