Dude, try out some simpler things first. Name your components accordingly to be able to identify what they are from their names. Then learn to work with debug and breakpoints, as ryanb31 has suggested.
It's not my specialty to develop games (I do develop software and web applications professionally) but I've had to create a simple snake game in the beginning of this year, it was in C. I've tried coding first but that made me spend some hours with pen and paper later to fix all the logic. Games are far more complex than usual programs, because their logic involves positioning, collision, and in other cases that aren't yours - gravity, physics and stuff. It's much important to write down your logic with pen and paper before start coding. When your logic works in the paper, then you'll "translate" your notes into code. That works much better.