blog.fossmo.net

Last month Kjetil and I where speakers at the MSDN Live tour in Norway. We held presentations in Stavanger, Bergen, Trondheim and Oslo. After this tour I learned something about doing a technical presentation for developers. I want to share my experience from this tour. I have gathered nine points with experience:

1) Use a lot of code in the presentation.
We did a big mistake in the first presentation in Stavanger. We didn’t show much code. I guess when a developer goes to a event like this, (s)he wants to see code, preferably live code in Visual Studio. We increased our ratings when we added more code to the second presentation in Bergen.

2) Know the stuff your presenting so well that you are dreaming about it! 
Developers want to be impressed when going to a presentation. There is no room for errors!

3) Use pictures and make the slides sexy
Design sells, just ask Apple. Spend some time to polish the slides. Use pictures to underline what you are talking about. You probably know the old saying; “Pictures tells more than thousand words”.

4) Don’t use to many slides.
People may go into a “PowerPoint coma” and you don’t want that.

5) Show that you are enthusiastic about the stuff you are presenting.
There is nothing more inspiring than to watch a person that is enthusiastic about the stuff (s)he is presenting. It rubs of to the audience.

6) Talk about something you have worked with.
The audience will more likely believe in what you are saying if you talk about something you have worked with and have real life experience with.

7) Think twice before doing a presentation together with another person 
You would probably think that being two persons working on the presentation will make the preparation go faster. Well it won’t. It’s much harder to be two persons working on a presentation. It’s a lot of decisions to be made and it’s easier to argue with yourself than another person. Create the presentation on your own, and then get feedback from other people, but don’t trust every advice you get. Be critical because it’s you who know the thing you're presenting best. The great thing about doing a presentation together with another person is that you are not alone on the stage and feel more safe. We managed to get a good interaction on stage, which the audience appreciated.

8) People may leave and not pay attention during your presentation.
F**k them. Don’t let things like this interfere with your presentation. I have experienced people having a conversation during a presentation I did and it’s quite annoying. It can throw you a bit off so be mentally prepared for this.

9) Make the audience laugh
Most technical presentations are boring by default. Do something to entertain the audience, but don’t make yourself look stupid. Don’t make fun of the thing you are presenting.

Tags: presentation

This last mount I have been around cities in Norway giving a presentation called ‘WPF Done Right’. This is in relation to Microsofts MSDN Live tour where they go to 4 large cities in Norway with presentations about new and upcoming technologies. The presentation I’m giving is about Composite Application Guidance. You may know it as Prism because this was the codename they used when they started developing this guidance. It’s important to distinguish Prism from Composite Application Block. Prism equals freedom. You can do whatever you want with this framework/guidelines. If you want to use something else than what comes out-of-the-box, you can. A god example of this is Unity. Unity is a IOC container made by Microsoft. If you don’t want to use it, you don’t have to. You can switch to Autofact or Windsor. It’s up to you. In CAB you have to follow all the rules that the CAB team have decided. CAB equals not so much freedom.

I’m really excited about this framework and I love working with it. I will definitely write posts about this framework in the future. 
The picture below is from the presentation in Trondheim.

Rune Grothaug at Microsoft took some pictures from the event in Trondheim. You can view them here.

I’m giving this presentation together with Kjetil Klaussen, a friend and colleague from Acando.

Tags: presentation, wpf

This is mostly a note to myself on how to create an attached property in WPF using a ComboBox.

public class SelectionBehavior
{
    public static DependencyProperty SelectionChangedProperty =
            DependencyProperty.RegisterAttached("SelectionChanged",
            typeof(ICommand),
            typeof(SelectionBehavior),
            new UIPropertyMetadata(SelectionBehavior.SelectedItemChanged));
    public static void SetSelectionChanged(DependencyObject target, ICommand value)
    {
        target.SetValue(SelectionBehavior.SelectionChangedProperty, value);
    }
    private static void SelectedItemChanged(DependencyObject target, DependencyPropertyChangedEventArgs e)
    {
        Selector element = target as Selector;
        if (element == null) throw new InvalidOperationException("This behavior can be attached to Selector item only.");
        if ((e.NewValue != null) && (e.OldValue == null))
        {
            element.SelectionChanged += SelectionChanged;
        }
        else if ((e.NewValue == null) && (e.OldValue != null))
        {
            element.SelectionChanged -= SelectionChanged;
        }
    }
    private static void SelectionChanged(object sender, System.Windows.Controls.SelectionChangedEventArgs e)
    {
        UIElement element = (UIElement)sender;
        ICommand command = (ICommand)element.GetValue(SelectionBehavior.SelectionChangedProperty);
        command.Execute(((Selector) sender).SelectedValue);
    }
}

And in the XAML file add

<ComboBox local:SelectionBehavior.SelectionChanged="{Binding MyCommand}"  
              ItemsSource="{Binding MySource}"
              Name="MyComboBox"/> 

MyCommand can be a DelegateCommand from CAG.

Tags: wpf

I can’t wait 62 years for this to finish…I guess it’s time to press the Cancel button ;-)

Tags: