Some constraints are blockages. Others are the most deliberately engineered part of the system. Your highest leverage long term role isn't throughput engineering. It's dam building.
Been working on an evals and enforcement toolkit for conventions. Designed it to help enforce and measure code quality in repos for agents and devs. Open source, docs and GitHub in video description.
Doing the same thing by hand four times is visibly dumb and cheap to fix. A wrong system is invisibly dumb and expensive to fix, because by the time anyone notices, everyone downstream has organized around it and feels obliged to keep it alive.
"Most thought leadership is signage. Well-designed, prominently placed, often pointing somewhere reasonable, and bearing no relationship whatsoever to the fate of the people who turn where it says to turn."
sebastianscholl.substack.com/p/thought-lead…
