Trying to do so is already a good start! It is like writing unit-tests for a logical problem. You list positive cases, negative cases, you also test other classes this change could touch, etc.
With time, one becomes better in that, and starts to "anticipate" problems even before thinking consciously.
I keep asking what is important and why is it important. It's very high level but it's fairly objective and client driven at times (the why we're doing x project) and it keeps me out of the weeds on details sometimes.
It's hard to find the balance and I think it'a a big challenge for what we do.
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.
Trying to do so is already a good start! It is like writing unit-tests for a logical problem. You list positive cases, negative cases, you also test other classes this change could touch, etc.
With time, one becomes better in that, and starts to "anticipate" problems even before thinking consciously.
I keep asking what is important and why is it important. It's very high level but it's fairly objective and client driven at times (the why we're doing x project) and it keeps me out of the weeds on details sometimes.
It's hard to find the balance and I think it'a a big challenge for what we do.