I think it's how one uses Google. If you've been developing for a while, it makes sense because you know what you're looking for; it's also an easy transition to a new language. On the other hand, a newbie may try to build a website with Google and get frustrated finding all kinds of technologies or the website is slow by throwing in unnecessary stuff. So as a senior developer, you can look at a piece of code and think about tradeoffs. Can it optimise or slow my code?
Second, look through language or framework documentation before consulting Google. That's my take, but in consideration that our intelligence is different, yes, do what gives the best result quickly and Google wins.
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.
I think it's how one uses Google. If you've been developing for a while, it makes sense because you know what you're looking for; it's also an easy transition to a new language. On the other hand, a newbie may try to build a website with Google and get frustrated finding all kinds of technologies or the website is slow by throwing in unnecessary stuff. So as a senior developer, you can look at a piece of code and think about tradeoffs. Can it optimise or slow my code?
Second, look through language or framework documentation before consulting Google. That's my take, but in consideration that our intelligence is different, yes, do what gives the best result quickly and Google wins.