<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on the Pirate Baby</title><link>http://pirate.baby/tags/software/</link><description>Recent content in Software on the Pirate Baby</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 23 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://pirate.baby/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Of Ducks, Types, and Identity</title><link>http://pirate.baby/posts/dreaming_of_a_dynamcially_typed_world/</link><pubDate>Wed, 23 Oct 2024 00:00:00 +0000</pubDate><guid>http://pirate.baby/posts/dreaming_of_a_dynamcially_typed_world/</guid><description>&lt;figure>
&lt;img src="http://pirate.baby/images/duck_typing.png"/>
&lt;figcaption>A Duck, Typing&lt;/figcaption>
&lt;/figure>
&lt;p>In 1967 computer scientist Melvin Conway made an observation that came to be known as &lt;em>Conway&amp;rsquo;s Law&lt;/em>.&lt;/p>
&lt;blockquote>
&lt;p>Organizations which design systems (in the broad sense used here) are constrained to produce designs which are copies of the communication structures of these organizations.&lt;/p>
&lt;/blockquote>
&lt;p>Conway&amp;rsquo;s Law is why you often find rigid, silo&amp;rsquo;ed tables modeled into the data architecture of rigid companies with silo&amp;rsquo;ed business departments, or scrambled and unplanned relationships across software entities at bootstrap startups; code reflects the human environment in which it is developed.&lt;/p></description></item></channel></rss>