Thanks for giving me this second chance at your attention. I'll give it two tries, one non-glamorous and one more dreamy (to me).
1. So first a concrete example. As part of a digital musicology project around the time of the pandemic, I built a GitHub Actions, `free-disk-space`, that organically got lots of usage and 700+ stars after I put it on the Marketplace. The action dealt with super sneaky low-level undocumented or poorly documented cloud image file system directory contents, to try to clear what the user would not need to allow for more space (in my original use-case, musical manuscript post-processing). Those kinds of sneaky are really hard to keep in mind, and so when the issues starting collecting more and more requests, I got overwhelmed, especially remembering which requests might go against something I'd previously learned the hard way (but never really documented). Were decisions made here arbitrary or [and please don't flag() this message because of it] "load-bearing"? I had to step away because I couldn't answer those questions tractably anymore with the puny codebase I had put together as a human and the average documentation. With this framework: Going back, processing, issues and commit messages and logs and code comments, and putting together back-filled ADRs, has helped me now evaluate new incoming requests against a set of epistemic records. This has made it much easier, and I've been able to make more headway in the last month than in the last year and a half. (See: https://github.com/jlumbroso/free-disk-space/issues/55)
2. Now a more abstract pitch. What I would tell a non-programming friend: Hey, I think you should try building with Claude Code and my framework; you could probably build and deploy amazing software, and the very unique use-cases you'd want to explore would probably make for compelling software.
What I would tell a programming friend: Hey, the way I/we learned how to program is over, and I don't think that's a bad thing, because I've been more thoughtful about a login dialog, about accessibility in auth design, about architecture of complexity, than I've ever been when I had to write things by hand. This is like vibe coding, but with the scaffolding needed to go the distance, and the deep-linking necessary for the records to support rather than choke your codebase. I get to be both a project manager who has the Big Vision, but also with the authority and ability to control and tweak the design choices with a lot of detail (unlike what a human project manager gets from human developers), allowing, with practice, a faithfulness of vision that reminds me of the early days of freeware and shareware, when the bar for software building was suddenly lowered and you got all these really cool, really thoughtful digital experiences on floppy disks, CDs, and eventually online...
How's that? :-)
Thanks so much for your interest, and this second opportunity.
() I literally did not see you had posted a submission about AI-isms including "load-bearing" but what a coincidence!
Please.