{"id":146,"date":"2014-02-02T15:13:20","date_gmt":"2014-02-02T15:13:20","guid":{"rendered":"http:\/\/www.eversholt.org.uk\/blog\/?p=146"},"modified":"2014-02-02T15:13:20","modified_gmt":"2014-02-02T15:13:20","slug":"using-the-right-words","status":"publish","type":"post","link":"https:\/\/www.eversholt.org.uk\/blog\/using-the-right-words\/","title":{"rendered":"Using the right words."},"content":{"rendered":"<h2>Problem &#8211; Error &#8211; Report<\/h2>\n<p>The field broken things is fully of confusing terminology. When I say something, it means precisely what I mean it to say, so here are some definitions of terms. Keep these straight and you&#8217;ll be half-way there.<\/p>\n<div style=\"clear: both; border-top: 1px solid #bbb;\"><\/div>\n<p>I use the word <strong>problem<\/strong> here to mean, &#8220;The cause that made the system produce errors.&#8221;<\/p>\n<h2>A Problem could be<\/h2>\n<ul>\n<li>A Fault<br \/>\nSomething that is broken or worn out, that is repaired by replacing the broken part<\/li>\n<li>An out-of-calibration event<br \/>\nSomething that is repaired by making an adjustment (like putting more air in a tyre if the pressure is low)<\/li>\n<li>A design flaw<br \/>\nSomething that is fixed by changing the design<\/li>\n<li>An upset<br \/>\nSomething that goes wrong, but isn&#8217;t evidence that the system is breaking down. The cosmic-ray-induced soft errors in computer memory are an example of an upset. Provided they don&#8217;t happen too often, we just learn to live with them.<\/li>\n<li>and other stuff<\/li>\n<\/ul>\n<p>so &#8216;problem&#8217; covers all sorts of causes. We tend to give different names to the causes depending on what action we need to take to make the system work properly. But, all these different sorts of problem share the fact that they cause the system to produce errors rather than working properly.<\/p>\n<div style=\"clear: both; border-top: 1px solid #bbb;\"><\/div>\n<p>I use the word <strong>error<\/strong> here very carefully, too.<\/p>\n<h2>An Error is<\/h2>\n<ul>\n<li>A signal or datum that is wrong.<br \/>\nFor example, low air pressure in the tyres, high temperature in the engine, zero RPM when the engine is supposed to be running.<\/li>\n<\/ul>\n<div style=\"clear: both; border-top: 1px solid #bbb;\"><\/div>\n<p>An error is internal to the system. It might propagate within the system and cause more errors. For example, low tyre pressure might cause tyre overheating. However, we won&#8217;t notice anything is wrong (we&#8217;ll be under the misapprehension that the system is working properly) until the error is detected by some error detector and produces a <strong>report<\/strong>.<\/p>\n<h2>A Report is<\/h2>\n<ul>\n<li>The output of an error detector that says &#8220;There&#8217;s an error!&#8221;<br \/>\nFor example, the warning light that tells that the engine is overheating<\/li>\n<li>The result of a specific test<br \/>\nFor example, when you measure the tyre pressure and find it is low<\/li>\n<li>Some human error detector<br \/>\nFor example, you notice the smell of burning rubber.<\/li>\n<li>Anything else that causes the procedure of diagnosis and repair to start.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Problem &#8211; Error &#8211; Report The field broken things is fully of confusing terminology. When I say something, it means precisely what I mean it to say, so here are some definitions of terms. Keep these straight and you&#8217;ll be half-way there. I use the word problem here to mean, &#8220;The cause that made the [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-146","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/posts\/146","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/comments?post=146"}],"version-history":[{"count":7,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/posts\/146\/revisions"}],"predecessor-version":[{"id":153,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/posts\/146\/revisions\/153"}],"wp:attachment":[{"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/media?parent=146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/categories?post=146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.eversholt.org.uk\/blog\/wp-json\/wp\/v2\/tags?post=146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}