Python

It pushes TDD hard (tests before implementation), enforces type safety with Pydantic validation at every boundary, and defaults to async patterns with proper connection pooling. The split structure puts CVE research and OWASP implementations in separate reference files, which keeps the main skill focused on patterns you'll actually use: parameterized queries, pathlib for file operations, never shell=True with user input. If you're building anything that touches authentication, databases, or user files in Python, the decision framework alone (which operation requires which safety measure) is worth having in context.