I think "Slopware" is the stuff that comes out in codegen unbridled by taste.

"Thinkware" is what runs on/around the model. If we loosely consider an LLM a computer, a prompt is somewhat of a program. Thinkware is all that stuff that runs on / wrangles this "new kind of computer".

Mmm "Slopware"

"Thinkware Engineering"

Software gaining more autonomy (AI agents, etc.) may very well make this problem worse. I'd be surprised if we didn't end up with per-task data puddles proliferating before we figure out systemic solutions.

How are you thinking about what this means for AI code generation? What new patterns are you applying to help mitigate the risk of your codebase getting stuck in the mud?

Bazel works best when deps are defined to be fully immutable and consistent for all new builds (or fail clearly). This means CI reflects local, etc. in the common case. rules_rust branch selection is leaking Cargo's looser model a bit.

Sounds like a plan ;). If you ever wander back into Bazel-land, I'm happy to help.

Note that it's better form to use a rev instead of a branch as Bazel won't check the repo on every build and you probably want to be able to control when it pulls a new version. I used a branch here for simplicity of example.

If you just want to replace the crates.io package with a git branch, you should be able to alter the spec. If you want them to coexist, or this gist doesn't work, let me know.

gist.github.com/akesling/7bb...