[manuscreationis]

I think you're generally on the right path, just keep trying. Since you're still getting your feet wet, you should pick a language and stick with it for a little while, but don't stick with it as your only language forever. Too many people make the mistake of getting comfortable with one technology, and deeming themselves "done" learning anything else.

Start with Python, or Ruby, or Javascript. Something simple. If you're a fan of Windows, take a look at C# (which you say you've had a semester of already).

Start S M A L L. You say you try to build things that are over your head. Don't do that. Build things that are just about your level, while still providing a challenge. You're not going to come out of the gate with something like Kenneth Reitz' "Requests" framework. You're going to have years of learning and experience ahead of you before you can produce work like that (unless you're a prodigy, which almost none of us are).

Most importantly, do not give up. You are not stupid or incapable of programming if you hit a wall and can't seem to get by it. We all hit these walls, at every level of our craft. The issue is recognizing when you have the ability to climb the wall, to blow a hole through it, walk around it, or just go back the way you came and pick another path.

You could try applying for unpaid (or lightly paid) internships as more of a learning experience. If companies don't think you'll be a drain on resources, I would imagine certain companies would love to have someone who is eager to learn hanging around to take minor tasks and to be mentored for a few hours a week. The key there is finding the right company with that kind of time/support.

Best of luck.