Leebranch921:
So if I break out of a while loop and there is a another while loop after it will the program be in the next while loop?
If you dont use while loops, what do you use?
The break keyword only breaks out of the inner loop. If you need to break out further, there is goto, which is generally frowned upon because it makes the code hard to follow (like some breadboard pictures I've seen with wires going everywhere), and return which exits the current function.
Generally once a project is more than a few lines, what I do is break things into functions that take some parameters and maybe produce one or more results. A function is a set of canned moves that allows you to break the task into smaller items.
Unfortunately, I tend to think internet forums like this aren't that good for teaching the basic concepts. Once you have the concepts, forums are good at things of syntax issues, etc. Is there a community college nearby that offers an intro to programming class? Maybe a hackerspace? Or a local techy teenager, that hasn't taken to sneering at his/her elders?
I would try to step back, and try to block out what you want to do at a high level (not worrying about language). Initially, you want the project to not have all of the bells and whistles that you eventually will want, but you want a reduced project to get you started. You will eventually add these later.
Now, that you have a high level idea, pick one part of the whole project to work on. Now, in this smaller piece, you want to iterate with successive refinement until you have that one piece done. Then save it, and carefully document the wiring setup (take one or more pictures of the breadboard, and write out a schematic so that you can replicate this later. One thing that I just ordered was several prototype shields with mini-breadboards, so that I could remove one shield and replace it with another. Then go on to the next thing. If you try to create the whole thing at once, it is a recipe for failure.
In addition to saving pictures and schematics, be sure to save your code. Backup early, backup often, particularly off of your primary computer.