Skip to content

Instantly share code, notes, and snippets.

@erica
Last active June 23, 2019 23:21
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save erica/7d129c559ddd9d87bcd4 to your computer and use it in GitHub Desktop.
Save erica/7d129c559ddd9d87bcd4 to your computer and use it in GitHub Desktop.

ASK A SPECIFIC QUESTION

How To Get Answers

Ask your question and then be patient. Tell us what you want to happen, what is actually happening, and include any error messages you find:

  • Provide a scenario. "I am trying to do X, I do so by calling APIs W and Y, but Z happens instead. I see the following error messages:..."
  • Focus on the goal. Ask about what you're trying to achieve (the big story) rather than the specific technical detail that you believe is holding you back.
  • Don't solicit help. Don't say, "Does anyone here know about (for example) Core Foundation". Just ask your question.
  • Do your homework. Search the web before asking in-channel.
  • Be courteous Don't just paste Stack Overflow questions in-channel.
  • Remember the topic Refer questions about third party libraries to their developers.
  • Asking questions: Getting help on IRC, Smart Questions, Getting Answers, What have you tried?
Handy Links

iOS #iphonedev • OSX #macdev • Off-Topic #iphonedev-chat • New to Apple Dev #cocoa-init • watchOS #ioswatchdev • tvOS #appletvdev

FAQ

Q: What are the channel rules?
  1. Google first. Ask second. Search the web thoroughly. Talk out your problem to yourself before asking questions in-channel.
  2. Be resourceful. Figure out how to participate without constant hand-holding. Don't be a help vampire. It's a bannable offense.
  3. Debug your own code. Ask for advice, not specific solutions. If you can't thoughtfully evaluate your own work, you shouldn't be in this channel.
  4. Show respect. This is a volunteer-staffed channel. Each member's time is worth at least as much as your own. Remember to say, "Thanks!"
  5. Don't say it "doesn't work". Explain your problem completely and concisely.
  6. Show your code. If you don't want to or can't show your code, create a minimal project that demonstrates your issue.
  7. Use a paste site. Never paste multiple lines of code directly into the channel. Don't paraphrase. Show your actual code and error messages.
  8. Don't cross-post your question to multiple rooms.
  9. Do not publicly log conversations. Think of #iphonedev as a coffee shop. If you cannot overhear the conversation as it happens, the words should be gone forever. We will ban any logging bots brought into the channel.
Q: How long until I can ask the same question again?

A: 45 minutes.

Q: Can I get help on AlamoFire/SwiftyJSON/AFNetworking/CocoaPods/Carthage/Masonry?

A: Take questions about 3rd party packages to channels that are specific to those implementations. This room is for iOS dev using Apple tools.

Q: Which is best? SwiftyJSON or AlamoFire?

A: NSURLSession

Q: What does EXC_BAD_ACCESS mean?

A: You're addressing already-released memory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment