I have a different take on this. But I’m not trying to change your mind; I respect your opinion as a familiar face around these parts. I just want to offer another perspective for those others reading here.
For tasks completely private to oneself, I agree with you: use the Due date as a “do” date as you suggest, if you want to.
But for shared tasks, I recommend to clients using the Due date field for the actual due date only, not “do” date. If you want, and you’re on any Asana paid plan, use the Start date component of the Due date field as the “do” date; that’s effectively a date range of:
"Do" date - "Due" date
Using just the one Due date field is simpler. Also, relegating the actual Due date to part of the title or to another custom field is less clear. Also, it prevents you from taking advantage of Asana’s built-in support for that field across different surfaces and features.
Many (most) of us do! My approach to My Tasks has Start date (not just Due date) rules to allow tasks to “to pop up when they’re relevant to work on:”
Thanks,
Larry