Don't be so hard on yourself, and don't panic. And don't get so wrapped up in self-pity that you ignore the suggestions being given. Programming is an intrinsically detail-oriented activity, so "getting stuck on little things" is a never-ending aspect of the job. Get used to it, and work on your skills for diagnosing, experimenting, and "reading the f***ing manual".
(Yes, it is okay, and in fact highly recommended, to take an experimental approach to the questions and problems that come up when trying to write a program. It's the best way to learn, especially in areas where the documentation seems confusing or incomplete to you. Try things out and see what happens.)
Don't just complain in general terms about how you aren't getting anywhere, because you can't get anywhere that way. Address the specific details that get in your way, and if you can't get past a particular problem, back up and look for another approach for accomplishing the overall task. | [reply] |