~ Code quality ~

Code Virtues

People can have virtues. So can code. In general, for better code, you maximize virtues and minimize smells

Code Coverage Is Not Enough

As leader of a Software Quality team, part of my job is to measure and report on code coverage. The thing is, code coverage, by itself, isn’t enough to prove correctness and provide confidence. But it is something that helps you along the way.

Safety Nets and Guardrails

You might thing Safety Nets and Guardrails are the same thing, but they’re not. They both make things safer, but how and when they work are very different.

Test Classification

Tests come in many different flavors, and which flavor you want depends on what you’re trying to validate with the test.

10 Commandments of Code Review

Code reviews are part of almost all development workflows. How you write them, read them, and respond to them says a lot about a team’s culture. It’s also a way to adjust a team’s culture. How you use them is up to you.

Review Your Own Code Review

Don’t just review it, review it BEFORE you show it to anyone. It’s good for you, it’s good for them, and it’s good for your code.

Demands ...

Providing customer value is what we’re all here for. Unfortunately, it’s not the only thing we end up doing because of demands on our time.

Code Coverage Is NOT useless

Clickbait titles aside, how you use your signals is important. Not just for measuring code coverage.

High Quality Quality

When you say you want quality software, what are you really asking for, and how can you get it?

Readability vs Idioms

Just what is readability anyway?

Hey, That's Pretty Clever

That’s pretty clever, so fix it.

Applesauce, Names, and Refactoring

Naming is important. Even if it’s applesauce

TDD Anti-patterns

Some kinds of tests you just don’t want to write

TAD vs. TDD

There is a difference between testing before and after coding

Lint Filters And Testing

Tests are like cleaning the lint filter on your dryer

Where do defects come from?

Is it someone’s fault, the system’s fault, or a balance of both?

Why We Test

The purpose of testing is to increase confidence for stakeholders through evidence.