In other words it can be hard to see the wood for the trees.
They work as follows.
For example a “DataRequest” trail might include the following markers:
There is no separate metadata/documents to be maintained which makes it more likely that trails will be kept up to date. When a developer is working with source code outside of a Code Trails enabled IDE they can still grep the source code for [TAG to find markers manually.
When you first open the Trails view you will see the following warning. Clicking the button will prompt a workspace rebuild to enable detection of TRAIL task tags.
Code Trails is closer to the Reverse LP end of the spectrum but it is designed to allow the user to expose the important design details rather than focusing on the details of each and every method signature.