Lots of good advice already, but I had a couple of things to add. First, it's likely programming will always allow you to make stupid errors relatively easily. Programmers design and build systems so that other people (or computers) won't be able to make stupid mistakes. In order to do that, a language has to give us lots of flexibilty, which equates to lots of rope to hang ourselves. It's just part of the job.
Secondly, I find Eclipse with EPIC really useful (there are other tools that give you similar functionality. That's just what I use). A lot of stupid errors are detected right away. Maybe not *everything*, but small errors like typos are highlighted as you type, so you don't have to run anything to find your compilation problems. A small time saving, you might say, but lots of small savings can add up to something big, allowing you more time to track down the really nasty problems.
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:
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||