|
|
Posted by laverdir on 03/16/07 10:50
Rik wrote:
> laverdir <MOVE-RE_ME_laverdir@post.t-com.hr> wrote:
>
>> Steve wrote:
>>
>>> "laverdir" <MOVE-RE_ME_laverdir@post.t-com.hr> wrote:
>>> | <SNIP hardy legible query>
>
>
>>> surely $query doesn't look like this in your code. i assume it
>>> looks like shit here b/c of the way your usenet client wrapped the
>>> text...right. i'd be a fool to believe anyone would intentionally
>>> create unmanageble inline sql statements. i mean, everyone knows
>>> that some employers would pass over otherwise qualified applicants
>>> otherwise. i'm sure the statement you have in real life looks
>>> something like this:
>>> <SNIP formatted query>
>>>
>> it looked similar to this when the query was in
>> designing proces, but then squizeed to one line
>> for space saving..
>
>
> Do you pay for spaces? I'd hardly think so. Having newlines & spaces:
> - has close to no impact on PHP and/or MySQL's speed of interpretation.
> - has zero impact on the bandwidth used to clients.
> - is really a help when having to work on the code later.
>
> If the spaces are the difference between fitting in the hosting plan or
> not you're going to need more room in future anyway. Removing this
> formatting from the code is only usefull when it's send to clients,
> like javascript. (Or when you have a grudge against fellow/future
> coders on the project, including yourself).
>
> Moral of the story: keep nice formatting.
screen space saving, to be precise.
for me, it's faster to read algorithm
workflow.
why do you care anyway?
are you some kind of coding martha stewart?
quoting beginners guides to writing 'readable'
code didn't help in this case.
im writing code for 22 years and don't care
how it's writen, i can read it equaly fast.
Navigation:
[Reply to this message]
|