procedures:warning
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| procedures:warning [2025/03/01 19:14] – ultracomfy | procedures:warning [2025/04/09 17:50] (current) – ultracomfy | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~Title: | ||
| <WRAP center centeralign> | <WRAP center centeralign> | ||
| <fs xx-large> | <fs xx-large> | ||
| Line 10: | Line 11: | ||
| At the same time, a warning //can// always occur in a context that is " | At the same time, a warning //can// always occur in a context that is " | ||
| - | In either case, the goal with issuing an S2-Warn is to communicate that a problem is identified and that I believe it has the potential to cause problems in the future. Ideally the first warning I issue is always //casual// with the goal of raising awareness, whereas subsequent warning are meant to add emphasis and communicate escalating severity. The level of severity will typically be communicated in [[qualifier|qualifiers]]. | + | In either case, the goal with issuing an S2-Warn is to communicate that a problem is identified and that I believe it has the potential to cause problems in the future. |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 22: | Line 23: | ||
| ---- | ---- | ||
| - | See also: [[Notice|Notice]], | + | See also: [[Notice|Notice]], [[Repeated Warning]], [[Final|Final]], |
| [[: | [[: | ||
procedures/warning.1740856484.txt.gz · Last modified: by ultracomfy
