<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/'><id>tag:blogger.com,1999:blog-13967713.post447151406139320702..comments</id><updated>2011-03-01T14:47:38.902+01:00</updated><category term='AOP'/><category term='tools'/><category term='engineering'/><category term='process'/><category term='HCI'/><category term='quote'/><category term='multithreading'/><category term='UML'/><category term='multicore'/><category term='oop'/><category term='COM'/><category term='poll'/><category term='announce'/><category term='cloud'/><category term='algorithms'/><category term='concurrency'/><category term='profession'/><category term='form'/><category term='ASP.NET'/><category term='GUI'/><category term='C#'/><category term='C++'/><category term='article reference'/><category term='agile'/><category term='NOSD'/><category term='metrics'/><category term='analysis'/><category term='generics'/><category term='free time'/><category term='coding'/><category term='pattern'/><category term='real options'/><category term='windows'/><category term='link'/><category term='design'/><category term='quality'/><category term='modeling'/><category term='book reference'/><category term='project management'/><category term='requirements'/><category term='architecture'/><category term='teaching'/><category term='estimation'/><category term='database'/><category term='.NET'/><category term='thinking'/><category term='language design'/><title type='text'>Comments on Carlo Pescio - blog: Notes on Software Design, Chapter 11: Friction in ...</title><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://www.carlopescio.com/feeds/447151406139320702/comments/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/13967713/447151406139320702/comments/default'/><link rel='alternate' type='text/html' href='http://www.carlopescio.com/2010/10/notes-on-software-design-chapter-11.html'/><author><name>Carlo.Pescio</name><uri>http://www.blogger.com/profile/12652284939993729858</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' 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>2</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-13967713.post-8172890871782761870</id><published>2011-03-01T14:47:38.902+01:00</published><updated>2011-03-01T14:47:38.902+01:00</updated><title type='text'>For a discussion of a suite of effective theories ...</title><content type='html'>For a discussion of a suite of effective theories that describe the behavior of software, see my blog on softwarephysics at:&lt;br /&gt;http://softwarephysics.blogspot.com/</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/13967713/447151406139320702/comments/default/8172890871782761870'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/13967713/447151406139320702/comments/default/8172890871782761870'/><link rel='alternate' type='text/html' href='http://www.carlopescio.com/2010/10/notes-on-software-design-chapter-11.html?showComment=1298987258902#c8172890871782761870' title=''/><author><name>Steve Johnston</name><uri>http://www.blogger.com/profile/09622155354944947611</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.carlopescio.com/2010/10/notes-on-software-design-chapter-11.html' ref='tag:blogger.com,1999:blog-13967713.post-447151406139320702' source='http://www.blogger.com/feeds/13967713/posts/default/447151406139320702' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1372269759'/></entry><entry><id>tag:blogger.com,1999:blog-13967713.post-3384030688970769551</id><published>2010-10-14T14:03:05.592+02:00</published><updated>2010-10-14T14:03:05.592+02:00</updated><title type='text'>Carlo, thanks for yet another exciting post in thi...</title><content type='html'>Carlo, thanks for yet another exciting post in this series, I absolutely love it! First it&amp;#39;s fun and even entertaining, to me at least. It also looks promising, obviously towards new smarter metrics, but especially toward a better informed vocabulary of concepts that we can use to shape, analyze and explain our design.&lt;br /&gt;&lt;br /&gt;This post has a weak -bare chronological- structure, yet is one of the easiest to understand, this structure is a good idea indeed. &lt;br /&gt;&lt;br /&gt;On the content, I had the matters of cohesion and coupling in my mind while reading your post, a bit like &amp;quot;haha, we&amp;#39;re going toward deeper-than-usual explanations of why low coupling and high cohesion is good&amp;quot;.&lt;br /&gt;&lt;br /&gt;&amp;quot;high-mass, low-viscosity artifacts can be considered as rather innocent underengineering&amp;quot;: yes indeed, this is now clear, and our usual metrics fail to capture that kind of distinction.&lt;br /&gt;&lt;br /&gt;Your concept of gravity, which makes massive (heavy?) artifacts get worst over time because they attract more stuff, is also very relevant; I like the dynamic view of software and its forces that influence us. It takes a lot of will to resist such forces sometimes.&lt;br /&gt;&lt;br /&gt;To be honest, I also write a comment to share my enthusiasm, and I hope you will carry on and refine that thread of research. Cheers</content><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/13967713/447151406139320702/comments/default/3384030688970769551'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/13967713/447151406139320702/comments/default/3384030688970769551'/><link rel='alternate' type='text/html' href='http://www.carlopescio.com/2010/10/notes-on-software-design-chapter-11.html?showComment=1287057785592#c3384030688970769551' title=''/><author><name>Cyrille Martraire</name><uri>http://cyrille.martraire.com/</uri><email>noreply@blogger.com</email><gd:image xmlns:gd='http://schemas.google.com/g/2005' rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img1.blogblog.com/img/blank.gif'/></author><thr:in-reply-to xmlns:thr='http://purl.org/syndication/thread/1.0' href='http://www.carlopescio.com/2010/10/notes-on-software-design-chapter-11.html' ref='tag:blogger.com,1999:blog-13967713.post-447151406139320702' source='http://www.blogger.com/feeds/13967713/posts/default/447151406139320702' type='text/html'/><gd:extendedProperty xmlns:gd='http://schemas.google.com/g/2005' name='blogger.itemClass' value='pid-1760457026'/></entry></feed>
