I think that if you make your request too specific, like in the second example, you might seem less approachable, and you'll cutting yourself off from a lot of potential serendipity. The first question could result in "No, but I know someone else you could talk to." The second question requires the person you're messaging to be willing and able to go down a very specific path.
For about thirty years, the Internet was a substantial store of different kinds of value that mostly weren't being monetized. People are slowly figuring out how to capture and extract that value, which is kind of inevitable. They're slowly catching up.
If you've tried to set up your own email server in the last ten years, you know how it's somewhere between tricky and impossible to get an email delivered without it being blocked by the countless layers of reputation checks and spam filters that are set up to keep public email inboxes usable. It seems like we might be heading that way for all public web traffic, especially "writes" (as opposed to "reads")
There are all kinds of technical details in software that almost no programmers understand - stuff like how their operating system's process scheduler works, or how the algorithm used by the network stack confirms that a packet was received. To have control and direction over a product, humans have always just needed to understand the details of how that product works well enough to deal with whatever can't be taken care of automatically. We will see if that still includes "the code" in a few years time. I think it will still include "the spec," in whatever level of detail that that needs to be in.