Look it up! Know how to navigate the documentation for the language/API/system you are studying or using. This is essential. You will not always have someone to answer your questions. You may have to find your own answers through a process of research, reading, and experimentation.

Try it! Have a question about how something will work? Throw together some test code and try it. Computer Science involves experimentation. You will learn a lot more by getting your answers this way than you will by asking someone.

Ask! This doesn't mean you shouldn't ask questions. Many times a well thought-out question can save you lots of time. However, you should have tried some research, reading of documentation, and experimentation before you ask. You will be more likely to ask the right questions, you will be more likely to understand and benefit from the answers and suggestions, and you will get a warmer response from whomever you are asking if it is apparent that you have already put some effort into discovering the solution for yourself.

It is my policy (for the most part) not to answer programming questions by email. It is just too easy for you to send me that email at the first stumbling block. Usually people end up figuring out their own solution before I can even answer their email! I will only discuss programming problems that are brought to my office hours (remote folks, please call me on the telephone). I find this encourages people to discover solutions using their own skills.

Being able to solve problems is what it is all about!