# Design and write code more efficiently by understanding the system flows

### See runtime usages

Digma overlays observability over code, so developers are able to see the application flows triggering any code location, query, http call, or any other asset. This provides an automatic view of any runtime dependencies.

<figure><img src="https://1440058360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErbSh4MmQO1ycjStau0a%2Fuploads%2FHiJIqEX3z27esVO8Gq6P%2Fimage.png?alt=media&#x26;token=5e341861-a5be-47a1-b0ef-21d11b14be86" alt=""><figcaption></figcaption></figure>

### Traces tied to the code

Each flow include a sample trace for that specific flow, which in turn is fully connected back to the code, so developers can transition from code to trace and vice versa while staying inside the IDE.

<figure><img src="https://1440058360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErbSh4MmQO1ycjStau0a%2Fuploads%2FiqSpSSw4QWG4496yf0s9%2Fflow2.gif?alt=media&#x26;token=b15606fb-9858-4f14-8216-6623583cbc3e" alt=""><figcaption></figcaption></figure>

Note: Areas of the code that are especially risky to change will have the [Code Nexus](https://docs.digma.ai/digma-developer-guide/digma-features/analytics/code-nexus) insight.

### Browse all assets used by a specific endpoint

You can navigate the [assets](https://docs.digma.ai/digma-developer-guide/digma-core-concepts/assets) tree or take an overview of an entire endpoint request to list all of the different unique assets that take part in its execution flow. Assets could be sorted by recency, performance impact, and other criteria. For each of the assets, you can navigate to the related code, see other flows it affects

<figure><img src="https://1440058360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErbSh4MmQO1ycjStau0a%2Fuploads%2FN2KwdSMQX2ltMmUaK319%2Fimage.png?alt=media&#x26;token=ed60f582-d15e-4bd9-a3e7-9d4cdb01d416" alt=""><figcaption></figcaption></figure>

### Find dead code

Any code that is not triggered will have the `Never reached` code lens attached to it. This is a good way to detect dead code that might be a candidate for removal.

<figure><img src="https://1440058360-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FErbSh4MmQO1ycjStau0a%2Fuploads%2FM32jZUDOuWc0xQjAftMM%2Fimage.png?alt=media&#x26;token=1ffc3dcd-83b1-45ca-b175-9320d3811c77" alt=""><figcaption></figcaption></figure>