On Fri, 17 Aug 2001, Tony Duell wrote:
> I am not convinced. While the 'instant gratification' (you type a
> statement without a line number and the result comes right back) might
> be useful when you're starting out, it also encourages the 'modify at
> random until it works' style of programming, rather than thinking
> about the problem, thinking about how to solve it, and only then
> actually writing the program.
This is only the case if you are taught this way, or do not develop skills
beyond this method of programming. The only reason we all (or most of us
at least) drive cars in a civilized manner is because we are taught to do
so. If it was up to us to drive the way we wanted, imagine the choas (and
fun) on the roadway.
> Needless to say, I consider 'modify at random until it works' to be a
> very Bad Thing!
One has to start somewhere! This is the best way to learn. Or did you
just pick up a soldering iron one day and simply know what to do? I don't
think so. Trial and error is the best learning tool.
> I've seen hardware 'designers' do something similar with FPGAs (and
> other technologies that are easy to modify). Things like 'maybe it'll
> work if I change this AND gate to an OR gate' or 'I'll try inverting
> that clock signal'. Or 'Maybe I need one more state in that counter'.
> No real idea as to what they should be doing, and why.
Granted, if you want to become an engineer, or in the very least a
"professional", you have to evolve beyond trial and error. But as I said,
you have to start at the bottom and work your way up. I would never start
a student off in a rigorous, structured environment. What a perfect way
to turn them off.
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger
http://www.vintage.org
Received on Fri Aug 17 2001 - 20:28:36 BST