well that was just a test, idk how to get it to where i want it to be. |
Don't worry about that for now, can you answer my other questions?
But I love doing it though, so its hard to quit. |
Don't feel you need to quit, IMO there are a couple of things:
1. Coding: get the basics right, understand how it works,
remember it. Move upwards from there.
2. Design: Have a clear idea of what you want to achieve. Write it down on paper. What is the input? What is the output? Write those two things down. How are you going to store the information? Choose a type that might be suitable -
std::string
,
std::vector<std::string>
,
std::vector<YourOwnClass>
Break the process down into individual steps - start out general then gradually refine things.
Also, you mentioned in the past that you are a visual learner: So draw pictures of how things work. Get this: that's what developers do. It's formalised into a thing called UML. I am not saying you should rush off and learn that - for now just draw a picture that makes sense for you.
I personally find as well as diagrams, I learn things better if I write things down. It's too easy for things to bounce off if it is only being read or listened to. I used to have a Lecturer that would read verbatim the lecture notes displayed on an overhead projector. So I would hear it, see it, and write it down, then check that I had written the formula correctly. After 1 hour and seven or eight pages of notes, it was amazing how much one remembered.
Anyway, can you answer my previous questions? I could write some code for you, but it depends on what those answers are.