3 ms·

What does minimalist design have to do with database sequence number generation? Or am I incorrectly assuming that once sentence is intended to flow on from th

• jonathankoren 6y ago
  As a general observation Asana feels intentionally stripped of features for aesthetic reasons, rather than any actual process reasons. A specific casualty of this “Remove all the things!” approach is ticket ids. Perhaps the logic was that since you have a title and a link, that’s all you need. Well, no. Titles can change, but ticket numbers tend to be fixed within teams. Without a short ticket id, it is very difficult to coordinate say git branches/prs to tickets. Whereas if you had a short stable id, you can just name your branch WEB-1234, and know it is associated with ticket WEB-1234. Short stable ids also make it easy to make summary tables, text docs, sms messages, paper notes, and other forms of communication refer to the ticket without constantly copying some excruciatingly long URL, or meaningless hexcode. In my brief experience with Asana, I found it to prioritize form over function. Or as a friend of mine said when comparing to Jira to Asana, “Jira may be a hard configure mess, but at least it knows what problems it’s trying to solve, even if it’s not particularly great at it. Asana doesn’t know what it is.”