It's interesting to see folks starting to argue that humans should NOT be in the loop for AI workflows. Even whole companies are built around the idea.

From a software creation and library author perspective, does that mean we should start building SDKs for AIs to consume rather than other developers? In that case, verbosity, parameter explosion, and simple, composable methods make more sense than rationalizing what a person might expect to be obvious.

I expect to see Library authors creating versions of their libraries specifically written to be groked by LLMs without the need for human oversight or that "human in the loop" portion.

That's weird and disturbing, but I can see it happening.

@khalidabuhakmeh sounds like even more libraries where the source code is the only documentation…
What is llms.txt? Why it’s important and how to create it for your docs – GitBook Blog

Discover what llms.txt is, why you should create it, and see llms.txt examples right in our complete guide | Steve Ashby | 22 Aug, 2025

@peterritchie I'm aware of llms.txt :)