By reducing the scope I by no means intended, just solve the symptom! **
A good developer always finds the right spot where to make changes, and often is **further up in the chain. Most of the changes should be made to prevent the bug from happening by ** investigating the root cause.**
By reducing the scope I meant to try to investigate on the smallest possible piece of your infrastructure.
I see too often full-stack dev s- with 2 or 3 screens - with everything open ( DB - Dev Console - multiple IDEs with Frontend code, backend code ) reading console.logs everywhere. when they could at least try to isolate the problem.
Thank you very much for pointing this out.
( I guess I will write a separate post for that. Because it pisses me off when in Code Reviews I find silly quick solutions to bugs that would have been better to be handled somewhere else.
Bug fixing shortsightedness (myopia) is also a big problem!
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 is absolutely a very good point!
By reducing the scope I by no means intended, just solve the symptom! **
A good developer always finds the right spot where to make changes, and often is **further up in the chain. Most of the changes should be made to prevent the bug from happening by ** investigating the root cause.**
By reducing the scope I meant to try to investigate on the smallest possible piece of your infrastructure.
I see too often full-stack dev s- with 2 or 3 screens - with everything open ( DB - Dev Console - multiple IDEs with Frontend code, backend code ) reading console.logs everywhere. when they could at least try to isolate the problem.
Thank you very much for pointing this out.
( I guess I will write a separate post for that. Because it pisses me off when in Code Reviews I find silly quick solutions to bugs that would have been better to be handled somewhere else.