Taco
I
think you need to be careful with producing a "methodology". Its one thing
to instill a set of instructions, but you need to make sure that your not, in my
opinion, telling a developer how to code. In some ways you could be
inhibiting development progress because, for example, a coder have always
written "count(*)" and now your saying that it has to be "COUNT(*)". To me
its like saying "For this project you have to write with your left hand and not
your right"
anyway
just
my 2cents
--------Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Taco Fleur
Sent: Wednesday, 7 January 2004 9:58 PM
To: CFAussie Mailing List
Subject: [cfaussie] MethodologyGuys (Guru's),I was just (humbly) wondering if you could gaze your hawk eyes over the following http://www.tacofleur.com/index/blog/archive/2004/01/?072043It's basically a methodology I have successfully worked with for a long time, I know all you Guru's out there all have your own Methodologies, so therefore I would appreciate some input if you have some time.As you might notice, it's not pretty and not finished, but if I don't throw it out there now I never will.....Taco Fleurhttp://www.tacofleur.com/index/blog/
0421 851 786
Tell me and I will forget
Show me and I will remember
Teach me and I will learn---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004
