Remove AV1580 guideline

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: dennisdoomen

_pages/Cheatsheet.md

@@ -95,7 +95,6 @@ NOTE: Requires Markdown Extra. See http://michelf.ca/projects/php-markdown/extra
 * Avoid signatures that take a `bool` flag ({{ site.default_rule_prefix }}1564)
 * Prefer `is` patterns over `as` operations ({{ site.default_rule_prefix }}1570)
 * Don't comment out code ({{ site.default_rule_prefix }}1575)
-* Write code that is easy to debug ({{ site.default_rule_prefix }}1580)
 
 <br/>
 **Framework Guidelines**

_rules/1580.md

@@ -4,10 +4,12 @@ rule_category: maintainability
 title: Write code that is easy to debug
 severity: 2
 ---
-Because debugger breakpoints cannot be set inside expressions, avoid overuse of nested method calls. For example, a line like:
+Because debugger breakpoints cannot be set inside expressions, avoid overuse of nested method calls. For example, in some IDEs, a line like:
 
 	string result = ConvertToXml(ApplyTransforms(ExecuteQuery(GetConfigurationSettings(source))));
 
 requires extra steps to inspect intermediate method return values. On the other hard, were this expression broken into intermediate variables, setting a breakpoint on one of them would be sufficient.
 
-**Note** This does not apply to chaining method calls, which is a common pattern in fluent APIs.
+**Note:** This does not apply to chaining method calls, which is a common pattern in fluent APIs.
+
+**Tip:** [JetBrains Rider](https://www.jetbrains.com/rider/) has a very advanced debugger that allows you to choose into which part of a nested or chained call you want to step. It also displays all intermediate parameter and return values.