AZGroups.com

We count our first run of Desert Code Camp to be a success. On the eval forms we received, when asked if people would attend this kind of event in the future, absolutely everyone said "Yes"! Remarkable. Because of this very positive response, we have already started planning for the next Desert Code Camp event. We are looking at late October or early November, just 6 months away. The same kind of fun, and held at the same facility. Hoping to have even more attendance next time. We are currently in the very early planning stages for this next event.  If you would like to give us feedback, we're all ears!  Let us know what would make the next event even more memorable.

-Lorin

 

Everything was great except there were too many good sessions to choose from (during any particular hour) and it's just not possible to be in two places at once.

I'd like to see an official forum for 'suggested sessions'.  Until then, I'll suggest two here: "Basic DotNetNuke Module Development" and "Advanced DotNetNuke Module Development"

-Nick

Most of the sessions I attended felt a little rushed near the end. Maybe the length of each session should be increased by 15 - 30 minutes? Another way to handle it would be to offer some sessions as "super-sized" 2 hour sessions if they have a lot of material to cover.

I agree. I had trouble delivering both of my talks in an hour, and it left no time for questions at the end.

How about having each session be around 1:25. That would give me another 15 of talk time and 10 minutes for questions. That would then give folks 5 minutes travel time to get to the next session, which was another problem.

I like the "super session" idea, but unless they are all at the same time, you'll end up with all the room times being staggered, which will make it almost impossible for attendees to schedule. But if they're all at the same time, keynote style, then chances are there will be a lot of good talks guaranteed to conflict with each other.

Another thing: I really think the next Desert Code Camp should be run over two days. The other ones I've attended in SoCal were all 2 days, which made them a lot more laid back and less rushed.

Just my 2c.

---

--Steve

I'm looking forward to the next CodeCamp.  Thanks for making this past one so good.

Some thoughts:

Please do not schedule the next one for October 20-22, 2006.   Those are the dates for the annual international Ruby conference, to held this year in Denver. :)

As others have mentioned, the scheduling between sessions was tight.  I found myself sneaking out of at least one talk in order to get to another in time.    And when I gave my talk I felt I should wait a bit before starting because I realized people were having trouble getting around , so travel time should just be built into the schedule.

Of more interest to me, though, is the idea that leaving gaps between sessions means more time for people to mingle and chat.  The only time I had a chance to talk to people I didn't already know was at lunch, and a big part of a good tech conference is the hallway track.

I like the idea of spreading the conf over two days; that should make it easier to to leave room between talks, and have fewer simultaneous talks.

---

----
James Britt

www.jamesbritt.com
www.ruby-doc.org
www.rubystuff.com
www.neurogami.com

I also agree with the idea of sessions being spilt into 2 days so that we don't have to choose between two good sessions.

 Ashish

http://www.loniya.com/ 

---

Ashish Gupta
www.Loniya.com
www.misswebhunt.com
www.dealspod.com