I am not blind, but I code in braille. Naturally this is time consuming, but since I do not program for a living I have the luxury of taking years to complete a program if I so choose. In fact, the current program I am working on started out in 1995 as a Perl 4 program. I have had to make some changes in recent years to keep up with Perl 5 and I hope it will be finished before Perl 6 hits the streets, otherwise I fear it may not be finished before I am deceased. One of the downsides to this approach is that many other programs like it have emerged throughout its many years of development and it is unlikely that anyone will care when I am finished with it - I refuse to let it go, however, as it is my legacy. There is an upside to this approach to writing programs, and that is *gawk*..kck..kck..*gasp*

Ok, kidding aside... There's already alot of good advice posted here, so I will just add my $0.02...

Having run a BBS in the 80's has instilled in me the appropriate amount of paranoia to always quadruple check user input. I've drawn from that experience to avoid many of the CGI pitfalls without having to experience the shame of falling victim first. But then, I don't do that for a living either.

In reply to Re: How to write programs? by djohnston
in thread How to write programs? by artist

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.