gmiajy4
asked on
Problem solving With High Level Languages
I am an applications programmer, when I have a specification for a problem, I normally think about the solution for a while and then the first solution that comes to me I usually design then test the design and then code,
then when the prog is running, it is then i test for speed issues and if it runs slowly I optimise, I have been talking to a few programmers who say that just by looking at code on paper they can tell that it will be slow - or while the algo is in their mind, is this the case with you, I cannot tell if a prog will be fast until i see it running. Also i only like to optimise whwn necessary, to me program structure, with tight functions is much more important, but do most programmers just code the first solution that comes to them, when searching for a solution ??
then when the prog is running, it is then i test for speed issues and if it runs slowly I optimise, I have been talking to a few programmers who say that just by looking at code on paper they can tell that it will be slow - or while the algo is in their mind, is this the case with you, I cannot tell if a prog will be fast until i see it running. Also i only like to optimise whwn necessary, to me program structure, with tight functions is much more important, but do most programmers just code the first solution that comes to them, when searching for a solution ??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
When one will look it up then one can act his way."
You have to look then act.
Shay.
*** If you wnat more links then email to shay@hili.com. ***