<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;AkMASHY4eSp7ImA9WhRRFE4.&quot;"><id>tag:blogger.com,1999:blog-17776550</id><updated>2011-11-28T02:00:49.831+02:00</updated><title>Infosmid</title><subtitle type="html">Ramblings about Software Architecture, Design and Programming.</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://infosmid.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://infosmid.blogspot.com/" /><author><name>Corneil</name><uri>http://www.blogger.com/profile/02929392099486168526</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>3</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/Infosmid" /><feedburner:info uri="infosmid" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;CUICQHo_fyp7ImA9WxFaFEU.&quot;"><id>tag:blogger.com,1999:blog-17776550.post-6833427969967661281</id><published>2010-07-18T22:04:00.000+02:00</published><updated>2010-07-18T22:06:01.447+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-18T22:06:01.447+02:00</app:edited><title>Why should you sign the Oath of Non-Allegiance</title><link rel="replies" type="application/atom+xml" href="http://infosmid.blogspot.com/feeds/6833427969967661281/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=17776550&amp;postID=6833427969967661281" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/6833427969967661281?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/6833427969967661281?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Infosmid/~3/0x68xeNgyco/why-should-you-sign-oath-of-non.html" title="Why should you sign the Oath of Non-Allegiance" /><author><name>Corneil</name><uri>http://www.blogger.com/profile/02929392099486168526</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Alistair Cockburn has once again found a meaningful way to bring clarity to the software development lifecycle.
Read about the Oath of Non-Allegiance
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/GvhrsgPeJhPQBQCA0ahZs3qo4CM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GvhrsgPeJhPQBQCA0ahZs3qo4CM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/GvhrsgPeJhPQBQCA0ahZs3qo4CM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/GvhrsgPeJhPQBQCA0ahZs3qo4CM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Infosmid/~4/0x68xeNgyco" height="1" width="1"/&gt;</content><feedburner:origLink>http://infosmid.blogspot.com/2010/07/why-should-you-sign-oath-of-non.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0IERXk8eCp7ImA9WBJSFUg.&quot;"><id>tag:blogger.com,1999:blog-17776550.post-113660633429290088</id><published>2006-01-07T05:35:00.000+02:00</published><updated>2006-03-05T11:38:24.770+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-03-05T11:38:24.770+02:00</app:edited><title>Values in Design: Reduce Complexity</title><link rel="replies" type="application/atom+xml" href="http://infosmid.blogspot.com/feeds/113660633429290088/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=17776550&amp;postID=113660633429290088" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/113660633429290088?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/113660633429290088?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Infosmid/~3/4DgRZ1r_hvY/values-in-design-reduce-complexity.html" title="Values in Design: Reduce Complexity" /><author><name>Corneil</name><uri>http://www.blogger.com/profile/02929392099486168526</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">Why is software development so difficult? Why does software tend to become complex?

Seemingly clever humans revel in complexity. How do you reduce complexity? You need to measure the complexity and then make appropriate changes that will reduce the complexity. Then you measure again to verify the results.

Do we need measurements that are seemingly artificial and contrived? Yes we need all the 
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/LHXPDd-qUtDQ--oNhzoXO-ShgmM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/LHXPDd-qUtDQ--oNhzoXO-ShgmM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/LHXPDd-qUtDQ--oNhzoXO-ShgmM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/LHXPDd-qUtDQ--oNhzoXO-ShgmM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Infosmid/~4/4DgRZ1r_hvY" height="1" width="1"/&gt;</content><feedburner:origLink>http://infosmid.blogspot.com/2006/01/values-in-design-reduce-complexity.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CU4EQHc5fip7ImA9WBVVFEQ.&quot;"><id>tag:blogger.com,1999:blog-17776550.post-113649351463751863</id><published>2006-01-05T22:35:00.000+02:00</published><updated>2006-01-05T22:45:01.926+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2006-01-05T22:45:01.926+02:00</app:edited><title>Values in Design: Flexible Service not Flexible Interface</title><link rel="replies" type="application/atom+xml" href="http://infosmid.blogspot.com/feeds/113649351463751863/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=17776550&amp;postID=113649351463751863" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/113649351463751863?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/17776550/posts/default/113649351463751863?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/Infosmid/~3/UAoWjsyHUDU/values-in-design-flexible-service-not.html" title="Values in Design: Flexible Service not Flexible Interface" /><author><name>Corneil</name><uri>http://www.blogger.com/profile/02929392099486168526</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><content type="html">What values are important to you when designing a Service and an Interface? A lot has been written about the design of services. I would like to touch on why you design an interface and the values that I feel is important.   What am I talking about when I refer to an interface? I am referring mostly to an interface that may be exposed by a service. I will use a web-service as an example. When you
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/_1SB7tAXjImYOzhJRYQYl8xbS-M/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_1SB7tAXjImYOzhJRYQYl8xbS-M/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/_1SB7tAXjImYOzhJRYQYl8xbS-M/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/_1SB7tAXjImYOzhJRYQYl8xbS-M/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/Infosmid/~4/UAoWjsyHUDU" height="1" width="1"/&gt;</content><feedburner:origLink>http://infosmid.blogspot.com/2006/01/values-in-design-flexible-service-not.html</feedburner:origLink></entry></feed>

