Battery packs: Let's talk about crates, baby

I like the concept for two reasons:

1. I think we're overdue for a general-purpose project templater
2. I believe "Yeoman, not ChatGPT" is the proper way to template out a project (Predictability and resource-efficiency FTW)

That said...

1. It feels sub-optimal that I had to find a link to the tool itself indirected through the README of one of the battery packs, instead of via a clear link on the blog post text. (eg. on the phrase "prototype of the battery pack tool")
2. I've never been big on using other people's scaffolds outside of the Django project generator and it's not clear from the README or the book whether bp has something that would let me pull from ~/src/templates/cli instead of Crates.io. (If not, I'll just stick with the little purpose-specific Python script I wrote and have been meaning to rewrite in Rust.)

I think what makes Django different is the degree of integration. I can find apps on https://djangopackages.org/ and install them, and they implement a single concern, seamlessly integrating into Django Admin, Django ORM, Django ORM Migrations, etc. in a cross-cutting way... partly with the help of types like GenericForeignKey/GenericRelation.

Back when I was using Python as my primary development tool for everything, other frameworks like Pylons and Pyramid were too much like the state of things in Rust and pre-defined scaffolding written by someone else felt sub-optimal because I wanted to evaluate the dependencies that were best for me and the process of discovering them was my way of avoiding what I now fault LLM-driven coding for. (i.e. Without Django's somewhat unique benefits, avoiding scaffolding not written by me won out because it made it easier to acquire a responsible, competent understanding of how my dependencies fitted together and functioned.)