<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Names Matter	</title>
	<atom:link href="https://www.salvis.com/blog/2020/06/21/names-matter/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.salvis.com/blog/2020/06/21/names-matter/</link>
	<description>Database-centric development</description>
	<lastBuildDate>Wed, 08 Nov 2023 11:11:24 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.1</generator>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/>
<atom:link rel="hub" href="https://websubhub.com/hub"/>
<atom:link rel="self" href="https://www.salvis.com/blog/2020/06/21/names-matter/feed/"/>
	<item>
		<title>
		By: Philipp Salvisberg		</title>
		<link>https://www.salvis.com/blog/2020/06/21/names-matter/#comment-29233</link>

		<dc:creator><![CDATA[Philipp Salvisberg]]></dc:creator>
		<pubDate>Sat, 03 Oct 2020 10:38:17 +0000</pubDate>
		<guid isPermaLink="false">https://www.salvis.com/blog/?p=9890#comment-29233</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.salvis.com/blog/2020/06/21/names-matter/#comment-29108&quot;&gt;Michael Milligan&lt;/a&gt;.

Many thanks for your positive feedback. 

Regarding endianness. I like the relation to Gulliver&#039;s Travels and the fact that the Lilliputians are called Little-Endians because they open a boiled egg on the little end. I see no problem in continuing to use the terms little-endian, big-endian or bi-endian. They are well defined and not discriminating IMO.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.salvis.com/blog/2020/06/21/names-matter/#comment-29108">Michael Milligan</a>.</p>
<p>Many thanks for your positive feedback. </p>
<p>Regarding endianness. I like the relation to Gulliver&#8217;s Travels and the fact that the Lilliputians are called Little-Endians because they open a boiled egg on the little end. I see no problem in continuing to use the terms little-endian, big-endian or bi-endian. They are well defined and not discriminating IMO.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael Milligan		</title>
		<link>https://www.salvis.com/blog/2020/06/21/names-matter/#comment-29108</link>

		<dc:creator><![CDATA[Michael Milligan]]></dc:creator>
		<pubDate>Fri, 02 Oct 2020 15:06:56 +0000</pubDate>
		<guid isPermaLink="false">https://www.salvis.com/blog/?p=9890#comment-29108</guid>

					<description><![CDATA[Thank you for this excellent, thoughtful article.

Being raised by conservative parents who nonetheless taught us - emphatically - that &quot;words can hurt&quot;, I have always paid attention to ontology. Your new terms have another major advantage: clarity. The terms themselves either encompass the definition or, at the very least, indicate their meaning directly rather than euphamistically.

An example of a self-defining term is &quot;exclusion list&quot;. It could not be any clearer.

An example of a term with a direct meaning is &quot;agent&quot;. Why use a euphamism, when a word whose meaning is commonly understand exists? The use of euphamisms requires all to know both it and the context of its use.

One further suggestion for the industry: let&#039;s stop using the terms &quot;big endian&quot; and &quot;little endian&quot;. No doubt these were coined as memory mnemonics, but their use is and always was in poor taste, not to mention too cute by half. The terms &quot;big ending&quot; and &quot;little ending&quot; work just fine for me.

Thanks again,

Michael Milligan
Layton, Utah]]></description>
			<content:encoded><![CDATA[<p>Thank you for this excellent, thoughtful article.</p>
<p>Being raised by conservative parents who nonetheless taught us &#8211; emphatically &#8211; that &#8220;words can hurt&#8221;, I have always paid attention to ontology. Your new terms have another major advantage: clarity. The terms themselves either encompass the definition or, at the very least, indicate their meaning directly rather than euphamistically.</p>
<p>An example of a self-defining term is &#8220;exclusion list&#8221;. It could not be any clearer.</p>
<p>An example of a term with a direct meaning is &#8220;agent&#8221;. Why use a euphamism, when a word whose meaning is commonly understand exists? The use of euphamisms requires all to know both it and the context of its use.</p>
<p>One further suggestion for the industry: let&#8217;s stop using the terms &#8220;big endian&#8221; and &#8220;little endian&#8221;. No doubt these were coined as memory mnemonics, but their use is and always was in poor taste, not to mention too cute by half. The terms &#8220;big ending&#8221; and &#8220;little ending&#8221; work just fine for me.</p>
<p>Thanks again,</p>
<p>Michael Milligan<br />
Layton, Utah</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
