Code Camp 7 - my session overviews

Here are my session descriptions (the code camp site doesn't seem to show me the appropriate link to add this officially right now - i'll try again later).

Disassembling .Net
Have you ever used ILDasm? Did you understand the information and why it was displayed the way it was? Ever wonder what some of the stuff meant? If so, you will probably find this session interesting and maybe even useful.

This will be an in depth look at disassembling a .Net assembly and making sense of its raw contents using mostly ILDasm and a hex editor.

This talk has three sections: in depth look at a .Net assembly's file format (and metadata structure), the IL code included in an assembly and a brief look into some options if you are shipping .Net code (obfuscation).

Reflector and Friends: An overview of Lutz Roeder's .Net Reflector and its add-ins
Do you use Reflector on a daily basis? How about it's addins? Ever wonder how other people use it or want some tips on other things you can do with it? If so, you will probably find this session of some use and maybe even have something to add.

This will be an introduction and overview of Lutz Roeder's .Net Reflector tool and some of the addins the community has developed for it.

There are two sections to this talk: an introduction and overview of the tools and (hopefully) an open discussion of more tips and tricks of the way people use them.

posted on Saturday, February 24, 2007 10:36 AM

Feedback

# re: Code Camp 7 - my session overviews

Jason,

Nice pair of sessions.

As an attendee and possible speaker at 'Deer in Headlights', I would like the community to create an informal set of standards for speakers. Doing so will increase the effectiveness of the sessions.

Here are some suggestions for speakers:

1. Make sure that your slides can be read from the back row by someone with 20/40 vision. Guy Kawasaki writes "Force yourself to use no font smaller than thirty points." This rule also applies to live demos. Since there are few applications that scale gracefully when the font is enlarged, creating an effective demo typically requires extensive preparation.

2. Create a backup in case a live demo fails. Don't debug a failing demo in real time -- it won't work and the audience (and your credibility) will suffer. Instead, have a backup presentation with screenshots and talk through the slides.

3. Work on creating smooth transitions between speakers. Swapping a laptop can easily take five minutes. Should there be a five minute break after each session?

4. Share your contact information. Carry business cards and hand them out to everyone at your session. Put all of your contact information in your presentations.

This is just a start. What else can we add?
2/26/2007 11:16 AM | Michael

# re: Code Camp 7 - my session overviews

Michael,

Nice ideas. When it comes to presenting I usually checkout what Scott Hanselman has to say. He is one guy that really seems to pay attention to the details you are speaking of.
2/26/2007 8:15 PM | Jason Haley

# NE Code Camp 7 - Rest easy. Your reservation is confirmed.

I loved the subject line of my reservation confirmation from the Waltham Westin. "Rest easy. Your reservation
3/3/2007 10:33 PM | Dave Burke

# NE Code Camp 7 - Rest easy. Your reservation is confirmed.

I loved the subject line of my reservation confirmation from the Waltham Westin. "Rest easy. Your reservation
3/3/2007 10:36 PM | Dave Burke Everyday Blog

Post Comment

Title  
Name  
Url
Comment   
Please enter the following code into the box below to stop spammers

  
Enter Code Here *