Unit Testing has settled into the mainstream. As developers, we write code that checks code, ensuring that the outcome matches some expected result. But, are we really? As end-users (which includes each one of us from time to time), when we ask a question, we don't just expect our answer to be right, we expect it to be right now. So as developers, why are we only validating for accuracy? Why aren't we going for speed? During this session we'll discuss meeting the performance needs of an application, including developing a performance specification, measuring application performance from stand-alone testing through unit testing, using tools ranging from Team Foundation Server to the command line, and asserting on these measurements to ensure that all expectations are met. Your application does "right." Let's focus on "right now."

You will undoubtedly have to give a presentation in your career. If it hasn't happened yet, it will. Maybe the Sales Department needs a technical resource to give a demo for that new software. Maybe you are doing the selling as you try to convince your boss to approve that awesome development productivity tool. Maybe you want to get into speaking, presenting the latest technology trends to your peers. Yet, everybody has been there: a presentation where you spend so much time reading the content from a slide that you ignore the content from the speaker. Perhaps it was a presentation where the deck was full of animated transitions right out of a 1970's made-for-TV movie. Maybe it was the slideshow that was there simply because the presenter felt obligated to have one. The quality of a slide deck can have as much impact on a presentation as the quality of the speaker. It can destroy. It can invigorate. It can shape the mood of your audience and bend it at will. Harness that power; use it to your advantage to tell your story and leave your audience inspired.