How to be a security person who doesn't get in the way

Security people have a reputation for being the ones who show up late and say no. This piece from Frankly Speaking walks through what it actually looks like to do the job well — without becoming a roadblock.

The key insight is simple: the best security folks write rules in plain English, not in jargon. They build things, not just review pull requests. They understand the product before they start talking about threats. And they communicate in ways the rest of the team can actually use.

The article covers the practical stuff — how to pick your battles, when to say no, and when to just let it go. Security isn't about catching every flaw. It's about catching the ones that would actually hurt. That means knowing what the team is building and what it needs, not just what the framework says.

It's the kind of writing that helps anyone on a product team — not just the security specialists. The advice lands because it's grounded in real experience, not theory.

Why this matters for us: security bloat hurts the people building things, and learning to spot the good security folks saves everyone time and headaches.