I was wondering if it is wise or advisable to send over a large amount of source code of one's application for debugging and error solving purposes, I'm working on an iOS app that I hope to release to the App Store and am seeking help on Stack Overflow and I'm tempted to send over a large amount of the code so someone (they requested it) can help me. Would you recommend sending over a significant portion of your app to someone for debugging purposes?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
Licensing and copyright issues notwithstanding, you usually get the best responses for really short code snippets - 5 lines is ideal, 50 lines is doable, 500 lines is asking too much. If you post a short snippet, you demonstrate that you have made an effort narrowing the problem down, that you are willing to do your homework (translate the short proof-of-concept solution into something that works in your product), and that you consider the time of those that are helping you as valuable as your own.
Honestly, I can't think of a problem that would require you to send large quantities of code; such problems should always fall in one of the following categories:
Whenever I have a such scenario when I have to share my code for debugging purposes on Stack Overflow. I do a lot of edits. I remove the package of my organization from Java files. I rename API names. And a lot of stuff. So that I can comply to the policy of my company to not supply code online. But with edits, it will be safe to get help from people.
People can help quickly with short code snippets. I always share my sense and approach that I am using and ask people. And I always get very useful pointers.
Remember that code published on Stack Exchange sites will become CC-wiki licensed, so you may not want to license your code thus by publishing it in that context.
More generally, you want to demonstrate enough code that the problem or bug you're trying to solve is reproducible. But regardless of intellectual property considerations, giving the other party more code than is necessary makes it harder for them to determine where the problem lies-remember that you're having trouble finding the bug, and you know your code better than they do. The "minimal buggy project" helps your reader see what you're trying to do, and indeed you may even gain a better understanding of the problem by identifying the relevant extracts of code.