a fair point, Blair
the other side of the equation of course is too much hand-holding that
it gets in the way, either by abstracting too much of the detail so
you don't know what's happening under the covers - or - it just plain
gets it wrong in edge-cases (special headers needed in CF
Lol... I remember that breakfast Barry!
On Wed, Jun 25, 2008 at 4:44 PM, Barry Beattie [EMAIL PROTECTED]
wrote:
a fair point, Blair
the other side of the equation of course is too much hand-holding that
it gets in the way, either by abstracting too much of the detail so
you don't know
Personally I think the tooling in .net is the worst thing to happen to
a good language. I like many of the language features in c#, but the
patterns that the tooling supports (code behind, page controllers)
just aren't as good as some of the best practice patterns in the Java
world. Also,
Scenario You're building an enterprise application for an existing
database You have Flex 3 front ends ColdFusion 8 backend!
Install the ColdFusion extensions (free) for Flex Builder Create a new
Flex project Setup your CF setting in the Flex project enable RDS
You can now browse to any
I get there is a use case for passive code gen, but for me it's pretty
limited. Assume only 20% of effort is building site (compared to
maintenance) and 20% is building the first cut with 80% being making
changes to original version, the most it can do is speed up 4% of the
app. It isn't
Hi Peter,
Where's the project management, your first cut shouldn't be done until
specifications are signed off, anything else is a change request and has a $
value.
Save yourself time and your company $'s by at least exploring PMBok project
management framework, otherwise you will always have a
Because your clients always know upfront what they need before you
build it? There's a reason why Agile and lean have become much more
popular. I believe our goal as professional software engineers is to
lower the cost of change so we can explore the solution space with our
clients to
Hi Peter,
It was basically because there was always a core set of functionality
required, usually driven by standards and best practices, additional
functionality was added as needed. They always had to provide a business
case to us, which ultimately defined their requirements after
Hi Rae,
Thanks for the reference for PMBok. I'll definitely check it out!
Best Wishes,
Peter
On Jun 25, 2008, at 5:00 AM, Rae Buerckner wrote:
Hi Peter,
It was basically because there was always a core set of
functionality required, usually driven by standards and best
practices,
