Ahahahahahhaha. Mobo.a ug pangisip nimo, Sir, oi. Wala ko ni post para mo tubag sa iyang problema, ni post ko para mo correct sa ni hatag ug solution.
Wala ka ni basa sa akong gi hatag nga link sa?
Kani nalang daan Sir murag kasabot man siguro ka ani.
Let us propose the following principle: The irresistible beauty of programming consists in the reduction of complex formal processes to a very small set of primitive operations. Java, instead of exposing this beauty, encourages the programmer to approach problem-solving like a plumber in a hardware store: by rummaging through a multitude of drawers (i.e. packages) we will end up finding some gadget (i.e. class) that does roughly what we want. How it does it is not interesting! The result is a student who knows how to put a simple program together, but does not know how to program. A further pitfall of the early use of Java libraries and frameworks is that it is impossible for the student to develop a sense of the run-time cost of what is written because it is extremely hard to know what any method call will eventually execute.