5 ms·

Let me google that for you: http://developer.apple.com/contact/phone.html http://developer.apple.com/contact/phone.html Literally the first result when search

by icey 15y ago

Let me google that for you: http://developer.apple.com/contact/phone.html http://developer.apple.com/contact/phone.html Literally the first result when searching for "apple developer support phone number".

bittermang 15y ago
And herin lies the problem of this attitude. The original commentator posed a solution, "Call them" but no phone number. The second commentator realized this gap, and asked, "What is the phone number?" One could reasonably expand upon this, it certainty hasn't occurred to me that you could call them and talk to them either. Do you need to be enrolled? Is the number secret? Where is the number. Clearly the first commentator must know this and more, as he is posing it as a solution. At the very least, he must have the number, or know where to get the number. You, the third commentator, come in with the Google Result. Obvious to some, just Google it. Not obvious to others. If it wasn't obvious that you could call them, it would be less obvious that the number is simply publicly available. Further, search results can sometimes be inconclusive, and while this one was the first result and directly on Apple.com, other queries are not so obvious. Again, the first source clearly had the information, and he was directly asked when he did not provide it. That is why communities, question and answer sites, forums, Stack Overflow, and everything else exist. Direct knowledge from people who are verified or profess to having the information that you seek. Some people feel better about direct conversations or direct answers from people vs. casting their fishing hook out in to the giant open Internet and hoping they catch their answer. Some people aren't any good at searching. Sometimes just asking someone who knows can be quicker.
- gnaritas 15y ago
  > Some people aren't any good at searching. You don't need to be good to Google most things. > Sometimes just asking someone who knows can be quicker. Google knows the answer to most simple queries like this. You shouldn't ask a question where the answer is trivially Googled; Google first, then ask when you can't find the answer. The previous poster had the right attitude by saying let me Google that for you, it's such a pervasive problem that sites like http://lmgtfy.com http://lmgtfy.com have to exist to help educate lazy people. Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified.
  - panacea 15y ago
    Ack.. I can't fault your reasoning, and I am definitely in the http://lygtfy.com http://lygtfy.com camp, but I have to pause and reflect on this: "Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified." Doesn't it strike you as somewhat borg-like, subsumed by technology that we should deny people to impulse to ask other people things? I realize that aggregators and comments sections give a sort of false illusion that it's a small number of people in a conversation when the number of actual viewers of a thread (and hence, multiple wasted 'human' cycles spent processing 'noise'), but seriously... we should always defer to the algorithm, the index, the internet rather than asking humans?
    - vacri 15y ago
      There is an immense difference between "can someone give me their phone number" and "I'm having troubles with mdadm picking up this array, can someone help out?" Pandering to trivial requests only encourages trivial requests. Hell, in a forum recently I responded to someone saying "you need version -foo- and you can find it here (link)". He said thanks... then three days later asked where he could find it (link was still valid). The next two comments were asking where they could find the exact thing in the link I'd given and described the parameters of. You also see the same thing in countless forums where commentor -foo- comes along, ignores the comments, and demands someone PM them with the solution. I don't have a problem with repeating stuff that's buried in the comments on page 5 or whatnot, but when it's this level of trivial crap, it is just chaff and shouldn't be encouraged.
      - gte910h 15y ago
        The number is actually not on the google page. Only by asking a human did they get the actual number I have called to get this sort of question answered on. I honestly didn't realize it was a hard to find resource either which is why I left it out, but even googling it, I don't see it anywhere. Also: Be nice to the guys on the other end of it. They've never been less than that to anyone who's been nice to them, nor treated them like idiots. Also, they don't set the policy, they just help devs navigate them. They are also decidedly non-technical, but policy based.
- philwelch 15y ago
  More to the point, a "let me google that for you" comment used to be the kind of dick move that got people downvoted to -8. It's not really worthy of this kind of analysis.
  - icey 15y ago
    Eh, it wasn't meant to be a dick move. I apologize if it was taken that way. It's definitely not worth this much hand-wringing. However, it is kind of frustrating when people don't attempt to put forth the most basic effort in finding information like this. I'm not an Apple developer at all, and it took more time to copy and paste the url into a comment box than it did to find the phone number.
- vacri 15y ago
  For this particular problem, your position is hyperbole. People have been "looking up phone numbers" since the demise of "operator, put me through to -foo-". Looking up a phone number for someone is a lowest-common-denominator task; if you're capable of using a phone, you should be capable of at least a cursory search for a phone number.
gte910h 15y ago
The correct number is 1 (408) 996-1010, ask for developer relations, 8am-5pm pacific time. It is not on that page. Be nice to them.

by icey 15y ago

bittermang 15y ago

And herin lies the problem of this attitude. The original commentator posed a solution, "Call them" but no phone number. The second commentator realized this gap, and asked, "What is the phone number?" One could reasonably expand upon this, it certainty hasn't occurred to me that you could call them and talk to them either. Do you need to be enrolled? Is the number secret? Where is the number. Clearly the first commentator must know this and more, as he is posing it as a solution. At the very least, he must have the number, or know where to get the number. You, the third commentator, come in with the Google Result. Obvious to some, just Google it. Not obvious to others. If it wasn't obvious that you could call them, it would be less obvious that the number is simply publicly available. Further, search results can sometimes be inconclusive, and while this one was the first result and directly on Apple.com, other queries are not so obvious. Again, the first source clearly had the information, and he was directly asked when he did not provide it. That is why communities, question and answer sites, forums, Stack Overflow, and everything else exist. Direct knowledge from people who are verified or profess to having the information that you seek. Some people feel better about direct conversations or direct answers from people vs. casting their fishing hook out in to the giant open Internet and hoping they catch their answer. Some people aren't any good at searching. Sometimes just asking someone who knows can be quicker.

gnaritas 15y ago
> Some people aren't any good at searching. You don't need to be good to Google most things. > Sometimes just asking someone who knows can be quicker. Google knows the answer to most simple queries like this. You shouldn't ask a question where the answer is trivially Googled; Google first, then ask when you can't find the answer. The previous poster had the right attitude by saying let me Google that for you, it's such a pervasive problem that sites like http://lmgtfy.com http://lmgtfy.com have to exist to help educate lazy people. Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified.
- panacea 15y ago
  Ack.. I can't fault your reasoning, and I am definitely in the http://lygtfy.com http://lygtfy.com camp, but I have to pause and reflect on this: "Yes, some people prefer to ask a human rather than Google; those people are lazy and need to be educated, not pacified." Doesn't it strike you as somewhat borg-like, subsumed by technology that we should deny people to impulse to ask other people things? I realize that aggregators and comments sections give a sort of false illusion that it's a small number of people in a conversation when the number of actual viewers of a thread (and hence, multiple wasted 'human' cycles spent processing 'noise'), but seriously... we should always defer to the algorithm, the index, the internet rather than asking humans?
  - vacri 15y ago
    There is an immense difference between "can someone give me their phone number" and "I'm having troubles with mdadm picking up this array, can someone help out?" Pandering to trivial requests only encourages trivial requests. Hell, in a forum recently I responded to someone saying "you need version -foo- and you can find it here (link)". He said thanks... then three days later asked where he could find it (link was still valid). The next two comments were asking where they could find the exact thing in the link I'd given and described the parameters of. You also see the same thing in countless forums where commentor -foo- comes along, ignores the comments, and demands someone PM them with the solution. I don't have a problem with repeating stuff that's buried in the comments on page 5 or whatnot, but when it's this level of trivial crap, it is just chaff and shouldn't be encouraged.
    - gte910h 15y ago
      The number is actually not on the google page. Only by asking a human did they get the actual number I have called to get this sort of question answered on. I honestly didn't realize it was a hard to find resource either which is why I left it out, but even googling it, I don't see it anywhere. Also: Be nice to the guys on the other end of it. They've never been less than that to anyone who's been nice to them, nor treated them like idiots. Also, they don't set the policy, they just help devs navigate them. They are also decidedly non-technical, but policy based.
philwelch 15y ago
More to the point, a "let me google that for you" comment used to be the kind of dick move that got people downvoted to -8. It's not really worthy of this kind of analysis.
- icey 15y ago
  Eh, it wasn't meant to be a dick move. I apologize if it was taken that way. It's definitely not worth this much hand-wringing. However, it is kind of frustrating when people don't attempt to put forth the most basic effort in finding information like this. I'm not an Apple developer at all, and it took more time to copy and paste the url into a comment box than it did to find the phone number.
vacri 15y ago
For this particular problem, your position is hyperbole. People have been "looking up phone numbers" since the demise of "operator, put me through to -foo-". Looking up a phone number for someone is a lowest-common-denominator task; if you're capable of using a phone, you should be capable of at least a cursory search for a phone number.

gte910h 15y ago

The correct number is 1 (408) 996-1010, ask for developer relations, 8am-5pm pacific time. It is not on that page. Be nice to them.