And yes, people still write entire programs on paper, and pray that they haven't forgotten a semicolon somewhere. To what end? Beats me. You have to type it in anyway...
Some of that may be age-related. I was raised on pencil and paper, and still find that I think better when I can sketch things out on paper. Similarly, I find it almost impossible to read or proofread using the screen. I need to have a book or print something out onto paper. That's one reason I needed to get Programming Perl, even though much of that is contained in the perldocs or man pages. It's not just the content, it's also the presentation. For well over half my life, computers weren't even an option.
Typing in something you've written out by hand isn't always a waste of effort. By re-typing, you are forced to deal with your code on the level of characters or small units, which often helps you find errors you've made (usually typos, not logic errors).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|