http://wikipedlla.com/programmer_etiquette_and_writing_good_cf_code
(I thought the teacher in me was well and truly burnt to a crisp...
aparently not...)
hyperthetical
* you're finishing off someone elses project, it's only a couple of
weeks of work
* that person is someone that you
I just wanted to point out a few things to anyone in the know.
Barry is currently doing work for me, fixing up the project he is
working on, and that he has talked about here.
I am not the original coder on this project. A contractor was brought
in for this.
For a variety of reasons, the people
On Mar 19, 1:02 pm, barry.b [EMAIL PROTECTED] wrote:
see, that's my point - dodgy practices that slow development down,
especially if you're tasked to come in later and finish the pile of
rubbish.
there should be no reason that people write bad** code, there's enough
code out there for
I agree. Its that problem were we blame the pen for the spelling mistake.
This also reflects the strengths and weaknesses of coldFusion.
Because its an easy language people arent learning how to write code with
maintenance in mind
until they actually have to maintain an app someone else
@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
I agree. Its that problem were we blame the pen for the spelling mistake.
This also reflects the strengths and weaknesses of coldFusion.
Because its an easy language people arent learning how to write code
:* [cfaussie] Re: programmer etiquette and writing good CF code
I agree. Its that problem were we blame the pen for the spelling mistake.
This also reflects the strengths and weaknesses of coldFusion.
Because its an easy language people arent learning how to write code
PROTECTED] On Behalf
Of Mark Ireland
Sent: Tuesday, 25 March 2008 6:14 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
I agree. Its that problem were we blame the pen for the spelling mistake.
This also reflects the strengths and weaknesses
:00 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
Nope, I agree with Geoff and Mark. You actually need reasonable technical
skills to write code (even crap code) in C++, etc *and* get it to work in a
public environment... I think the point
Sent: Saturday, 15 March 2008 4:59 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
Its not all about pooling. That's just one of the advantages for using it
-Original Message-
From: cfaussie@googlegroups.com [mailto
Message-
From: cfaussie@googlegroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Brett Payne-Rhodes
Sent: Tuesday, 25 March 2008 7:00 PM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
Nope, I agree with Geoff and Mark. You actually need reasonable
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
Nope, I agree with Geoff and Mark. You actually need reasonable
technical skills to write code (even crap code) in C++, etc *and*
get it
to work in a public environment... I think the point
@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf
Of Joel Cass
Sent: Wednesday, 26 March 2008 9:40 AM
To: cfaussie@googlegroups.com
Subject: [cfaussie] Re: programmer etiquette and writing good CF code
Meh.
I reckon the best type of programmer is one that accepts the faults of
others
12 matches
Mail list logo
