<?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>Really Aced &#187; agile</title>
	<atom:link href="http://blog.sommestad.net/tag/agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sommestad.net</link>
	<description>Web and Cocoa development through the eyes of Kristofer Sommestad, a SWAD developer.</description>
	<lastBuildDate>Sun, 23 Jan 2011 12:21:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Flash Catalyst gives me the creeps</title>
		<link>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/</link>
		<comments>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/#comments</comments>
		<pubDate>Mon, 16 Mar 2009 09:14:16 +0000</pubDate>
		<dc:creator>esset</dc:creator>
				<category><![CDATA[Flash & Flex]]></category>
		<category><![CDATA[actionscript]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[flash catalyst]]></category>
		<category><![CDATA[pipeline]]></category>
		<category><![CDATA[wysiwyg]]></category>

		<guid isPermaLink="false">http://reallyaced.wordpress.com/?p=56</guid>
		<description><![CDATA[Recently we&#8217;ve been having general discussions on the workflow in agile development projects. How can we make our development pipelines as effective as possible for our developers and designers? One product trying to address this is Adobe&#8217;s Flash Catalyst. Flash Catalyst aims towards allowing for importing a ready-made Photoshop file with a site design to [...]]]></description>
			<content:encoded><![CDATA[<p>Recently we&#8217;ve been having general discussions on the workflow in agile development projects. How can we make our development pipelines as effective as possible for our developers and designers? One product trying to address this is Adobe&#8217;s <a href="http://labs.adobe.com/technologies/flashcatalyst/">Flash Catalyst</a>.</p>
<p>Flash Catalyst aims towards allowing for importing a ready-made Photoshop file with a site design to a workbench, where various functionality can be added easily: new pages, visual effects (transitions) etc. It all sounds really nice, as it makes it easy to convert a design into a real application with functionality.</p>
<p><strong>It&#8217;s giving me the creeps</strong></p>
<p>It&#8217;s pretty much at this moment I really start getting the creeps. To me, WYSIWYG (&#8220;What You See Is What You Get&#8221;) editors have never been anything but bad. They&#8217;re of course easy-to-use, but generally produce crappy code that infects your application like a virus. The code debt increases exponentially by the minute (OK, maybe I&#8217;m exaggerating again&#8230;)  and in the end, you&#8217;ll lose control of your application.</p>
<p>This might be OK in one-time-development applications such as ads, campaign sites etc, but in our world, we can&#8217;t really afford creating our applications from scratch all the time. It&#8217;s really important to create good, reusable code in order to stay on top. And from what I&#8217;ve seen this far, that is nothing that&#8217;s done by using tools like Flash Catalyst (or even Flex?).</p>
<p><strong>It&#8217;s important to stay in control</strong></p>
<p>We mostly build large applications with quite advanced features and we need to be able to maintain in control of the code, as the risk of producing nasty bugs increases with the size of your application. If you&#8217;re using a UI based tool like Flash Catalyst, it&#8217;s very likely that you will have a lot more trouble finding where the issue really is than if you&#8217;ve got yourself a well-written code base.</p>
<p>In my opinion &#8211; when working with applications like ours&#8217; &#8211; the development velocity is not more important than having a well-developed application.</p>
<p><strong>I&#8217;m not saying it&#8217;s worthless</strong>&#8230;</p>
<p>As with everything, I can&#8217;t really say that it&#8217;s crap before we&#8217;ve tried it out for real. I just don&#8217;t think we&#8217;ll be able to rely on it for our bigger games, given what I&#8217;ve read and the demos I&#8217;ve watched this far. But maybe we can use Flash Catalyst for marketing campaigns (i.e. ads) and smaller prototypes of our applications? That would probably be a more logical way to use it.</p>
<p>Please prove me wrong; it&#8217;d be awesome if designers could implement their changes while not ruining my code&#8230; <img src='http://blog.sommestad.net/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
<p><strong>Some references</strong></p>
<p><a href="http://www.insideria.com/2008/12/thoughts-on-flash-catalyst.html">Chris Griffith&#8217;s thoughts on FC</a> (and some comments on his thoughts)</p>
<p><a href="http://theflashblog.com/?p=619">FC Video Tutorial</a></p>
<p><a href="http://labs.adobe.com/technologies/flashcatalyst/">Official FC site</a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.sommestad.net/2009/03/flash-catalyst-gives-me-the-creeps-2/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

