<?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: Security architecture and document reviews</title>
	<atom:link href="http://www.greebo.net/2005/08/18/security-architecture-and-document-reviews/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.greebo.net/2005/08/18/security-architecture-and-document-reviews/</link>
	<description>mostly useless crap from me</description>
	<lastBuildDate>Mon, 23 Jan 2012 12:46:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Tor</title>
		<link>http://www.greebo.net/2005/08/18/security-architecture-and-document-reviews/comment-page-1/#comment-245</link>
		<dc:creator>Tor</dc:creator>
		<pubDate>Fri, 19 Aug 2005 20:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.greebo.net/wp/?p=311#comment-245</guid>
		<description>There might be One True Way for many things - but humans don&#039;t necessarily work or think in the same way. Also, when designing an architecture there will be many considerations to take and Security is an important one but certainly not the only aspect. 
Therefore, I beg to differ somewhat to the &quot;uber-architectural&quot; approach: 
I&#039;&#039;d argue that in a team effort to create an architecture you&#039;ve got to be tough enough to botch communicate clearly and honestly about issues that are critical. However, you may  also be prepared  to give up on areas that you identify as lesser importance (whether they be less risky/critical issues, or document  form/layout) in order to get the main message across.</description>
		<content:encoded><![CDATA[<p>There might be One True Way for many things &#8211; but humans don&#8217;t necessarily work or think in the same way. Also, when designing an architecture there will be many considerations to take and Security is an important one but certainly not the only aspect.<br />
Therefore, I beg to differ somewhat to the &#8220;uber-architectural&#8221; approach:<br />
I&#8221;d argue that in a team effort to create an architecture you&#8217;ve got to be tough enough to botch communicate clearly and honestly about issues that are critical. However, you may  also be prepared  to give up on areas that you identify as lesser importance (whether they be less risky/critical issues, or document  form/layout) in order to get the main message across.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

