<?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: The Process of Software Architecting</title>
	<atom:link href="http://blog.martinig.ch/books/the-process-of-software-architecting/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.martinig.ch/books/the-process-of-software-architecting/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 18:09:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Marc W</title>
		<link>http://blog.martinig.ch/books/the-process-of-software-architecting/comment-page-1/#comment-9853</link>
		<dc:creator>Marc W</dc:creator>
		<pubDate>Thu, 03 Mar 2011 09:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martinig.ch/?p=432#comment-9853</guid>
		<description>I am really surprised that the book gets that positive comments. Not only here but also at some ohter places. I am reading it at the moment. I&#039;ve read the first five chapters now, so the rest of the book might be better, but thát good? The first 100 pages of the book all full of vague definitions, which are on the one hand &#039;open doors&#039;, like things that are already known to all who know software development, on the other hand still to abstract to be useful. Now I am hoping that the case studies starting from page 100 are more interesting, but I am not screaming from the roof how good this book is now.</description>
		<content:encoded><![CDATA[<p>I am really surprised that the book gets that positive comments. Not only here but also at some ohter places. I am reading it at the moment. I&#8217;ve read the first five chapters now, so the rest of the book might be better, but thát good? The first 100 pages of the book all full of vague definitions, which are on the one hand &#8216;open doors&#8217;, like things that are already known to all who know software development, on the other hand still to abstract to be useful. Now I am hoping that the case studies starting from page 100 are more interesting, but I am not screaming from the roof how good this book is now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: blog.martinig.ch @ 2012-02-09 23:46:44 by W3 Total Cache -->
