One of the most oft-repeated imperatives in the scriptures is to “ask.” Try it out. Go to scriptures.lds.org and enter “ask” into the search box. I got 345 results. Put that together with “knock” and “seek” and you’ll notice that there is hardly anything that the Lord directs us to do more than to search out, think about, and ask for the answers to our problems.
As I have been troubleshooting my own programming needs, I have found this to be one of the most important things I can do to increase in knowledge. When you come across a programming behavior that baffles you (either it doesn’t work the way you’d expect or you just don’t know how to do it yet), SEEK the answer. Just as with the Lord, we need to go to the source to find the answers. Go to someone reputable, whose advice and instruction you can trust.
Next, PONDER their advice. Think about what they’re saying and put it to action. I often find that I have a quick reply along the lines of, “yes, but that doesn’t help me.” But then, when I stop to really digest the answer, I find that the person who offered advice often is saying something more meaningful than I initially interpreted. Remember D&C 9:7. “Behold, you have not understood; you have supposed that I would give it unto you, when you took no thought save it was to ask me.”
FInally, ASK. Ask for further understanding, for clarification, etc. Make sure to “ask not amiss” (2 Ne. 4). One way of asking amiss is to expect the person you are asking for help to do all the work for you. Another way is to provide too little information. Programmers can be very helpful, but they might not be as kind as the Lord is if you expect them to do everything for you.