Guard Every Bullet

validation and retries

Part of: Resume Bullet Booster

You now have three separate rules: strong opener, has a number, within the word limit. Scattered across your code they're easy to forget. This lesson pulls them into one validator that checks every rule at once and, when a bullet fails, tells your tool exactly what to fix. It also handles the edge case everyone forgets, empty input. One function, all the rules A validator returns the list of things wrong with a bullet. Empty list means it passed. Notice the order: EMPTY short-circuits . An empty bullet isn't weak or long, it's nothing, and every other check would just add noise. Return early, then collect the rest in a fixed order so the output is predictable. Turning failures into a retry The validator is what makes the "prompt for quality, verify for reliability" loop real. When a bullet fails, you call the model again and tell it why it failed, so the retry is better than a blind redo: Feeding the failure codes back is the trick. "You started weak and used no numbers" gives the model a concrete correction, so attempt two usually lands. Cap the tries so a stubborn task can't loop forever and burn money, then return the best you got and flag it. Why empty input matters most The em

Challenge: The Bullet Validator