Living document

Recommended reading on agentic engineering

A living log of articles, talks and papers on agentic engineering — each with a short note on why it is worth your time. Newest first, updated whenever I read something worth passing on.

12 readings · updated

article

Using the package registries as common ground between OS maintainer and OS user to require payment and transfer them to the OS maintainer. Could work

seldo.com

Nobody pays for open source. We can force them to. | Seldo.com

Thirty years of voluntary funding schemes haven't paid open source maintainers because asking doesn't scale. The real money already flows — to JFrog, Docker, Sonatype — at the registry layer. The fix: registries charge companies for supply (they already do), then route a slice automatically to the maintainers who make that supply worth having.

article

While more constraints usually means better results (correctness, code quality), the article argues about adjusting the constaints to your actual throughput. E.g. if Back-pressure is too high by agents creating too many human-review-needed tasks, create more constraints to reduce that effort. If too less back pressure, reduce the required quality gates of the agentic setup

X (formerly Twitter)

Addy Osmani (@addyosmani) on X

Agentic Code Quality