What kind of projects are you working on that aren't amenable to the sort of code reuse or abstraction that normally addresses this sort of "boilerplate"?
There are lots of projects like that, especially when doing work for external clients.
Very often they want to own all the code, so you cannot just abstract things in your own engine. It then very easily becomes the pragmatic choice to just use existing libraries and frameworks to implement these things when the client demands it.
Especially since every client wants different things.
At the same time, even though there are libraries available, it’s still work to stitch everything together.
For straightforward stuff, AI takes all that work out of your hands.
Writing boilerplate code is mostly creative copy-pasting.
If I were to do it, I would have most of the reusable code (e.g. of a RBAC system) written and documented once and kept unpublished. Then I would ask an AI tool to alter it, given a set of client-specific properties. It would be easier to review moderate changes to a familiar and proven piece of code. The result could be copied to the client-specific repo.
The author of the initial comment mentioned that customers of contract work prefer code which is 100% theirs, purpose-written, not a dependency, even vendored.
