The closer reads like people might've made the right call refusing the engagement.
It also reads like a refusal of true disengagement. Maybe you can now work on that, given that your profile says you're retired?
__
That said, I use AI the same way. It saves one from a ton of draining interactions, ego management etc.
> The closer reads like people might've made the right call refusing the engagement.
I think there's enough history of my contributions to various open-source projects over the past ~20 years to serve as evidence that I go pretty far out of my way to be accommodating to projects that are open to contributions.
> It also reads like a refusal of true disengagement.
I'm not sure what "refusal of true disengagement" means.
My goal is generally to accomplish something like building a piano recital scoring app, or being able to run an old game on my laptop. There's a few dozen steps needed to achieve that, which incrementally go down the stack until it encounters a library that works well enough that I don't need to debug it. Sometimes this is a very short list -- I've been amazed at how well the Vulkan ecosystem works, ditto the Go stdlib and the major Go ecosystem libraries.
But sometimes it's like falling down a ladder, hitting each rung on the way down, in which case I turn to an LLM to make the ladder go away. A lot of C projects seem to be like this -- it's a conservative choice of language in general, for people who saw the rise of C++/Java/C#/Go/Rust/etc and decided to skip them, so the attitudes and tooling are likewise conservative.
> Maybe you can now work on that, given that your profile says you're retired?
Being retired means that I want to spend more time doing fun things and less time arguing about file descriptor lifetimes on mailing lists.