Cyclomatic complexity refers to a specific code snippet.
I am talking about inherent characteristics of a particular API and how the patterns it encourages influences debugging.
For example:
>In fact, if any value looks wrong in the DOM of a React app, you can trace where it comes from by looking at the code of components above it in the React tree one by one. No matter the app size, tracing a rendered value is (tree height).
Really, all of this can be pared down to: reduce mutable state. That's what React does, and it's why code written in functional languages like Haskell tend to be much easier to reason about.
Basically, the fewer things you need to know about in a given context, the less likely you are too mess it up.
I am talking about inherent characteristics of a particular API and how the patterns it encourages influences debugging.
For example:
>In fact, if any value looks wrong in the DOM of a React app, you can trace where it comes from by looking at the code of components above it in the React tree one by one. No matter the app size, tracing a rendered value is (tree height).