It's also a reminder - we're not just here for the surface concept of X, we're here for the deeper philosophical reasons of Y and Z. The goal isn't to check off a "disability accessible" checkbox, it isn't even to "think how disabled people might use this" - it's to be actually accessible to all the actual people with actual disabilities.
Trust me, there are a a LOT of people who need this reminder.
I'd expect the difference in prompts produces significantly different LLM outputs, too - tell an LLM to check boxes and it won't show much initiative, but give it a philosophy and it will often suggest ideas you missed.
Yes, this exactly! Thank you for picking up what I was laying down. I gave them these names as a reminder to myself, the person who is using these tools, who I'm doing this particular task for, why I should remember to look at what I do through particular lenses, and how to get the best output from my tools of choice.
They're my tools in my toolbox for my code. For most of the projects I've used them in, I've been the sole developer and the issues other folks have raised about naming schemes don't apply. I've shared them with colleagues, but if they use them they can call them whatever they'd like -- I'm not trying to say my way of doing things is better for everyone, but it is better for me. And maybe could be for someone else too.
(Sorry for both a three item list and a "not X, is Y" phrasing in my reply. Oh jeez -- and an em dash too. I'm working on moving my writing style away from what LLMs are throwing out there right now, but it's slow going.)
Uh, yes it is? It's just whimsy with an explanation. Long live descriptive, preferably short, names.