Real Men Test in Production

What does “real men test in production” mean?

“Real men test in production” is a tongue-in-cheek phrase used by developers to describe the reckless practice of deploying code without properly testing it first.

The joke suggests that staging environments, automated tests, and quality assurance are unnecessary. Instead, you launch the update immediately and let real users discover the bugs for you.

This is obviously not recommended. Testing in production can lead to broken functionality, lost data, security vulnerabilities, and some very uncomfortable Slack messages.

At Overflow, we have Jort: our developer and the man who always tests in production.

Not because it is best practice, of course. He simply believes every deployment deserves a live audience.

Fortunately, Jort usually knows what he is doing. Usually.

Should you test in production?

Some testing in production is both normal and valuable. Monitoring, feature flags, canary releases, and controlled experiments help teams understand how software behaves under real-world conditions.

The important distinction is control. Professional teams test carefully in production after completing their regular checks—not instead of completing them.

So, do real men test in production?

Sometimes. But real professionals make sure they can roll it back.