I just thought I'd put a thread together for those of us who are experienced developers to share tips with those who are new to iOS development.
I'll start the discussion.
Tip #1: Get to know the debugging tools. Figure out what it means to "step over", "step into", and "step out of" an instruction/thread. Also figure out how to do those things. Learn what a "stack trace" is and how to use the Debug Navigator to view the stack trace and to find the line of code that is causing a method to fire. Learn how to make a breakpoint. Especially learn what exception and symbolic breakpoints are and how to create them. Taking just a few minutes to learn how to use the debugger, and getting into the habit of using as much of that knowledge as you can apply when debugging your code, will save you hours of frustration.
Tip #2: Get an account on Stack Overflow. If you have a problem and have spent hours trying to find a solution, you can always ask the Stack Overflow community for a solution.
Tip #3: When posting on forums, write good questions. Use the question box to tell others exactly what the problem is, then use the body of the question to post: the relevant code, what you've tried so far, what solutions you think are irrelevant to your problem & why, and anything else other people should know - like how to reproduce the problem you're having, if it's not obvious.
Tip #4: Don't reinvent the wheel. Look into accomplishing whatever goals you have for your program using existing frameworks and libraries. You'll save time and your program just might be more efficient. Plus, if there's a problem and you have reason to believe that problem is caused by someone else's code, perhaps you can take comfort knowing that you didn't cause the problem.
I'll start the discussion.
Tip #1: Get to know the debugging tools. Figure out what it means to "step over", "step into", and "step out of" an instruction/thread. Also figure out how to do those things. Learn what a "stack trace" is and how to use the Debug Navigator to view the stack trace and to find the line of code that is causing a method to fire. Learn how to make a breakpoint. Especially learn what exception and symbolic breakpoints are and how to create them. Taking just a few minutes to learn how to use the debugger, and getting into the habit of using as much of that knowledge as you can apply when debugging your code, will save you hours of frustration.
Tip #2: Get an account on Stack Overflow. If you have a problem and have spent hours trying to find a solution, you can always ask the Stack Overflow community for a solution.
Tip #3: When posting on forums, write good questions. Use the question box to tell others exactly what the problem is, then use the body of the question to post: the relevant code, what you've tried so far, what solutions you think are irrelevant to your problem & why, and anything else other people should know - like how to reproduce the problem you're having, if it's not obvious.
Tip #4: Don't reinvent the wheel. Look into accomplishing whatever goals you have for your program using existing frameworks and libraries. You'll save time and your program just might be more efficient. Plus, if there's a problem and you have reason to believe that problem is caused by someone else's code, perhaps you can take comfort knowing that you didn't cause the problem.
Last edited: