Two things I've learned:
1. Write all code as if someone else is going to have to go through it without your assistance. I made the mistake of assuming no one would ever see the backend code to something I wrote. Completely wrong. It's no fun having someone actually laugh at you for routine or variable name choices-- even if you find out later that you're a better programmer than they are.
A consequent of this mindset is that you have the ability to go back into code later and expect that you don't have to dredge through frail memories of why you did what where.
2. Ego? I make enough completely stupid mistakes that I figure every bug is my fault, even after I've tested it upsidedown, backwards, and inside-out. It's actually a relief to run against some undocumented feature/failing of a language, module, or (most often in my case) database interface application.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||