Update summary of strategies

lectures/debugging-strategies/slides.qmd

@@ -29,23 +29,25 @@ digraph {
 }
 ```
 
-## General strategies
+## Strategies covered in this lecture
 
- - Search online for this or similar issues
- - Add output verbosity, especially around where the error occured
+ - Understand compiler usage and messages
+ - Include debug output/logging mechanisms
  - Narrow down the code where the error occured (divide and conquer)
  - Use a debugger
- - Did it work before? What changed since?
- - If changes are committed in a repo,
-   find the last valid commit (`git bisect`)
 
 
-# Compiler errors {.leftalign}
+## Other strategies
 
- - Try to locate and isolate the code section
+ - Consider the last working state and focus on what changed since
+ - If changes are committed in a repo,
+   find the last valid commit (`git bisect`)
+ - Search online for this or similar issues
+ - Ask colleagues working with the same code
  - Call for vendor support
 
 
+
 # Compile-time errors {.leftalign}
 
  - Make the compiler say what you need to know