Rethinking the Java Curriculum: Goodbye, HelloWorld!
Subject:   Confusing two different things
Date:   2002-08-23 07:48:58
From:   davetron5000
As many have pointed out, and the like is for learning two things:

1. The development cycle for programming anything: write code, compile code, run code, repeat
2. To verify that your environment is set up.

I feel that schools do not spend enough time on "how to program" and too much on theoretical discussions about non-applicable things. Articles like this make me think that there is even more removal of "how to program" knowledge from the students.

I also feel that Java should not be the introductory language for students, because it robs them of the chance to learn about resource allocation and management (namely memory), which is very important in helping them PROGRAM COMPUTERS, which is what they are being trained to do for the most part.

Additionally, once you are in your methods of your well-architected objects and all that, you are writing a procedure. A method in the real world EVENTUALLY boils down to a procedure for acomplishing some task. That is where programming should start.

The first programming language I learned in school was Karel the Robot, because it taught me how to problem solve and write a robust procedure to accomplish something. From there you expand.

OO is a tool. Not all of it is good. XP is a tool. Not all of it is good. The ability to solve a problem and tell a computer EXACTLY what to do IS what programming is all about. This should be taught in school, and it should not be intermingled with the teaching of various techniques/theories/etc.

1 to 1 of 1
  1. Confusing two different things
    2002-08-23 15:05:50  blrfl [View]

1 to 1 of 1