Why You Should Come to DevIntersection

DevIntersection is going to be an awesome conference. It’s right around the corner, so get to work convincing your boss to let you come. Here are just a couple of reasons you should come.

- You get a Windows 8 Tablet. Yep. That’s right, a Windows 8 Tablet! Register by Nov 20 for that!

- It’s in Vegas a week that has traditionally low airfares

- $65 room rates and the MGM Grand, so your overall cost will be relatively low.

- The MGM has just been renovated, so the facilities should be great.

- Richard Campbell is the force behind this show, so you know it will be a bit irreverent, casual and absolutely stuffed full of great information

- There’s an amazing list of speakers

- Look for a fantastic blend of info direct from Microsoft and some of the best independent speakers to go way beyond the Microsoft party line.

- Keynotes by the Scott Guthrie, Steve Fox, and the Visual Studio Team

- It’s your last chance effectively use any leftover training and travel funds in calendar 2012

- Did I mention that everyone who registers by Nov 20 gets a Windows 8 Tablet?

Abstracts for the show are under “Sessions” at DevIntersection . My talks are:

Deeper into Async – I’ll explain async in .NET 4.5 and show techniques to integrate timeouts, cancellation and exceptions into your async apps. (There is a mistake in the heading, in 75 minutes, I will focus on single thread async – this is NOT a multi-thread talk, I’ll work to get this fixed)

Visual Studio 2012 Tips – I’ll show you ways to improve your navigation, editing and searching techniques.

Managed Extensibility Framework in .NET 4.5 – I’m really excited to show you the next version of MEF with resolution of open generics, flexible container creation and inference and improved diagnostics. This will start with an introduction to MEF so it’s definitely not just for MEF geeks.

You should also come to my post conference workshop called Better Coding: Stop Coping, Start Comprehending.

I’m becoming increasingly passionate about people learning or relearning core concepts of the framework. In general, it’s consistent, and if you understand what’s happening under the hood you can predict what it will. You can get your hands on a lot of material on the main libraries. That’s great, but, as I’ve gone around the country doing talks, I see a dropping level of knowledge about the core framework itself – the type system, the languages, the fundamentals of why .NET works the way it does. And I’ve seen this in folks that have been in .NET since the early betas because it’s been a really long time since .NET kicked off.

There’s the basics – we still need to understand nuances of the heap and stack, overloads, evil static constructors, the multiple meanings of equals, attributes and such things. And there are the things that have evolved our thinking about code – generics, lambda expressions, LINQ and Dependency Injection. And there’s the new stuff – async, simpler parallel processing, code info and event sourcing. Whew! It’ pretty overwhelming unless you have a mental model that aligns with the consistency underlying the framework. This day is absolutely stuffed full of information to make you better at writing .NET code.

I teach this with a fun unit test “puzzle” format where the audience collaborating to select from multiple commented assert options. I’ll ask you to think as well as listen, and sometimes you’ll get fellow students explanations as well as mine for the critical question of why something works the way it does. We might do a skit involving throwing Snickers bars, and I’ll integrate Visual Studio tricks, so when I write code for you, I’ll show you some pretty cool things along the way.

I hope you’ll sign up for DevIntersection, get your new Tablet and sign up for my post conference workshop as well!

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>