in reply to Re^2: Free Perl IDE for a begginer
in thread Free Perl IDE for a begginer
I'm no expert.
I just have fun with programming..
But, ugly code is awful.
And definitely not the way of the lowest resitance.
Why ?
I believe you can do fast and simple hacks - which will work and do what you want.
But, if you e.g. instead of writing some functions, modules, .. , just hack a script with a few hundred lines without a structure at all, it will work now - but it's extremely hard to maintain such a thing.
So instead of thinking about a concept - which needs some time -, and having the experience that it's possible to materialize your thoughts in a program, you just hack it down. And if there are needed changes in the script (as always), the script will get uglier and uglier - until you don't know anymore at all what the heck is happening in your program. Which is quite frustrating, time expensive, and you'll need a debugger(.-)).
On the other hand I've always made the experience that some thoughts about the structure before starting to code pay out.
It's a great feeling to me to find solutions - and you'll be able to change your scripts with much less work.
So I'd like to propose structured and well thought solutions - Although perhaps this could seem like unneccessary work
Have fun :-)
I just have fun with programming..
But, ugly code is awful.
And definitely not the way of the lowest resitance.
Why ?
I believe you can do fast and simple hacks - which will work and do what you want.
But, if you e.g. instead of writing some functions, modules, .. , just hack a script with a few hundred lines without a structure at all, it will work now - but it's extremely hard to maintain such a thing.
So instead of thinking about a concept - which needs some time -, and having the experience that it's possible to materialize your thoughts in a program, you just hack it down. And if there are needed changes in the script (as always), the script will get uglier and uglier - until you don't know anymore at all what the heck is happening in your program. Which is quite frustrating, time expensive, and you'll need a debugger(.-)).
On the other hand I've always made the experience that some thoughts about the structure before starting to code pay out.
It's a great feeling to me to find solutions - and you'll be able to change your scripts with much less work.
So I'd like to propose structured and well thought solutions - Although perhaps this could seem like unneccessary work
Have fun :-)
|
|---|
In Section
Seekers of Perl Wisdom