previous next
Satisfaction: 3
Liked_Best: The technical sessions, though some of the keynotes were very entertaining.
Short_Talk: Did_Not_Like
Short_Talk_Length: 15
Short_Talk_Format: Horizontal
Parallel: Just_Right
Format: 1+3+
Later_Sessions: No
Exhibit_Hall_Hours: I had plenty of time to visit the exhibits. However, as the number of exhibits grows, then more hours will probably be required.
OS_Pavillion: Yes
Keynotes: Fewer
Reduced_Number_of_Keynotes: 3
Improve_Next_Year: Post lunch menus. For me, I like the JavaOne idea of having buffet and box lunch choice. I typically prefer the box lunch. As a first time attendee, I wasn\'t aware that lunch was included.
I couldn\'t find the registration hours posted on the website. The site should also probably should indicate that parking is free.
I had a few bad experiences with the soda machines. One coke machines was unplugged, the other was out of diet coke. One pepsi machine ate money. I notified eclipseCon registration desk so they could post a sign, but I don\'t believe they did anything. It ate a colleagues money as well. I found him in the hotel store buying a coke, like me. So I used the conference center phone and their catering division refunded my money and an hour later sent someone to refill the machine.
I didn\'t learn about the cookies/brownies and soda in the registration area until the last day.
A/V was good. Tutorials not so good. As you are aware many rooms had no electrical outlets for our laptops until an hour or so into the morning tutorials. The tutorials appeared to have too much material for hands-on learning. Installing the requisite material took longer than the anticipated. (In both my tutorials, the requisites stated on the requisite page were wrong; i.e. one needed updated release of eclipse another hadn\'t put any requirements.)
Variance in the tutorial materials. One of mine was good about writing down the steps; the other not so good. I think its great the respective speakers wanted to share their knowledge, but they needed to weed it down to the key features that could be accomplished within the time and leave the rest as \"homework\" on backup slides.
My colleagues had similar experiences in their tutorials. I think I would have a hard time convincing my engineering lead that the tutorials are a good return on investment.
I saw a lot of attendees writing their trip reports during sessions. It might be fun to have a communal trip report. Each session might have a trip report subpage similar to feedback. I imagine speakers might like it as well because they could readily see if they made their key points came accross. Nevermind, that it is always interesting to see what others thought.
Wireless was excellent, thank you.
Location: maybe