Just because Perl is a higher-level
language than C doesn't mean that writing in it frees you from good
design practices.
Of course. I'm not suggesting abondoning good design practices. I'm suggesting a different set of design practices that is popular amoung some groups of Perl programmers.
You do create
mockups of your website beforehand, right?
No, I use a template system so that design and code are seperate, and design can be changed on the fly. Perhaps the web designers resposible for the look and feel do mockups; I wouldn't know what good web design practices are, I'm just a programmer.
Now, pseudo-code takes a lot of forms. For example, if you're
writing a CGI script, the pseudo-code has been created for you -
it's called CGI.pm and you should use it.
No, that's called code reuse, and yes it is a wonderful thing.
You then go and write a
prototype. You test that, adding onto it, and end up with your
development module. You bang on that some more and end up with
v0.1 - that's a type of psuedo-code we call "prototyping" and
"iterative development".
No, that's a rough draft or prototype, not pseudocode. By definition, pseudocode is not real code and cannot be executed. Not everything that is part of the design phase is pseudocode.
--
Snazzy tagline here