<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Architexa - Working with Large Codebases</title>
	<atom:link href="http://blog.architexa.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.architexa.com</link>
	<description>know your code</description>
	<lastBuildDate>Wed, 09 Nov 2011 21:20:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Celebrating Eclipse&#8217;s 10th Birthday in Boston</title>
		<link>http://blog.architexa.com/2011/11/celebrating-eclipses-10th-birthday-in-boston/</link>
		<comments>http://blog.architexa.com/2011/11/celebrating-eclipses-10th-birthday-in-boston/#comments</comments>
		<pubDate>Wed, 09 Nov 2011 21:20:12 +0000</pubDate>
		<dc:creator>Vineet Sinha</dc:creator>
				<category><![CDATA[About]]></category>
		<category><![CDATA[Eclipse]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=320</guid>
		<description><![CDATA[Eclipse is turning 10 years &#8211; and we have been in a mood to celebrate it. We have been involved in a lot of Eclipse related events in the past, but wanted to do something special this year. If you are in Boston, come join us next week. We will be having free pizza, beer [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/11/celebrating-eclipses-10th-birthday-in-boston/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Diagrams in Open Source &amp; Successful Development</title>
		<link>http://blog.architexa.com/2011/09/diagrams-in-open-source-successful-development/</link>
		<comments>http://blog.architexa.com/2011/09/diagrams-in-open-source-successful-development/#comments</comments>
		<pubDate>Wed, 07 Sep 2011 21:15:15 +0000</pubDate>
		<dc:creator>novita</dc:creator>
				<category><![CDATA[Documentation & Communication]]></category>
		<category><![CDATA[Understanding Developers]]></category>
		<category><![CDATA[eclipse]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=310</guid>
		<description><![CDATA[When development teams are in the same room, it is not surprising to see diagrams being used &#8211; if only being shared via sketches made on pads, or through the use of whiteboards. Interestingly, despite the fact that OSS teams are distributed geographically, diagrams also play an important role in OSS development. There was a [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/09/diagrams-in-open-source-successful-development/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Diagrams- More than What Meets the Eye</title>
		<link>http://blog.architexa.com/2011/08/diagrams-more-than-what-meets-the-eye/</link>
		<comments>http://blog.architexa.com/2011/08/diagrams-more-than-what-meets-the-eye/#comments</comments>
		<pubDate>Wed, 24 Aug 2011 22:07:27 +0000</pubDate>
		<dc:creator>novita</dc:creator>
				<category><![CDATA[Documentation & Communication]]></category>
		<category><![CDATA[Understanding Developers]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=303</guid>
		<description><![CDATA[“Diagrams?” Yes, diagrams. All of us use diagrams in one way or another. Mostly, diagrams are used to enhance communication and to illustrate what exactly one is talking about. “But that’s it. Diagrams are sketches which are meant to be thrown away without deserving a second look.” Now that&#8217;s where you&#8217;re wrong. In fact, diagrams [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/08/diagrams-more-than-what-meets-the-eye/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Making Code Easy to Understand &#8211; What Developers Want (a study)</title>
		<link>http://blog.architexa.com/2011/07/making-code-easy-to-understand-what-developers-want-a-study/</link>
		<comments>http://blog.architexa.com/2011/07/making-code-easy-to-understand-what-developers-want-a-study/#comments</comments>
		<pubDate>Wed, 27 Jul 2011 13:10:01 +0000</pubDate>
		<dc:creator>Vineet Sinha</dc:creator>
				<category><![CDATA[Documentation & Communication]]></category>
		<category><![CDATA[Understanding Developers]]></category>
		<category><![CDATA[User Experience]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=198</guid>
		<description><![CDATA[What exactly makes a codebase easy to understand; the documentation or the tools that you use? In our effort to help developers who are working with large codebases, we conducted a survey (see details and highlights) to find out what techniques developers use to better understand code. One of the major questions that we had [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/07/making-code-easy-to-understand-what-developers-want-a-study/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>A Detailed Study on Understanding Code</title>
		<link>http://blog.architexa.com/2011/07/a-detailed-study-on-understanding-code/</link>
		<comments>http://blog.architexa.com/2011/07/a-detailed-study-on-understanding-code/#comments</comments>
		<pubDate>Tue, 19 Jul 2011 19:45:40 +0000</pubDate>
		<dc:creator>Vineet Sinha</dc:creator>
				<category><![CDATA[Agile & Development Methodologies]]></category>
		<category><![CDATA[Documentation & Communication]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=252</guid>
		<description><![CDATA[Let&#8217;s face it; code can be hard to understand. We have all encountered a piece of code that took longer than expected to figure out or was easy to misunderstand. It could be a new library, a coworker&#8217;s code, or your own code from 6 month&#8217;s ago. In a previous post we discuss the importance of [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/07/a-detailed-study-on-understanding-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Code Visibility: one factor of code quality that you shouldn’t forget</title>
		<link>http://blog.architexa.com/2011/07/code-visibility-one-factor-of-code-quality-that-you-shouldn%e2%80%99t-forget/</link>
		<comments>http://blog.architexa.com/2011/07/code-visibility-one-factor-of-code-quality-that-you-shouldn%e2%80%99t-forget/#comments</comments>
		<pubDate>Wed, 13 Jul 2011 21:23:47 +0000</pubDate>
		<dc:creator>Xin</dc:creator>
				<category><![CDATA[Agile & Development Methodologies]]></category>
		<category><![CDATA[Design Patterns & Architecture]]></category>
		<category><![CDATA[Developer Tools]]></category>
		<category><![CDATA[UML & Diagramming]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=289</guid>
		<description><![CDATA[Every developer cares about code quality. But how do you maintain code quality throughout the software development cycle? Readability, modularity, and efficiency all are important factors of writing good code but there isn&#8217;t much agreement on the best way to maintain a high level of code quality. One factor which is often missed in discussions [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/07/code-visibility-one-factor-of-code-quality-that-you-shouldn%e2%80%99t-forget/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>UML- Useless Meaningless Lousy?</title>
		<link>http://blog.architexa.com/2011/07/uml-useless-meaningless-lousy-2/</link>
		<comments>http://blog.architexa.com/2011/07/uml-useless-meaningless-lousy-2/#comments</comments>
		<pubDate>Tue, 05 Jul 2011 20:37:26 +0000</pubDate>
		<dc:creator>novita</dc:creator>
				<category><![CDATA[UML & Diagramming]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=270</guid>
		<description><![CDATA[It is easy to find numerous negative sentiments about UML. The main complaints seem to revolve around UML being of little practical use and inconvenient to draw and update. I have been looking into the practicality of UML and find this answer on stackoverflow very interesting: Using UML is like looking at your feet as [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/07/uml-useless-meaningless-lousy-2/feed/</wfw:commentRss>
		<slash:comments>17</slash:comments>
		</item>
		<item>
		<title>Herding Software Developers</title>
		<link>http://blog.architexa.com/2011/06/herding-software-developers/</link>
		<comments>http://blog.architexa.com/2011/06/herding-software-developers/#comments</comments>
		<pubDate>Thu, 30 Jun 2011 20:44:33 +0000</pubDate>
		<dc:creator>Seth Rosen</dc:creator>
				<category><![CDATA[Agile & Development Methodologies]]></category>
		<category><![CDATA[Documentation & Communication]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=250</guid>
		<description><![CDATA[Managing software developers can be a difficult task, especially when working with an agile team. Changing requirements and priorities combined with a learning and growing team can make even the most experienced managers sweat. Similar complex interactions have been studied in a number of fields. Game Theory, Cybernetics, and Chaos Theory all provide inspiration to managers [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/06/herding-software-developers/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>50 Articles on Code, Architecture, Agile, and Large Codebases</title>
		<link>http://blog.architexa.com/2011/06/50-articles-on-code-architecture-agile-and-large-codebasses/</link>
		<comments>http://blog.architexa.com/2011/06/50-articles-on-code-architecture-agile-and-large-codebasses/#comments</comments>
		<pubDate>Wed, 29 Jun 2011 18:16:04 +0000</pubDate>
		<dc:creator>Seth Rosen</dc:creator>
				<category><![CDATA[About]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=282</guid>
		<description><![CDATA[Today Architexa&#8217;s &#8220;Working With Large Codebases&#8221; blog has posted it&#8217;s 50th post. While not a huge number, we are excited to see the response to so many of our articles for helping developers work with Eclipse, with agile teams, use design patterns, and document and communicate ideas  with developer tools and diagrams. Architexa has been working [...]]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/06/50-articles-on-code-architecture-agile-and-large-codebasses/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Uh oh, not another Large Code Base!</title>
		<link>http://blog.architexa.com/2011/06/not-another-large-codebase/</link>
		<comments>http://blog.architexa.com/2011/06/not-another-large-codebase/#comments</comments>
		<pubDate>Tue, 21 Jun 2011 20:38:57 +0000</pubDate>
		<dc:creator>novita</dc:creator>
				<category><![CDATA[Developer Tools]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://blog.architexa.com/?p=265</guid>
		<description><![CDATA[I came across two blog posts which agree that large code bases are a hassle to programmers. The first post, “Code’s worst enemy” written by Steve Yegge, basically loathes large code bases and Jeff Atwok shares the same opinion in “Size is the enemy” . The problem with large code bases is that their physical size is indication for the large amount of effort, cost and time to be invested for that project, as stated in Steve McConnell books.]]></description>
		<wfw:commentRss>http://blog.architexa.com/2011/06/not-another-large-codebase/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

