<?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>Skillful Software</title>
	<atom:link href="http://www.upayasoftware.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.upayasoftware.com</link>
	<description>Looking for skillful techniques that make it easier to build software well</description>
	<lastBuildDate>Wed, 08 Jul 2009 10:54:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>The Science of Business Applications</title>
		<link>http://www.upayasoftware.com/2009/07/08/the-science-of-business-applications/</link>
		<comments>http://www.upayasoftware.com/2009/07/08/the-science-of-business-applications/#comments</comments>
		<pubDate>Wed, 08 Jul 2009 10:54:43 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Software Is Hard]]></category>
		<category><![CDATA[Software Process]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=61</guid>
		<description><![CDATA[Building software is both an art and a science, as many people have said.  One might argue that when building business applications it is better to leave the art behind, and focus on the science.  Business software needs to be reliable, scalable, and built on time and budget, after all. And it is true that [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2009/07/08/the-science-of-business-applications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can architecture be agile? Absolutely.</title>
		<link>http://www.upayasoftware.com/2009/07/02/can-architecture-be-agile-absolutely/</link>
		<comments>http://www.upayasoftware.com/2009/07/02/can-architecture-be-agile-absolutely/#comments</comments>
		<pubDate>Thu, 02 Jul 2009 10:48:42 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Software Process]]></category>
		<category><![CDATA[Teams]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=53</guid>
		<description><![CDATA[Lately both Pawel Brodzinski and Martin Fowler have been letting people know that architecture and agile are not incompatible.  I wholeheartedly agree, and actually am I a bit surprised at the extent to which people seem to think these two approaches are mutually exclusive &#8211; they seem pretty compatible to me.  At is root, I [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2009/07/02/can-architecture-be-agile-absolutely/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JavaServer Faces performance &#8211; some specifics</title>
		<link>http://www.upayasoftware.com/2009/07/01/javaserver-faces-performance-some-specifics/</link>
		<comments>http://www.upayasoftware.com/2009/07/01/javaserver-faces-performance-some-specifics/#comments</comments>
		<pubDate>Wed, 01 Jul 2009 13:30:19 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Coding]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=49</guid>
		<description><![CDATA[Last year I posted about some helpful advice I found on JSF performance.  Sadly, those slides are no longer available.  So I&#8217;m putting the details that I remember in this post.

JSF keeps lots of information about the current page and previous pages in the JSF state object.  This allows all of the Faces components to [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2009/07/01/javaserver-faces-performance-some-specifics/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Unit testing vocabulary</title>
		<link>http://www.upayasoftware.com/2009/06/17/unit-testing-vocabulary/</link>
		<comments>http://www.upayasoftware.com/2009/06/17/unit-testing-vocabulary/#comments</comments>
		<pubDate>Wed, 17 Jun 2009 11:36:10 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Worth Reading]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=44</guid>
		<description><![CDATA[I just saw Martin Fowler&#8217;s little note about the vocabulary of unit testing, and I thought it was so clear and helpful that I had to share it.
Just seeing the words and the definitions listed side by side clarifies several approaches to what is proabably the hardest part of unit testing &#8211; keeping your tests [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2009/06/17/unit-testing-vocabulary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clear thinking about code reuse</title>
		<link>http://www.upayasoftware.com/2009/06/09/clear-thinking-about-code-reuse/</link>
		<comments>http://www.upayasoftware.com/2009/06/09/clear-thinking-about-code-reuse/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 14:41:33 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Software Design]]></category>
		<category><![CDATA[Worth Reading]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=39</guid>
		<description><![CDATA[Udi Dahan has just fired off a great post about the pitfals of trying to reuse code &#8211; that we make big problems for ourselves by trying to re-use domain-specific code into ways it wasn&#8217;t designed to be used. Successful re-use comes about when the code being used is generic enough to actually work in [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2009/06/09/clear-thinking-about-code-reuse/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Feeling a bit of a fanboy</title>
		<link>http://www.upayasoftware.com/2008/10/31/feeling-a-bit-of-a-fanboy/</link>
		<comments>http://www.upayasoftware.com/2008/10/31/feeling-a-bit-of-a-fanboy/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 17:35:48 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Coding]]></category>
		<category><![CDATA[Organization]]></category>
		<category><![CDATA[Software Process]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Worth Reading]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=38</guid>
		<description><![CDATA[Call me a fanboy if you must, but the people at Coding the Architecture know their stuff.  The slides Simon Brown put together on Why Software Projects Fail are a very good, very specific description of what a good software architect can bring to the a project
]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2008/10/31/feeling-a-bit-of-a-fanboy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Test for good developers</title>
		<link>http://www.upayasoftware.com/2008/10/30/test-for-good-developers/</link>
		<comments>http://www.upayasoftware.com/2008/10/30/test-for-good-developers/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 19:16:13 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Career]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Software Design]]></category>
		<category><![CDATA[Specific Technologies]]></category>
		<category><![CDATA[Teams]]></category>
		<category><![CDATA[Worth Reading]]></category>
		<category><![CDATA[Interviewing]]></category>
		<category><![CDATA[Thinking Architecturally]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=37</guid>
		<description><![CDATA[I&#8217;ve definitely made some interviewing mistakes in my day.  Once mistake which I hope too avoid in the future is hiring people who don&#8217;t think architecturally, as so eloquently described by Simon Brown over at Coding the Architecture.
I&#8217;ve recommended a couple of people who seemed quite competent when talking about their technical skills during the [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2008/10/30/test-for-good-developers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>JavaServer Faces performance concerns addressed</title>
		<link>http://www.upayasoftware.com/2008/10/29/javaserver-faces-performance/</link>
		<comments>http://www.upayasoftware.com/2008/10/29/javaserver-faces-performance/#comments</comments>
		<pubDate>Wed, 29 Oct 2008 20:41:49 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[Specific Technologies]]></category>
		<category><![CDATA[JavaServer Faces]]></category>
		<category><![CDATA[JSF]]></category>
		<category><![CDATA[memory]]></category>
		<category><![CDATA[performance]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=36</guid>
		<description><![CDATA[I&#8217;m back in JSF land recently, and today I found Eelco Klaver&#8217;s slides on JSF performance.  Anyone considering JSF should read the slides.  They provide a clear and succinct analysis of why there is a very serious out-of-the-box performance issue with JSF, and what to do about it.  This issue is not widely documented, so [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2008/10/29/javaserver-faces-performance/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Another excellent point</title>
		<link>http://www.upayasoftware.com/2008/10/28/another-excellent-point/</link>
		<comments>http://www.upayasoftware.com/2008/10/28/another-excellent-point/#comments</comments>
		<pubDate>Tue, 28 Oct 2008 15:30:32 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Software Design]]></category>
		<category><![CDATA[Worth Reading]]></category>
		<category><![CDATA[Creativity]]></category>
		<category><![CDATA[Design]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=35</guid>
		<description><![CDATA[How does one arrive at good design, whether it be the architecture for a huge system or the layout for a single interface? Nick Malik over at Microsoft sums it up very nicely:
Design is a process where you consider the problem and then propose multiple, competing, wildly creative solutions.  You then narrow down your brainstorm [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2008/10/28/another-excellent-point/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Doing it right at Facebook</title>
		<link>http://www.upayasoftware.com/2008/10/27/doing-it-right-at-facebook/</link>
		<comments>http://www.upayasoftware.com/2008/10/27/doing-it-right-at-facebook/#comments</comments>
		<pubDate>Mon, 27 Oct 2008 15:02:17 +0000</pubDate>
		<dc:creator>Andrew Sacamano</dc:creator>
				<category><![CDATA[Architecture]]></category>
		<category><![CDATA[Skillfulness]]></category>
		<category><![CDATA[Software Design]]></category>
		<category><![CDATA[Worth Reading]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Loggin]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[Reliability]]></category>
		<category><![CDATA[Robet Johnson]]></category>
		<category><![CDATA[Skill]]></category>

		<guid isPermaLink="false">http://www.upayasoftware.com/?p=34</guid>
		<description><![CDATA[I came across this today, and was so pleased by the clarity of thought that I needed to share it.  From Robert Johnson at Facebook, describing their monitoring protocol, Scribe:
The second major design decision was about reliability. We chose was a middle ground here, reliable enough that we can expect to get all of the [...]]]></description>
		<wfw:commentRss>http://www.upayasoftware.com/2008/10/27/doing-it-right-at-facebook/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
