Oh man, you're in the situation, that I was in about 3 years ago, as a rookie on my own team!

I know it's not a good feeling, when the newer guys have to learn, and they're your backboard, because It was never a good feeling, going into build season knowing so little about programming, for me.
Learning to programming isn't always going to be simple, it's fairly hard, and the best way to learn trial and error. You have to teach them by letting them try it first. Set up a prototype, and give them simple task to accomplish such as getting the robot driving. Obviously you have to give them a background for it first, so you show them, let them look over your shoulder, give them a few pointers, and let them on there own way to try some coding! If you don't let them try, but instead just teach them, they'll think they know it all, and when they're finally need it they will run into as many problems as possible. Brown's Rule : Anything that can go wrong, will go wrong; and trust me I've been through that.
Let them experience all types of sensors, inputs, outputs, and operators. The more they KNOW they can do (with actuall testing) the more of the picture they can put together, and slowly they'll piece the picture together.
Since you only have a basic understanding, this is an awesome opportunity for you to learn alongside them. This way all of you will really be at the same par.
