> The main difference therefore between error and warning is, "We didn't think this could happen" vs "We thought this might happen".

What about conditions like "we absolutely knew this would happen regularly, but it's something that prevents the completion of the entire process which is absolutely critical to the organization"

The notion of an "error" is very context dependent. We usually use it to mean "can not proceed with action that is required for the successful completion of this task"

▲

wizzwizz4 2 days ago | parent [-]

Those conditions would be "Critical", no? The error vs warning distinction doesn't apply.

▲

fhcuvyxu a day ago | parent [-]

No, many applications need to be fault tolerant.

Crashing your web stack because one route hit an error is a dumb idea.

And no, calling it a warning is also dumb idea. It is an error.

This article is a navel gazing expedition.

They're kind of right but you can turn any warning into an error and vice versa depending on business needs that outweigh the technical categorisation.

▲

wizzwizz4 15 hours ago | parent [-]

A log entry marked "CRITICAL" does not imply crashing the web stack.

	▲	fhcuvyxu 9 hours ago \| parent [-]
		Right. Was thinking of fatal.