Hey Peter, thanks for breaking the ice on this thread. :-) Actually I thought that the thread would be a very interesting e-conversation between programmers on the list and would generate interest for others to join the programming club thus I listed it. My plate is full with other things like learning vectors etc but am sharing some insights as I go along. Methods are the code building blocks and therefore determine the code flow in one's app/program. Flow charts may not be of help because they are provide an overview to certain levels eg decision making blocks of if/else. Rgds. On Tue, Mar 30, 2010 at 8:28 PM, Peter Karunyu <pkarunyu@gmail.com> wrote:
I personally create functions/methods based on "uses"
For example, suppose i have a registration form, i will probably have methods like: printUserRegistrationForm() and consequently processUserRegistrationForm()
But I normally find that i derive the variables AFTER coming up with the methods, and not before. And i've never been able to predefine all variables before I finish the project, but then again, I often use a laissez faire approach to software design :-)
Have you explored using pseudo code and flowcharts? If done properly, these are just like coding on paper.