June 25, 2014
Before we could create an excellent program, there are important steps that we should remember. I noticed that they are similar with the scientific method.
So yeah, first we need to understand the problem / observation and it is not aneasy task. Most problems need serious thinking to be able to grasp it and not all the time we would be able to understand them. Think. Think. Think.
Second is to create an algorithms / create hypothesis that will solve the problem. Pseudo codes and Flowcharts. Writing and taking notes of steps is great so that we wouldn't forget them and we could arrange them in right sequence. When we were tasked to create flowcharts for in 4th year, it took me a long time to finish because I got confused by the different shapes to be used. I asked myself, "Why not just list down the steps? Bullet form would be best." Pseudo code is better, in my opinion.
Third, convert the algorithm to programming language / experiment. This would be the time to use an IDE (such as Lazarus, NetBeans, and Eclipse) to input the codes. Right now, I'm using NetBeans because it is the one our professor in IntPrg told us to use. I don't memorize all java keywords (there are a lot), so sometimes I commit lexical errors and make up my own words.
------------------------------------------------------------------------------------------------------------
*It is a programmer's task to make a user's life as easy as possible while he has a hard time creating programs. Haha. How sad.
Before we could create an excellent program, there are important steps that we should remember. I noticed that they are similar with the scientific method.
So yeah, first we need to understand the problem / observation and it is not an
Second is to create an algorithms / create hypothesis that will solve the problem. Pseudo codes and Flowcharts. Writing and taking notes of steps is great so that we wouldn't forget them and we could arrange them in right sequence. When we were tasked to create flowcharts for in 4th year, it took me a long time to finish because I got confused by the different shapes to be used. I asked myself, "Why not just list down the steps? Bullet form would be best." Pseudo code is better, in my opinion.
Third, convert the algorithm to programming language / experiment. This would be the time to use an IDE (such as Lazarus, NetBeans, and Eclipse) to input the codes. Right now, I'm using NetBeans because it is the one our professor in IntPrg told us to use. I don't memorize all java keywords (there are a lot), so sometimes I commit lexical errors and make up my own words.
------------------------------------------------------------------------------------------------------------
*It is a programmer's task to make a user's life as easy as possible while he has a hard time creating programs. Haha. How sad.