<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.6.2" -->
<rss version="0.92">
<channel>
	<title>Andy@Gigantiq</title>
	<link>http://www.gigantiq.com/blogs/andy</link>
	<description>Andy's Gigantiq blog.</description>
	<lastBuildDate>Sun, 08 Feb 2009 03:42:59 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Rules of structured programming and Scala</title>
		<description><![CDATA[Recently I have been reading &#8220;Clean Code A Handbook of Agile Software Craftsmanship&#8221; by Robert C. Martin. I was originally inspired to read this book after attending a talk given by Robert Martin at JAOO earlier this year in Brisbane where he talked about &#8220;Clean Code&#8221;.
With my current focus being on Scala, I find myself [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/16/rules-of-structured-programming-and-scala/</link>
			</item>
	<item>
		<title>Implicit Conversions in Scala</title>
		<description><![CDATA[In the Ruby programming language, one of its most powerful features is the concept of open classes. In Ruby, classes are never closed: you can always add methods to an existing class to augment its behaviour.
An example of this taken from http://www.ruby-lang.org/en/documentation/ruby-from-other-languages is shown below.
class Fixnum
  def hours
    self * 3600 # number of seconds in [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/14/implicit-conversions-in-scala/</link>
			</item>
	<item>
		<title>Managing Transitions of Story Cards on a Wall</title>
		<description><![CDATA[Like most agile projects, my current project uses a story wall (sometimes called a Kanban Board) for keeping track of the current iteration&#8217;s worth of stories. Typically these stories are hand written on index cards and stuck on the wall in columns to show the current status of each Story.
As the the stories status changes [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/08/managing-transition-of-story-cards-on-a-wall/</link>
			</item>
	<item>
		<title>Testing Scala using specs</title>
		<description><![CDATA[As I mentioned in an earlier post, Scala offers many alternatives for unit testing. With its Java interoperability using JUnit or TestNg is no more difficult than using the purpose built testing frameworks for Scala such as ScalaTest, Rehersal, specs, and ScalaCheck.
My personal favourite is specs. The specs testing framework, is a Behaviour-Driven-Design testing tool [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/06/testing-scala-using-specs/</link>
			</item>
	<item>
		<title>IDE and Ant support for Scala</title>
		<description><![CDATA[If I intend on writing even a smallish application there are two things I look for in regards to the tool support of the language.

I hope the language has reasonable IDE support. By reasonable it should offer me a moderate number of code refactorings as a minimum.
The language should integrate nicely with an automated build [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/05/ide-and-ant-support-for-scala/</link>
			</item>
	<item>
		<title>Introduction to Scala</title>
		<description><![CDATA[For quite some time now a number of people whom I respect highly have been talking quite consitently about the Scala programming language. It has also been mentioned a number of times on &#8220;The Java Posse&#8221; pod cast. As a result my interest in Scala was sparked and I figured it is time I get [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2008/10/05/introduction-to-scala/</link>
			</item>
	<item>
		<title>Gigantiq are Looking for Skilled Java Developers</title>
		<description><![CDATA[Gigantiq has a number of exciting opportunities we are exploring at the moment. We are looking for smart Java developers to join the Melbourne team.
If you think that you can fit into a team of skilled, passionate Software Developers then drop us a line and tell us about yourself.
We are happy to engage the right [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2007/08/27/gigantiq-is-looking-for-skilled-java-developers/</link>
			</item>
	<item>
		<title>Enforcing Package Dependencies (Part 4)</title>
		<description><![CDATA[Macker is my prefered tool for java package dependency enforment. It is a free tool licenced under GPL.
While Macker is not as simple as Japan to configure, it is not difficult and is considerably more powerful. Like Japan, Macker is configured via XML and is designed to be integrated into an ant build.
Here is a [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2007/08/01/enforcing-package-dependencies-part-4/</link>
			</item>
	<item>
		<title>Enforcing Package Dependencies (Part 3)</title>
		<description><![CDATA[Japan is another open source tool that can be used for enforcing package dependencies. It comes with an IntelliJ plugin as well as an ant task. The ant task makes it trivial to incorporate into an ant build.
The real beauty of Japan is how simple it&#8217;s configuration is despite being a dreaded XML file.

&#60;japan-config base-package="com.gigantiq.bedrock" [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2007/05/30/enforcing-package-dependencies-part-3/</link>
			</item>
	<item>
		<title>Enforcing Package Dependencies (Part 2)</title>
		<description><![CDATA[JDepend is probably the best known of the package dependency tools. It has certainly been around for quite a while.
JDepend allows you to analyse java package metrics, dependencies, and cycles and allows you to visualise the analysis in a graphical UI, textual UI, and XML UI. I won&#8217;t go into detail on how to do [...]]]></description>
		<link>http://www.gigantiq.com/blogs/andy/2007/05/26/enforcing-package-dependencies-part-2/</link>
			</item>
</channel>
</rss>
