The second piece of code looks more structured, visual-friendly and self-explaining. Reading only the few first lines makes it clear that there's a form and a ticker and a story that goes on around these...The first code on the other hand makes it mentally exhaustive since you need to incrementally follow the infix arrow to the next and collectively decide on the overall synergy all these pointing arrows will possess, hence, maintaining such a code by someone else can invite wrath upon the one who originally wrote it..
At the end, it all boils down to preferences, if you're working in a team, there will be an agreed upon style and method to code design and its documentation. If you're solo then it is you who calls the shots on the style choice but meanwhile keep reading others' code and inspecting others' styles for you to be flexible enough to adjust to style modifications...
Best of luck :)
Excellence is an Endeavor of Persistence.
A Year-Old Monk :D .
-
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.
|
