Describe what happened
When a program does something unexpected, describe the behavior before making changes. What instruction was running? What should have happened instead? A specific description helps narrow the search and makes it easier to ask someone else for help.
Keep the comparison fair
Try one change and repeat the same scenario. If several instructions change at once, it becomes harder to know which one affected the result. Keep a short note of each attempt so useful discoveries are not lost between tests.
Find a coding starting point ↗