Reminder: CFUnited 2010 Speaker Selection

November 25, 2009 · By webrat · No Comments

Just a reminder that speaker selection for CFUnited 2010 started and that if you have a CFML topic that you think should be discussed and you're want to try your hand at presenting, you should submit your here ( http://callforspeakers.cfconf.org/ ). If there's any interest in presenting Railo related topics (ehcache caching, clustering, etc), by all means, let us know so we can assist you.

If you haven't been to cfunited before, I highly recommend it. I went to the 2009 conference (Thanks again Railo!) and it was great. Met a lot of people, talked a lot about CFML, jQuery and AIR. I dare say there was a lot of CFML developers interested in jQuery tracks. If you think jQuery is being discussed way too much in the cfml community (is that possible?) and you're a fan of dojo and whatnot, YOU SHOULD BE PRESENTING. Topics like this are awesome because they're relevant and they expose CFML developers to another framework that they might possibly look into / work with.

If you are considering going to CFUnited, do yourself a favor, take a laptop. If you don't have one, beg, steal or borrow. There are a few hands on development track, but most of it is presentation and you should be trying out new code or brainstorming while you're there. The whole place is a big fountain of ideas. I have seen people assisting with debugging other people's code in the hallways, etc.

Plus, If you're working on something cool now, you have a chance to present that 'something' at CFUnited's demo mania - they let anyone get up and present interesting stuff on their project. Slidesix's desktop app, Fusiondox and John Mason's Merlin project were presented among others. Even Raymond Camden had a cfml maze demonstration that from his blog. So, big or small ideas, feel free to share with the CFML community!

Tags: Community · Conference

0 responses so far ↓

  • There are no comments yet...Kick things off by filling out the form below.

Leave a Comment

Leave this field empty: