Quote:
well the question was too tricky to answer
The first step is to solve by hand with a sheet of paper and a pencil. This is how you build an algorithm/procedure that solve the problem.
Failing on first trial is normal. You learn and find the algorithm by "trial and error". "Trial and Error" is an efficient way of learning.
Note that partial answer is an indication that you are close to the answer.
Once you have a method to solve the problem, you have to translate code, this is your algorithm.
We do not do your HomeWork.
HomeWork is not set to test your skills at begging other people to do your work, it is set to make you think and to help your teacher to check your understanding of the courses you have taken and also the problems you have at applying them.
Any failure of you will help your teacher spot your weaknesses and set remedial actions.
Any failure of you will help you to learn what works and what don't, it is called 'trial and error' learning.
So, give it a try, reread your lessons and start working. If you are stuck on a specific problem, show your code and explain this exact problem, we might help.
As programmer,
your job is to create algorithms that solve specific problems and you can't rely on someone else to eternally do it for you, so there is a time where you will have to learn how to. And the sooner, the better.
When you just ask for the solution, it is like trying to learn to drive a car by having someone else training.
Creating an algorithm is basically finding the maths and make necessary adaptation to fit your actual problem.
The idea of "development" is as the word suggests: "The systematic use of scientific and technical knowledge to meet specific objectives or requirements."
BusinessDictionary.com[^]
That's not the same thing as "have a quick google and give up if I can't find exactly the right code".