Last Updated: 11/14/2014 04:56:40 PM

My thoughts on cf.Objective changing their name.

My thoughts on cf.Objective changing their name.

cf.Objective() changed their name to dev.Objective() why did they do it? What does it mean?

 

One thing I have always liked about cf.Objective() is the feeling of community. Let's be honest, we don't go to conference *just* to learn.  We go to learn *with* other like minded people.  We could get the exact same instruction by watching a youtube video on the topic.  However what makes conferences so electric is that you are there with others and can get immediate feed back on your ideas, from people facing the same challenges as you. 

 

When cf.Objective first started it was to help people who identifiied themselves as ColdFusion developers, who mostly did ColdFusion all day long.  Today however many things have changed.  Our roles as developers has grown. Today we have to know a heck of a lot more than ColdFusion to get our jobs done. When knowing javascript became more and more vital to our jobs, cf.Objective() responded and added the js.Objective track. For the past couple of years ColdFusion topics represented less than half of the topics delievered at cf.Objective(). This is not because ColdFusion is less important to our jobs. It is because our jobs as developers have grown.  

 

cf.Objective() is rightfully changing their name to dev.Objective() because the challenges we face as web developers are universal.  Language is just syntax, but the problems we face in ColdFusion are also faced by people who write .Net,  Groovy, Ruby, Clojure & Scala.

 

Will there still be a good deal of ColdFusion topics at dev.Objective()? You betcha! 

You never forget your first language, and dev.Objective() will always have a special spot for ColdFusion, CFML & Railo.  The difference is we also are embracing other topics that ColdFusion developers can learn from that may not be directly ColdFusion related.  This conference has always targeted the intermediate / advanced developers looking for pragmatic ready to apply information, that has not changed. So don't expect a bunch of "Intro to language x" topics 

 

Bottom Line: cf.Objective() has changed to reflect the changing face of our community

 

Sincerely,

Tim Cunningham

dev.Objective() Content Chairman