Confusion over two types of annotations

Woah — this thread really took off! I haven’t had the chance to read everything yet since I’m on holiday (and Merry Christmas to those who celebrate :christmas_tree:).

Speaking only for myself: I believe it’s healthy to express opinions about software. When feedback is constructive, there’s real value in sharing it.

At the same time, I fully recognize that the development team has spent a lot of time thinking through design decisions, and that features are built the way they are for good reasons. I also understand that it’s practically impossible to create software that fits everyone’s workflows and preferences equally well.

When I ask questions or share thoughts, my intention is genuinely to understand why things work the way they do, and—where it feels appropriate—to suggest alternative perspectives rather than make demands. I don’t necessarily expect acknowledgment (even though, of course, it’s always appreciated). For example, in the case of the “user stories” I posted earlier, the goal was simply to provide a basis for discussion rather than to present anything final or prescriptive.

I do find it a bit unfortunate that the conversation has shifted toward meta-discussion. In the end, we’re all here because of a shared fascination with DEVONthink, and I believe most people are participating with positive intentions. From a user’s perspective, open and respectful discussions can also help newcomers feel welcome and better understand the app, rather than reinforcing an “insiders only” atmosphere that sometimes emerges in technical communities.

Personally, my experience on this forum—and in exchanges with the support team—has been overwhelmingly positive. I’m still learning my way around DEVONthink, and I value these discussions because they help me become a better user, and hopefully help others along the way as well.

7 Likes