That's such a critical mindset to have! I have seen junior engineers super relying on the debugger such that they can fix the data somehow, but they pay less attention to the fundamental causes:
I completely agree! A lot of times, I've seen developers fix a NullPointerException by adding a null check before the function invocation. But the variable should never have been null in that location!
Longer term fixes such as investigating the workflow, figuring out data issues go a long way in building a robust system instead of immediate symptomatic fixes.
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.
That's such a critical mindset to have! I have seen junior engineers super relying on the debugger such that they can fix the data somehow, but they pay less attention to the fundamental causes:
I completely agree! A lot of times, I've seen developers fix a
NullPointerExceptionby adding a null check before the function invocation. But the variable should never have been null in that location!Longer term fixes such as investigating the workflow, figuring out data issues go a long way in building a robust system instead of immediate symptomatic fixes.