Standard response. I too thought the same and made no progress, until I saw the problem was how I looked at the problem. We’re used to the above because “Computer says: No!” is the common user experience. We’re schooled that there is a sweet spot to rewarding use, we just have to submit to the designers intent.
For deeper tools a little consideration of the task at hand repays massively. I don’t mean that in the sense that “App A does this, but at App B we do it this way.” Far from it, the joy of a thinking tool is tools with which to think.
Let’s step back. Consider your opening problem. What sort of an article/title where you expecting to find and that might help unpick the disconnect.
If you feel this is push-back I can only say I’m writing this as I break out from a significant re-factoring of aTbRef to answer the issue of how to set attributes using the UI: 2 person-days effort and counting. so, it’s not that you’re being asked to join a different cult (which seems the normative software experience, IME).