Writing things down (even without code) helps a lot of the time. Many call that Rubber Duck Debugging. I'll explain my issue to my wife (who has no idea what I'm talking about), to myself on a walk along the waterfront at my home, or to my desk as I'm headbanging it out of frustration.
Well, i usually try to explain things to my "internal imaginery dumb user personality". Basically, a fantasy personality in my own head that doesn't know much about computers. Same strategy i use when designing user interfaces and similar stuff. Now, whoever says "you don't have to be mad to work here" - well, madness certainly helped me to improve code quality and user experience ;-)
perl -e 'use MIME::Base64; print decode_base64("4pmsIE5ldmVyIGdvbm5hIGdpdmUgeW91IHVwCiAgTmV2ZXIgZ29ubmEgbGV0IHlvdSBkb3duLi4uIOKZqwo=");'
-
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.
|