A course about moving the catch left into the editor, for a developer whose commit volume rose faster than anybody's capacity to review it. It starts with the split that decides everything: the editor's job is prevention, the pull request's is judgement, the pipeline's is assurance, and a check put in the wrong one gets disabled within a month. It then works through the latency budget that decides whether a check survives contact with a developer at all, the small set of checks that genuinely earn a local slot (secret detection before the commit exists, dependency checks at the moment a package is added, and pattern checks with a real precision floor), and the false positive economics that turn one noisy rule into a disabled extension and take the useful checks with it. The back half is the human side: designing the message a developer sees, deciding what is shown and what is routed elsewhere without interrupting them, blocking against warning, commit hooks, rollout across machines you do not control, keeping the editor consistent with the pull request and the pipeline, and the honest limit, which is that an editor check cannot see the whole system and must never be sold as though it can.
Nothing. Every course, exam, and certificate on the catalog is free — including retakes. All you need is a free Safeguard account.
None. The flagship course, Safeguard Certified Practitioner, is a beginner-level course — basic familiarity with how software is built helps, but every exam question is answerable from the lessons themselves.
You can retake it after a 24-hour cooldown, as many times as you need. Retakes are free, and each attempt draws a fresh random set of questions.
The Safeguard Certified Practitioner credential is valid for 24 months from issue. The expiry date is printed on the certificate and shown live on its public verification page. Renewing means passing the current exam again.
