Update readme and write down what I learned

Author: p2635

README.md

@@ -19,7 +19,7 @@ Note: When I started this challenge, I was a python n00b so this made my brain w
 - [x] Day 6: Tuning Trouble 🤖
 - [x] Day 7: No Space Left On Device 💾
 - [x] Day 8: Treetop Tree House 🌲
-- [ ] Day 9: Rope Bridge 🪢
+- [x] Day 9: Rope Bridge 🪢
 - [ ] Day 10: Cathode-Ray Tube
 - [ ] Day 11: Monkey in the Middle
 - [ ] Day 12: Hill Climbing Algorithm

day9/ScratchNotes.md

@@ -20,4 +20,14 @@ up left (wide)
 down R (low)
 down R (wide)
 down L (low)
-down R (wide)
+down R (wide)
+
+# What I learned
+
+* When debugging, print stuff out and see exactly where something failed. Compare the variable values.
+* Check the logic in your functions, are they missing any scenarios?
+* Don't be afraid to go and look for help, it's not a sign of weakness, you are stuck.
+* If you are overwhelmed, really go take a break, you've been staring at the screen so long.
+* Breaking it down and visualizing it helped a lot, rubber ducking your ideas.
+* Making your code more generic (i.e. creating reusable functions) saves you time down the line.
+* You can use breakpoints in VS code and watch certain vars, it helps you check what is going on.