Thread: Better way

What do you suggest as the better practice when coding a program?

1.Figure out absolutely every little detail about the functioning of structures, classes, and functions, that goes inside the program before starting to code. Write down all those things, and start to write the program as the paper says.

OR

2.First only think of the basic functioning of the program and start to build structures and functions in a basic way. While the work in progress, decide all the small details that should be included in structures and functions. (I feel that this way is easier)

- Kasun

You should have a pretty good idea of what you can and cannot do without actually doing it, so I write all the class and function definitions, write the central portion of my program (main function) and then go and code in all the interfaces, etc..

Having done some initial design, you should be able to code and test a class in isolation before using it in your application.

Being able to define everything in fine detail is certainly one approach; these days, particularly with OO, an iterative approach is perhaps more common.

It's 6am, so his name escapes me, but one of the creators of C once said "Debugging is twice as hard as coding. Therefore if you code as cleverly as possible, you are by definition unable to debug your own code."

Just an amusing quote that I liked.

Originally posted by skorman00
It's 6am, so his name escapes me, but one of the creators of C once said "Debugging is twice as hard as coding. Therefore if you code as cleverly as possible, you are by definition unable to debug your own code."

Just an amusing quote that I liked.

A quick search on Google threw up:

“Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it.” – Brian W. Kernighan