I feel like print statements are great for debugging, they're good at showing the order of things or changes over time.
For git, try git add -p. Lets you review and stage one change at a time. Or just git diff (for unstaged changes) or git diff --cached (for staged changes), then you don't need to run 10 diff commands in sequence.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
print(100, value) .... print(200, value)instead of using the debugger.git diffon each file and observe the changes before committing.I feel like print statements are great for debugging, they're good at showing the order of things or changes over time.
For git, try
git add -p. Lets you review and stage one change at a time. Or justgit diff(for unstaged changes) orgit diff --cached(for staged changes), then you don't need to run 10 diff commands in sequence.