> Barry:Would you say it's been happening for what? 5+ years now?
I'd really like to respond to this chapter-and-verse at the moment but
I'm really pushed for time...
but I will say that (IMHO) Kay Smoljak is right on the money: The
issue isn't a religious war. it's not good Vs evil or red team Vs
blue - unless you're a shareholder of Adobe or Microsoft (hey Scott -
shares in the company are part of your package, yes?)
for everyone else, a particular technology is an enabler. That's all.
Sure people have their preference - and I came kicking and screaming
into CF late 2002 (CF6.0/Redsky/CF6.1), grudgingly used it then like
it and stayed for the ride. Meanwhile I'd been using ASP (classic) and
had been part of the ASP.NET public beta up to it's release where I
deamed ASP.NET 1.0 a pile of rubbish and turned my back on it (it was
the infinite post-backs as one reason that killed it for me although I
really like some things in C# - it has what Java should)
but it's noteworthy to see that when I was a CF-noob, "old hands" like
Gary Menzel were active in the community - now Vaughn and the guys are
migrating (have migrated?) to Java and are nowhere to be seen in the
CF world. People move on, situations change.
"ColdFusion - he's just this guy, y'know?"
don't get me wrong, for mine, CF is the best darn bang-for-buck I can
get. But if you asked a question of which web-based technology is
"best" then you'll not get one single answer: as Sean Corfield often
says "it depends!". there's still a ton of dynamic web apps written in
VBScript (ASP classic - depricated in 2003). Ford Vs Holden, anyone?
and, leaning heavily on the capabilities of the little Flash Player,
Adobe are starting to get together an interesting technology stack
suitable for the "digital media" world (although the mess of LiveCycle
with DS and ES, et al, needs to be sorted - too confusing for
managers). It makes the ownership of CF by Adobe that (seems to start
to) have good flow-on effects.
so when it comes to job choices, platform can a modifier. ie: you take
a dev job with a CF flavour.
1) enabler: the technology becomes the vehicle for people to do things
better/faster, etc.
2) enabler: the technology is a joy to use so it gives job
statisfaction doing things.
3) enabler: the technology has the platform longevity to keep you
doing this for as long as you need it to.
and I have no doubt that coding CF could give me both for many years
to come. I support the technology to do my bit in it thriving into the
future. I have no shares in Adobe so the long-term outcome for me is
purely future employment.
which is why I try and get people interested in CFUG's, etc - being
active in ensuring the platform has logevity and providing job
security by platform security, instead of being a passenger blown
along with the winds... (as well as keeping skills up (1) which leads
to better results (2))
but...
if you were hunting for a job, would you follow the technology stack
and hang the industry it's used in? Keep in mind the further you
progress through the ranks, the less important specific technology
becomes as you need to manage outcomes and what the technology has to
do as business needs change/grow (as Gary Menzel realised - and
planned for - a couple of years ago).
or would you follow the path of the industry you know well and that
you can apply your skills and domain knowledge into and then use the
technology to enable outcomes?
Idealy you'd seek one that would do both ... but as I'm finding,
they're hard to come by.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"cfaussie" group.
To post to this group, send email to cfaussie@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en
-~----------~----~----~----~------~----~------~--~---
