Guardian Angel wrote: > On Mon, 2003-11-17 at 06:19, R. Joseph Newton wrote: > > Guardian Angel wrote: > > > > But now... i want to be more precise with my script. > > > So i made 2 extra if loops, 1 is looking for errors, and if so, also > > > check if there is no 127.0.0.x adres in it anymore (works so far :D) > > > > > Whoa! This is not the way to get a programming job done. Rambling does not get > > you there. > > Before you can write effective code, you have to focus your thinking process. > > Don't get > > caught up in fascination with coding tricks. Look for tools to accomplish clearly > > defined > > purposes. Express those purposes, and the steps to achieve them, in plain > > language. > > > > Most important, take a breath. > > > > Joseph > > > Uhm... lol... i get it. But this *is* working (although it will not be > the best code you ever seen ;)) > Ofcourse i can better make a complete plan of what i want, but that is > too much atm. > I have *no* experience with coding at all, and it's a bit overwhelming > for now :) ( a lot of statements, loops, array's, hashes etc) > So i was just trying to make my scripts step by step more difficult, so > i can understand *why* Perl is doing things, and what it is doing. > That way i can better understand what happends, and then (ofcourse) I > have to find out exactly what i want, and how i want it... but for now > that is too much.
Sounds good. It is good to stretch yourself, too, but the trick is to keep track of the process while you are doing it. Break things down into manageable chinks. This is really the core of effective programming IMHO. It is also fine to take a while working with simple programs. Many of the programming tasks needed are fairly straightforward. > > So i prefer little parts (which i can understand) and then step by step > learning more. > ie. i see a lot of ppl who start with (for me) heavy scripts (used with > 2 or 3 modules) while they have not really a clue of what they are > doing... copy/ paste will work, but it will definitly not *learn* to > write code yourself :D That can be alright too, if it helps you get started. My first Perl script, back in 2000,, was an adaptation of Matt's Guestbook script. I dinked with it a bit to use a hidden field in the submission form to specify a target page to put the code at the bottom of. The original scrit was for a single page that was all guestbook. My adaptations worked, and it was pretty cool. There were soe problems with this, too. For something like a week, I was stuck on a blind system error (since I didn't have a compiler at home to test my code on. It turns out that I was trying to access a hash element with parens. the text editor I was using didn't show the distinction clearly, and it wasn't until I pasted the code into my C++ IDE that I could even see the difference. Had I written smaller programs of my own earlier, I am sure this woudl not have escaped me. > And now i will take a deep breath.....aaahhhhhh (nice) Great! That and maybe taking a walk can often be just the ticket for unlocking sticky programming issues. Joseph -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
