The concept of annotations is a powerful expressive resource for interactive environments, which I believe is underexploited. IMO they are easier to understand for non-coders than data types: annotations allow building some relevant computations without worrying about run-time state changes. Users may simply annotate their data objects with relevant symbols, and expect built-in processes to create automated results with little work and a simple mental model of what's going on.
For example, tags are a common and easy-to-use mechanism. Users tag their data with different words, and this creates different collections, one for each word. Search allows retrieving all the annotated instances in each collection no matter where they are located. Generating this same interaction by code by the user would be a very complex development, but annotations create a language to obtain that effect by leveraging a pre-programmed system that hides all the complexity.
As @Mattia Fregola's example shows, they can also be used for collaborative work. An annotation is accessible from multiple remote points and can be edited with different tools with conceptually simple semantics. I think an annotation style of programming may be used for other use cases such as data transformations and data pipeline creation, as an automation mechanism that retains this kind of simplicity for end users. Also, think of the Decorator design pattern for more cases where this style is used even by expert programmers to simplify some kinds of automated effects.