<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0" xml:base="http://www.42lines.net">
<channel>
 <title>42 Lines blogs</title>
 <link>http://www.42lines.net/blog</link>
 <description>42 Lines delivers scalable web applications that are easy to use and easy to maintain.
</description>
 <language>en</language>
<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/42LinesBlogs" /><feedburner:info xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" uri="42linesblogs" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
 <title>A programmer parable: A broken clothes dryer</title>
 <link>http://www.42lines.net/content/programmer-parable-broken-clothes-dryer</link>
 <description>&lt;p&gt;It's pretty obvious that the principles behind good software engineering are not domain specific, but today I was reminded that they aren't even specific to programming itself.&amp;nbsp; They're &lt;em&gt;engineering&lt;/em&gt; principles, and beyond that, they're principles of problem solving that we observe in daily life.&amp;nbsp; For example, let's say your clothes drier stops working, like mine did, oh...several months ago.&amp;nbsp; The lessons are in italics, and though they are obvious, it's the obvious things that need re-iteration.&amp;nbsp; At least for me :)&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/content/programmer-parable-broken-clothes-dryer" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/content/programmer-parable-broken-clothes-dryer#comments</comments>
 <category domain="http://www.42lines.net/category/tags/testing-engineering-principles-design">testing engineering principles design</category>
 <pubDate>Tue, 26 May 2009 02:11:01 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">22 at http://www.42lines.net</guid>
</item>
<item>
 <title>Integrating hibernate validator and wicket</title>
 <link>http://www.42lines.net/content/integrating-hibernate-validator-and-wicket</link>
 <description>&lt;p&gt;I've made some code public that integrates &lt;a href="http://validator.hibernate.org/"&gt;Hibernate Validator&lt;/a&gt;&amp;nbsp;with Wicket.&amp;nbsp; The code is available via anonymous svn via:&lt;/p&gt;
&lt;p&gt;&amp;nbsp; svn co &lt;a href="https://svn.42lines.net/public/examples/wicket/hibernate-validator-example" title="https://svn.42lines.net/public/examples/wicket/hibernate-validator-example"&gt;https://svn.42lines.net/public/examples/wicket/hibernate-validator-example&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;and I'll go through how it works in this post.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/content/integrating-hibernate-validator-and-wicket" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/content/integrating-hibernate-validator-and-wicket#comments</comments>
 <category domain="http://www.42lines.net/category/tags/wicket-hibernate-testing-validator">wicket hibernate testing validator</category>
 <pubDate>Fri, 22 May 2009 16:13:46 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">21 at http://www.42lines.net</guid>
</item>
<item>
 <title>AWS adds monitoring/loadbalancing/scaling</title>
 <link>http://www.42lines.net/content/aws-adds-monitoringloadbalancingscaling</link>
 <description>&lt;p&gt;It looks like AWS has recognized that turnkey scaling as provided by GAE is a competitive advantage, and has &lt;a href="http://aws.amazon.com/about-aws/whats-new/2009/05/17/monitoring-auto-scaling-elastic-load-balancing/"&gt;added that &lt;/a&gt; to their set of core services, as well as &lt;a href="http://aws.amazon.com/about-aws/whats-new/2009/05/17/monitoring-auto-scaling-elastic-load-balancing/"&gt;load balancing and monitoring.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/content/aws-adds-monitoringloadbalancingscaling" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/content/aws-adds-monitoringloadbalancingscaling#comments</comments>
 <pubDate>Mon, 18 May 2009 13:32:36 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">19 at http://www.42lines.net</guid>
</item>
<item>
 <title>The deployment KISS</title>
 <link>http://www.42lines.net/blog/clint/deployment-kiss</link>
 <description>&lt;p&gt;In &lt;a href="http://www.seamframework.org/Community/SeamEJB3VsSeamPOJO#comment76122"&gt;this post&lt;/a&gt; on the seam framework list I reiterate a point that I think a lot of J2EE folks miss when they're designing apps.&lt;/p&gt;
&lt;p&gt;&lt;b&gt;KISS applies to deployments too.&lt;/b&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/blog/clint/deployment-kiss" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/blog/clint/deployment-kiss#comments</comments>
 <pubDate>Mon, 11 May 2009 18:49:35 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">18 at http://www.42lines.net</guid>
</item>
<item>
 <title>Is integration testing a Bad Thing (tm)?</title>
 <link>http://www.42lines.net/content/integration-testing-bad-thing-tm</link>
 <description>&lt;p&gt;J.B. Rainsberger has recently been &lt;a href="http://www.infoq.com/news/2009/04/jbrains-integration-test-scam"&gt;railing against intgeration testing&lt;/a&gt;, and I find myself agreeing with that argument a great deal.  Our  integration tests always take too long to run, are astable with respect to changes to the UI layer, and are probably sucking time that could be better spent unit testing.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/content/integration-testing-bad-thing-tm" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/content/integration-testing-bad-thing-tm#comments</comments>
 <category domain="http://www.42lines.net/category/tags/wicket-bdd-jdave-integration-testing">wicket bdd jdave integration testing</category>
 <pubDate>Mon, 11 May 2009 13:59:23 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">17 at http://www.42lines.net</guid>
</item>
<item>
 <title>Types everywhere</title>
 <link>http://www.42lines.net/blog/clint/types-everywhere</link>
 <description>&lt;p&gt;As we migrate more of our code away from JSF and towards Apache Wicket, I'm struck again by how nearly every architectural change we've made has been &lt;em&gt;toward&lt;/em&gt; more strong typing and thus &lt;em&gt;away&lt;/em&gt; from anything that a compiler can't verify.  I'm getting pretty religious about this.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.42lines.net/blog/clint/types-everywhere" target="_blank"&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.42lines.net/blog/clint/types-everywhere#comments</comments>
 <pubDate>Mon, 11 May 2009 02:58:34 +0000</pubDate>
 <dc:creator>cpopetz</dc:creator>
 <guid isPermaLink="false">16 at http://www.42lines.net</guid>
</item>
</channel>
</rss>
