I spent the first half of my career building software as an individual. Programming seemed a solo sport. I was content with sitting in a cube or office by myself, head down and focused on my problem. Today, it seems silly to view the average software development project as anything but a team effort, yet countless development shops still believe the solution is to improve how we work alone.
Continue reading
Retrospectives are an integral part of every project we undertake, and described as a key ceremony in scrum lifecycle. Though agile teams may be doing retrospectives as a part of their project lifecycle, but there are a few common mistakes we may be making which prevent us from obtaining the maximum benefits of this practice.
Continue reading
When people start to change their questions and measurements, they often change their culture. Agile approaches change the culture of the project and organization. Here is how testers can change the conversation from being a “support” part of the organization to helping people see how to change the culture.
Continue reading
What do you do when you need to test the performance of an asynchronous application? What if the application is not easily observable in a standard input/output or request/response interaction? Performance testing asynchronous applications can be tricky, but it’s not impossible. You just need to change the way you think about monitoring application behavior.
Continue reading
I consider my adoption of TDD to be perhaps the most influential moment in my career of writing code. The practice provides so many benefits. Recently, though, I’ve realized that these benefits don’t just apply to writing code. They apply to everything I do professionally. And so today I’d like to share some of those lessons.
Continue reading
Today I’m going to talk about mistakes that developers often make when writing unit tests. You’ll typically see these so-called sins of unit testing when people are first start unit testing. But if they’re not careful, it’s more than just a temporary growing pain. These problematic tests become baked in to the codebase and stick around for the long haul. Let’s look at what to avoid
Continue reading
Many people confuse the purpose of a vulnerability assessment and a penetration test. They are really different activities – each one with a specific set of goals. In this article, we’ll describe each activity and give some real examples of how pen tests and vulnerability assessments can be used correctly to provide the greatest value.
Continue reading
When I was working on a project several years ago, the development team was making a case for addressing technical debt. Most conversations I hear about technical debt are framed around the affect they have on software development. I’d like to make some framing around how technical debt affects testing, quality, and delivery.
Continue reading
The terms “confidentiality” and “privacy” are often used interchangeably, but they actually represent completely different topics. In this article, we’ll explain what each one is, how they differ, and some ways to ensure confidentiality and privacy in your environments.
Continue reading
“Love” is a strong word. I’m not sure I really love test-driven development (TDD). But I do love solving problems by programming and crafting simple, elegant code. I continue using test-driven development because it gives me more opportunities to do the things I love (deliver clean software solutions), and because it reduces baldness-inducing software development pains (defects and unnecessary complexity).
Continue reading