<?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: How does the user language fit in with the ubiquitous language?</title>
	<atom:link href="http://www.markhneedham.com/blog/2009/01/10/how-does-the-user-language-fit-in-with-the-ubiquitous-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markhneedham.com/blog/2009/01/10/how-does-the-user-language-fit-in-with-the-ubiquitous-language/</link>
	<description>Thoughts on Software Development</description>
	<lastBuildDate>Sat, 11 Feb 2012 23:17:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Phillip Calçado</title>
		<link>http://www.markhneedham.com/blog/2009/01/10/how-does-the-user-language-fit-in-with-the-ubiquitous-language/comment-page-1/#comment-2667</link>
		<dc:creator>Phillip Calçado</dc:creator>
		<pubDate>Sun, 11 Jan 2009 10:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=838#comment-2667</guid>
		<description>The translation will always happen unless you have a single domain (thus a single Ubiquitous Language). 

I think you probably have to face the fact that this is necessary and not try to escape from it. Create Bounded Contexts for you two Domains and define a Context Map. Wrap everything with integration tests and you&#039;re good.</description>
		<content:encoded><![CDATA[<p>The translation will always happen unless you have a single domain (thus a single Ubiquitous Language). </p>
<p>I think you probably have to face the fact that this is necessary and not try to escape from it. Create Bounded Contexts for you two Domains and define a Context Map. Wrap everything with integration tests and you&#8217;re good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Marick</title>
		<link>http://www.markhneedham.com/blog/2009/01/10/how-does-the-user-language-fit-in-with-the-ubiquitous-language/comment-page-1/#comment-2660</link>
		<dc:creator>Brian Marick</dc:creator>
		<pubDate>Sun, 11 Jan 2009 02:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.markhneedham.com/blog/?p=838#comment-2660</guid>
		<description>There&#039;s been some research in science studies about &quot;boundary objects&quot; as a way of aligning different communities toward common goals. I wrote a summary here: http://visibleworkings.com/analogyfest/marick-boundary-objects.pdf

A related idea is Fujimura&#039;s &quot;packages&quot; (paper in _Science as Practice and Culture_) and Galison&#039;s &quot;trading zones&quot; (in _Image and Logic_).

I like boundary objects and packages because they&#039;re not purely linguistic - there are also things involved, so they are closer to software (which is a linguistic construct, in a way, but related to as a thing). 

I&#039;ve wanted to dig into these ideas more, but other things keep getting in the way.</description>
		<content:encoded><![CDATA[<p>There&#8217;s been some research in science studies about &#8220;boundary objects&#8221; as a way of aligning different communities toward common goals. I wrote a summary here: <a href="http://visibleworkings.com/analogyfest/marick-boundary-objects.pdf" rel="nofollow">http://visibleworkings.com/analogyfest/marick-boundary-objects.pdf</a></p>
<p>A related idea is Fujimura&#8217;s &#8220;packages&#8221; (paper in _Science as Practice and Culture_) and Galison&#8217;s &#8220;trading zones&#8221; (in _Image and Logic_).</p>
<p>I like boundary objects and packages because they&#8217;re not purely linguistic &#8211; there are also things involved, so they are closer to software (which is a linguistic construct, in a way, but related to as a thing). </p>
<p>I&#8217;ve wanted to dig into these ideas more, but other things keep getting in the way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

