delicious

Testing, at it's very core, for me, is about ensuring correctness. Whether you're testing using an automated testing framework such as NUnit, MbUnit, or xUnit or you test by hitting F5 and running your project, you're seeking correctness.

Care about what you do.

Another CODE REDUCER! "Simplifying the Complex - For some reason I find it really satisfying to reduce the number of lines of code in a project by rigorously applying the DRY principle and then making it infinitely more readable through refactoring and using thoughtful naming conventions. I also love reducing the number of clicks that a user is required to make in the user interface."

In other words, how is it that I can interview two candidates with the exact same number of years of experience and an almost identical list of buzzwords on their resumes, yet there is still an order of magnitude difference between them in terms of the overall value they bring to an organization? I believe the gap exists because there are a number of knowledge and experience ‘multipliers’ that some people utilize and others don’t.

"I don't need to test that, I know they work." - you, me, everyone (at one point in time) :) Why its a Folly: A few questions in regards to this should set us up nicely ... Why are you even trying to perform testing of any kind if you're not testing even the basic stuff? This is the REAL SIMPLE stuff that should not be ignored. Seriously, If you write code and you KNOW its solid, then why write tests for it if your so confident? Think about that... That doesn't make sense! WE'RE ALL HUMAN, WE ALL MAKE MISTAKES. That's why. No one's code is perfect. I don't care who you are. Also, what happens after you check in your code and then tomorrow Developer X checks out the code, makes a change to a setter and then checks it back in. How do you know if that did or did not break anything? YOU DON'T.

Wow "One of the questions he asked is: when is a feature done? This is a perennial topic with Agilists and it's a very valid question; how do we know when a feature is 'potentially shippable?' I piped up with my answer: a story is done when it's in production use. That was a little different than the answers from the others in the room."