I'm more comfortable with the environment set up as I prefer (which basically means four Xterms open). We prefer the familar, and working with the unfamiliar requires more adjustment and mental energy for the same results.
That said, sometimes diagramming things or writing down pseudo code is very helpful. It forces you to think about the correctness of your solution and the design, rather than the mechanics of making the thing run. I still have trouble reading long sections of code out of books, though, which is odd after all this time.
I have a bad habit of writing just enough stub code to test, and then alternating between testing and adding slightly more code. That's good in some cases, but I think I'd be more efficient if I programmed bigger chunks at once.
Either way, you should not count lines in a file with a one-liner like this, even if it's shorter. It frightens people:
perl -pe "END{ die }" file_name >/dev/null
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.