The first stated value of the Manifesto for Software Craftsmanship is: "Not only working software, but also well-crafted software" Well-crafted software is often spoken in terms of the audience of other coders, who read, modify, and consume the code of the software. The focus of developers usually consis on the blocks on code through unit tests, not the overall application. The other key audience is the consumer of the software. The consumer of the software has their focus on the overall performance and lack of bugs on an application. Too often the performance tests of the application is left to QA teams. Here I would like to talk about: Developers role in quality with Unit Tests Developers role in performance profiling and testing. What is performance profiling? Why do we need to do it? How do we profile our performance for applications? Tools for performance monitoring Gathering performance data. Benchmarking Performance Tuning