We want actionable error messages. Passive voice erodes their usefulness.
For example, “Failures were made somewhere in your CI pipeline” — passive, confusing, vague.
Instead, replace it with “Jenkywenkins made a whoopsie!” — clear, direct, active.
Discussion
nostr:npub1unvr9ua946fwwt7w7sk5r5w5kvaswxalakwl862srzy0x5zduw3qfxcwrs Same goes for documentation.
Don't say: Event will be logged.
Say: Logjob does timeywhimey things with event.