This is very reminiscence of the whole LMGTFY (let me google that for you) phase of things. At a job in a while back, when front-level support reached out to senior staff for help the two golden rules were:

  1. Do NOT answer right away. If they wait, there is a good chance the next message is "Oh wait, I figured it out" (e.g. they googled it finally)

  2. Send them a google link w/ the search term showing the first result.

Granted, this was a bit tongue-in-cheek and we did a LOT of trainings to help facilitate actual learning. Still, it was far too easy for senior staff time to get burned up by folks making minimal effort to think for themselves so friction remained.

While the site makes a good point, they miss the most important point, IMO, which is inferable by the example of a good response. The good response is better principally because it contains business-contextual information, which AI can never provide without proper prompting (and if you know to provide that, you prob don't need the AI answer):

  "We need pub/sub for the notifications feature."

I'm not anti-AI, but good answers include historical business context to explain decision making. Sometimes if you're lucky, code comments contain this in relevant sections :).