I have never, ever understood the need to obfuscate code in production. Do people really think it's a security measure? I've heard that touted, but never bought into it.
This may be off topic, but my chaotic brain sees it as relevant, so here goes: There has been some discussion of late as to first, second, and third rate programmers. My take on this is that we should be striving to become first rate communicators and that first rate programming is simply a means to that end. It's not just that we need to be smart about the code we produce. We ultimately need to be smart about how we use that code to get a message across, be it to the end user or the people who must live with our coding decisions, present and future. As FoxtrotUniform points out, the person you help just might be YOU. Obfuscation is a step in the wrong direction, IMHO. Fine as a game or an exercise, but definitely, definitely not for production environs. Consider this a humble third and ++'s to the author. <flame suit on>
----
I am what I read
-
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.
|