<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>InsideRIA</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/" />
<link rel="self" type="application/atom+xml" href="http://www.insideria.com/atom.xml" />
<id>tag:www.insideria.com,2008-01-28://34</id>
<updated>2009-09-17T15:08:54Z</updated>
<subtitle>InsideRIA.com is an online community developed by O’Reilly and sponsored by Adobe Systems Incorporated. Our goal is to create an invaluable resource for information on the ever-changing state of design and development of rich Internet applications (RIAs).</subtitle>
<generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.21-en</generator>

<entry>
<title>Do You Speak Flex?  Part Two:  Recruiting the Right Experience</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/2009/09/do-you-speak-flex-part-two-rec.html" />
<id>tag:www.insideria.com,2009://34.37902</id>

<published>2009-09-09T16:09:09Z</published>
<updated>2009-09-17T15:08:54Z</updated>

<summary>It&apos;s imperative to identify what your requirements are and the number of resources that you&apos;ll need to address them. You must determine what your team needs to accomplish before you begin to assemble it, otherwise you risk redundancy, inefficiency, and slowed or stalled projects. It sounds elementary, but this step can save you a lot of headaches later on. </summary>
<author>
<name>Ben Elmore</name>

</author>

<category term="Blogs" scheme="http://www.sixapart.com/ns/types#category" />

<category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flex" label="flex" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flexframework" label="flex framework" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="teamdevelopment" label="team development" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="training" label="training" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.insideria.com/">
It&apos;s imperative to identify what your requirements are and the number of resources that you&apos;ll need to address them. You must determine what your team needs to accomplish before you begin to assemble it, otherwise you risk redundancy, inefficiency, and slowed or stalled projects. It sounds elementary, but this step can save you a lot of headaches later on. 
</content>
</entry>

<entry>
<title>Do You Speak Flex?  Part One:  Building a Team</title>
<link rel="alternate" type="text/html" href="http://www.insideria.com/2009/08/do-you-speak-flex-part-one-bui.html" />
<id>tag:www.insideria.com,2009://34.37710</id>

<published>2009-08-13T13:00:00Z</published>
<updated>2009-08-13T20:00:39Z</updated>

<summary>With the release of Flex 4, misconceptions abound regarding Flex, and there has been a general reluctance to build Flex development teams internally.  These are that Flex resources are scarce, and that teams need years of experience, must be large, expensive, and comprised of all-stars. However, I&apos;ve found that with a few exceptions, the opposite is generally true and that nearly any organization can afford to build an effective team.  This series of articles intends to debunk mistaken notions and help organizations realize the power and accessibility of this skill set. </summary>
<author>
<name>Ben Elmore</name>

</author>

<category term="Blogs" scheme="http://www.sixapart.com/ns/types#category" />

<category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flash" label="flash" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flex" label="flex" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="flexframework" label="flex framework" scheme="http://www.sixapart.com/ns/types#tag" />
<category term="teamdevelopment" label="team development" scheme="http://www.sixapart.com/ns/types#tag" />

<content type="html" xml:lang="en" xml:base="http://www.insideria.com/">
With the release of Flex 4, misconceptions abound regarding Flex, and there has been a general reluctance to build Flex development teams internally.  These are that Flex resources are scarce, and that teams need years of experience, must be large, expensive, and comprised of all-stars. However, I&apos;ve found that with a few exceptions, the opposite is generally true and that nearly any organization can afford to build an effective team.  This series of articles intends to debunk mistaken notions and help organizations realize the power and accessibility of this skill set. 
</content>
</entry>

</feed>