This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Article discussion edit

Unintuitive name, perhaps backwards edit

Latest comment: 25 days ago1 comment1 person in discussion

Is "failure transparency" a term of art? The name seems backwards. The article suggests that "high failure transparency" is achieved when the user does not know that a failure occurred and the failure is opaquely solved by a complex work-around. Nothing about that scenario sounds "transparent". Additionally, from a developer/operations perspective, "transparency" would refer to knowing when, where, why a failure occurred, whether it was solved or not. "Opacity" would refer to NOT knowing that a failure occured or not knowing when, where, or why failure occurred. Alexgenaud (talk) 10:03, 9 May 2024 (UTC)Reply

Add topic

Talk:Failure transparency

Article discussion edit

Unintuitive name, perhaps backwards edit