My nice employer allowed me to visit a software conference in June (International PHP Conference, for those who care). Wanting to make the most of it, I would ask the more experienced conference goers in here to give me some tips on what I could do to maximize my learning experience on the conference, and to reduce beginner mistakes.Sorry that this question is a little ambiguous, but I think it's best to keep it a little bit more open, so I can get a wide range of Ideas, and it will be of more use to further people seeking for an answer.
Attending my first software conference - any tips before I go?
experience
Review the schedule before you go.Choose two sessions for each time slot. Some will get cancelled, some moved, some full, some you'll decide that the speaker was terrible last time, some you'll just want to hear them speak again, but you'll need options.Take notes, however you would normally.  I prefer a notepad and pen, but make sure you use the method you are most comfortable with.  Many of these will be useless later, or at least my own notes often are, but I find I retain more and can get the gestalt, which I find the most useful.If possible have a buddy system.  Each of you take a track relevant to your position, or employer, or where the industry or your particular use of the technology is likely to be headed.Talk to other attendees.  I've made both interesting social and business contacts this way, in addition to the added perspective and tips on what/who to go see, especially as many sessions are offered at multiple times.Use what you've learned.  Practice those IDE shortcuts, write up that sample application, read the mentioned reference documentation, and do it all at the end of the day, back in your room. [Edit] 7. (or 8. see @Ozz comment.) Give a presentation of the highlights to your team when you return.  A summation of where the technology is heading and what your company might be able to use in that future helps you recall what you learned, spreads the wealth a little bit, and reminds your boss why he, or she, paid for it.