----- Original Message -----
From: "Rogelio M. Serrano Jr." <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 18, 2002 7:54 AM
Subject: Re: [plug] GUI and UP CS
> > ----- Original Message -----
> > From: "Orlando Andico" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, January 17, 2002 11:54 AM
> > Subject: Re: [plug] GUI and UP CS
> >
> >
> > > On Thu, 17 Jan 2002, Andre Cruz wrote:
> > > ..
> > > > me to think first, write down ideas/outlines then code away. i'm
sure
> > > > guys like orly and dido like to program straight to the keyboard or
> > > > so...but to each his/her (in sacha's case!) own, i guess...
> > >
> > > I program to the keyboard and regret my design decision many months
(or
> > > even years) later. =)
> >
> > well for me, its depends on the tasks.... if the task is so easy, i can
go
> > straight ahead with the keyboard (even with my two eyes are close
<wink>)...
> > if the task is complicated, then a careful planning before going to the
> > keyboard....
> >
> > fooler.
>
> When in design phase i program at the keyboard. Just to try out the
> ideas right? Then do a prototype. Its is all part of making a design.
> Then do a full blown paper program then code it. There is no substitute
> for a well though out design. It is a long process. Thats why we reuse
> code right? so we minimise reinventing the wheel like we are all prone
> to doing.
>
> Now debugging is means a lot of things. And it can only be be done well
> if you know the program. And a well thought out program is easy to
> debug. Debugging is necessary because we just can not foresee all cases
> or circumstance that a program is going to run under. Paranoia
> might serve us well to minimise bugs but that is a debatable point.
>
================================
Things are starting to get complicated around here. The main point of
debugging is to remove all errors and have an
error free program. Isn't this what all programmers want, an error free
program?
CS graduates (not all but most of them) lacks training in the proper
approach to programming.
A program is a system which requires a systematic and well structured
approach. If we
take this for granted because we thought we are really good and has mastered
programming,
then we are wrong. You will observe that a carefully studied and planned out
system will always
turn out having lesser time for debugging or if not, no debugging at all.
One reality we need to see is that,
the bigger a program is (lots of processes involved) the more it needs
careful analysis.
The best approach to careful analysis, is a systematic approach (not leaving
any stones unturned, doing it step by step).
This suggests manually going through all the processes and carefully taking
notes (never go to step 5 without going
through steps 1, 2, 3, & 4).
SUGGESTED STRUCTURED APPROACH:
1. Write down the problem on a piece of paper. There is no substitute for
this.
A piece of paper can memorize the whole problem better than your brain
(that is to the letter).
Note: when writing the problem take special concern for the sub-problems
branching out
because this is where most of the bugs come from.
2. When you have completely layed-down the problem and sub-problems,
do a careful study on how they will be solved. Put it in writing.
3. Write the algorithm in English or dialect where you are most competent
in.
4. Translate the resulting algorithm into whatever computer language you are
most competent in.
SYSTEMS LIFE CYCLE
1. Problem Identification Phase
2. Systems Analysis Phase
3. Systems Design Phase
4. Implementation Phase
5. Testing Phase
6. Installation Phase
7. Documentation Phase
Going directly to your PC and encode your program is good only for programs
with few processes involved. I consider this only as my programming exercise
but not programming as professional programmer.
Start right and end right. When you want to go North, start going North. You
may use the route
going South but it is the longer route(granting that the route goes around a
sphere).
Rudelskie
============================================
> >
> > _
> > Philippine Linux Users Group. Web site and archives at
http://plug.linux.org.
> > ph
> > To leave: send "unsubscribe" in the body to
[EMAIL PROTECTED]
> >
> > To subscribe to the Linux Newbies' List: send "subscribe" in the body to
ph-l
> > [EMAIL PROTECTED]
> >
> _
> Philippine Linux Users Group. Web site and archives at
http://plug.linux.org.ph
> To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
>
> To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
>
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
