|Perl: the Markov chain saw|
Structured vs. Unstructured Languagesby gryng (Hermit)
|on Aug 03, 2000 at 02:47 UTC||Need Help??|
I want to start this post out with an "ommmmm". That's right clear your monkish spirit and relax.
Now, we all agree that there are two parts to programming, that which is the language, and that which is beyond the language -- what you created, a part of you, and thus a mirror, and so, a problem solver.
They key to becoming a programmer is to become a problem solver, and impart that skill into your programs and thus breath into them life.
However, it would be easy to say that the programming language is not important, a mask or sheet that covers up the true nature of the problem solver you create -- something that hinders and hides your efforts.
It is so that the language is a mere contrievance and hinders the unwary.
But it is also so that each language has in itself it's own beauty, like a well adorned mask, that in some ways enhances what is behind rather than hide it.
Therefore the choice of your programming language shapes the nature of your problem solver. Unstructured languages lend to the programmer power like the water fall and bee-hive. Structured languages lend to the programmer power like the great thinkers and craftsmen.
And for those that start off, it may be dangerous to use the untamed power of the unstructured language, but it offers them a kind of greed that lets them further the developement of the problem solver.
But for those that start off with structured languages a greater discipline and drive is needed, because the power of control requires more energy to develop as great of works as the unstructured languages which lend the power of titans to the initiate.
And return to the center, breath out,