Blog posts in the queue to write

blog_queue.markdown

• Expressing intentions in unit tests: introduction
• Expressing intentions in unit tests: pronouns
• Expressing intentions in unit tests: test organization
• Changing old habits: service location
• Changing old habits: command and query abstractions
• Changing old habits: abstract base classes for abstractions
• Changing old habits: testable object pattern
• ASP.NET MVC security: <location> and handlers (the ELMAH incident)
• ASP.NET MVC security: over-binding (or mass assignment, if you prefer)
• Building a proper HTTP ASP.NET MVC app, part 1: the URLs
• Building a proper HTTP ASP.NET MVC app, part 2: where do forms fit?
• Building a proper HTTP ASP.NET MVC app, part 3: simple content negotiation for what matters
• NoQA: An introduction
• Why NoQA: good testers are harder to find than good developers
• Why NoQA: context is expensive
• Why NoQA: craftsmanship and ownership
• YesQA fallacies: developers don't make good testers
• YesQA fallacies: developers don't like testing
• YesQA fallacies: developers can't be trusted
• YesQA fallacies: QA must be separate gatekeepers
• YesQA fallacies: legal and compliance
• YesQA fallacies: domain knowledge and special testing
• NoQA in action: context-driven testing
• NoQA in action: developer ET
• NoQA in action: automation, in three parts
• NoQA in action: pair testing
• NoQA in action: end-game
• A pure MSBuild alternative to NuGet's package restore
• A summary of lessons learned after spending three years as a tester