Tom Lauck’s

It’s the Age of the Deseloper


Having a non-conventional title to this journal has been somewhat of an interesting journey.  The responses regarding the title always vary and are at times, very amusing.  Surprisingly enough, about three (3) times out of ten (10), informal interviewees cannot decipher the meaning of deseloper within a reasonable 30 seconds.  Ironically, the percentage of users that did not immediately grasp the word deseloper is about 30%.  This is in fact roughly the same percentage of users that still use IE 6.  While I blatantly discriminate against IE 6 and its users, I do not and will not discriminate against users who not understand the word deseloper.  So to add a portion of understanding to all of my readers and for general education purposes, I thought it would be beneficial to examine what exactly a deseloper is in today’s workplace and if they truly have value.

Definition of Deseloper:
  • one who has the ability to produce both web design and development at high fidelity.

To dive a little deeper, deselopers can go one of three ways in there area of focus, either favoring the left side of the brain, the right, or more of a balanced approach.  Typically, these individuals can do it all.

How do you go about creating the design (look & feel, user experience, information architecture) of your applications?

  • I do it myself 58.6%


As one can imagine, this is extremely valuable in small or freelance settings.  In a larger corporate setting is there still value?

At first pass the answer may be no.  Typically large corporate environments have two sides of the house, design and development or IT.  A designer or developer having an understanding of the other side becomes more of a bonus rather than a requirement.  However, with the emergence of sophisticated UI technologies such as Flex, Silverlight, AJAX, should leveraging these technologies be left to the designer or developer?

I would argue to say both.  Take for instance the continual drive to allow better separation of logic and presentation in Silverlight. Flex, or AJAX.  This is evident by the many Microsoft developers exited over Sliverlight, but are not ready to be Silverlight developers. If there is a Silverlight developer, they are faced with the serious lack of Silverlight designers. Therefore, in order to execute on a Silverlight app, either a designer has to learn XAML and C# or the developer has to try be a designer. And we all know how that usually turns out. So, we find ourselves in an area where the true separation of developers and designers for these front end or UI technologies has not happened yet.  Enter the deseloper.

Until an adoption of these front end technologies happens for application developers around the world, or designers learn how to effectively use the other side of their brain and produce rock solid code, there is a valuable niche for the deseloper.  Because customers, clients, or management is always looking for the latest and greatest, deselopers are willing and ready to execute.  So perhaps the deseloper may someday in the near or far future be a rich internet application developer or rich internet application designer (as opposed to web designer or web developer).

On estimating value in the workplace :

A skilled, quick professional stands out these days. The people who shine are the people who get the new world – a no nonsense approach, courtesy, and most importantly, speed.


The deseloper gets the new world.  And with a full grasp of all the tools on hand from both a design and development standpoint, the deseloper can strike like lightning.  Yes, in whatever title or role the deseloper is morphed into, the deseloper is certainly here to stay.

Mar 16 2009

It’s A Walk Off! Flex MVC Frameworks Settle it on the Runway


After years of using a homegrown approach to MVC for Flash and Flex, it was time to take look at the various frameworks for Flex.  I figured “I might be of service,” David Bowie style.

This will be a Straight Walk Off, Old School Rules

Zoolander parodies aside, there are half a dozen characteristics that could be expected of a good MVC framework.  The approach was to gather a pulse on what frameworks are being discussed, download and view the source, and work with some examples.  The following criteria will be used throughout:

  1. Simplicity
  2. Minimal Footprint
  3. Maturity
  4. Scalability
  5. Active Community
  6. Some brains behind the operation (its subjective, but ‘done the right way’)

Arp Framework

Arp is(was?) Aral Balkan’s attempt at MVC for Flex. Although originally created for ActionScript 2, at Flash Forward in Austin, this looked promising. Then again, Flex was just gaining traction, so everything was looking promising. Aral has done a great job with his projects,, <head> Conference,, and his many contributions to the Flash and Adobe community. Unfortunately, however, it seems that Aral has since stopped actively developing Arp, thus eliminating Arp as an option.

1. 2. 3. 4. 5. 6. Overall


Ángel Blesa owns this project, and as one may easily surmise from his name the project is Spanish. Therefore, it is difficult to speak to the quality of the project. But, if you do speak Spanish, then this may be something to look into. However, for an English-only speaking developer, Guasax is a hard sell. Even the video tutorials are in spanish. Another quirk that factored into Guasax not making the cut was the run-time XML config files.

1. 2. 3. 4. 5. 6. Overall


At first glance, MVCS seems more like a blueprint than a framework. But, Joe Berkovitz is smart (#6 Some brains behind the operation). Joe has some interesting thoughts on Flex application architecture, and is well worth the read. It is difficult to find an active community and it is really more of an approach rather than a framework. Luckily, a framework is included in the example code. Overall, MVCS’ approach is an interesting one, however, not fully applicable if searching for an MVC framework.

1. 2. 3. 4. 5. 6. Overall

Adobe Cairngorm

Cairngorm is one of the original Flex frameworks, and it certainly has a very large backing in enterprise environments, especially since it is sponsored by Adobe. It could be said that if you are developing Flex in the enterprise, you are/should be familiar with Cairngorm. Cairngorm also has a relatively small footprint. However, Cairngorm is not a silver bullet. Although Cairngorm serves its purpose, it is a little too complex in most scenarios. Thus, if the point of a framework is to become more efficient, the complexity of Cairngorm can do quite the opposite. This is especially true for those who aren’t familiar with frameworks.

1. 2. 3. 4. 5. 6. Overall


Given the issues Cairngorm, would it not be nice if a framework took the good of Cairngorm and corrected the bad. A huge proponent of Cairngorm since it came out, Cliff Hall set out to do just that. PureMVC has gained a lot of steam since its creation, has a small footprint, is scalable, and simple. PureMVC has also been somewhat future-proofed. By keeping the concept simple and generic, PureMVC has been ported to almost every useful language. Furthermore, it is easy to find very informative documentation, overviews, and best practices. Although still relatively young and smaller community compared to Cairngorm, PureMVC seems to be evangelized among the developer community at the moment, and rightfully so.

1. 2. 3. 4. 5. 6. Overall

Time Will Tell

After looking at several frameworks for Flex, PureMVC hits the criteria stated at the outset almost perfectly. As such, I am developing with PureMVC on a current project and have been very pleased thus far. Yet, time will tell if PureMVC sticks as the de facto standard Flex MVC framework.

To the readers, I would love to hear about your findings with Flex frameworks. Perhaps you have used a framework not listed here? Or do you have a different observation or opinion?

Nov 6 2008

Time is Money, Platform Matters


Moral of the story, choose your platform wisely.  When I drafted this post in the spring, the intent was to showcase the power of highly developed platforms like ASP.NET as opposed to Ruby.  I was then going to throw all the RoR people under the bus for jumping on a bandwagon :) [prepare for getting hit over the head by Ruby people]

But now that I am in an environment where I am constantly confronted with a heavy Java back-end, this comparison seems so much more powerful. [prepare for getting hit over the head by Java people]  Granted process has a lot to do with the excessive production time some companies face, however, language and platform choice clearly has a significant impact.  In large corporate environments, elevations to production can creep on several years of work.  Platform choice, along with process management goes a long way in cutting down on time it takes to elevate.

Below is a collection of 4 screencasts from that I found on Viddler depicting a “bake-off”.  Essentially developers were given the same task of building the same basic web application.  The results were recorded and put side by side.

ASP.NET, Ruby, Java, Perl Side by Side Comparison

In the end, if time is money the findings show that it would be logical to use ASP.NET.  In many cases, this could be attributed to Visual Studio as an excellent development tool.  The intellisense available in VS is very different and far better from almost ever other tool/editor I have used.

To add more in favor of Visual Studio being a winning tool, this screencast was completed before jQuery began shipping with Visual Studio.  jQuery has transformed the JavaScript world, and coupled with beefed up support for JavaScript intellisense in Visual Studio 2008, development time is cut down dramitically.  

One can argue over intricacies of the languages, however, the speed of C# and RAD capabilities in Visual Studio make the VS/.NET combo a robust and rapid web development platform.

And I Digress…

While slightly off topic, this also serves a nice message to Adobe.  Flex is a step in the right direction, but Visual Studio 2008 is a far better development tool than Flex Builder is in its wildest dreams.  If Silverlight begins to get better market penetration, Adobe will be forced to innovate, and perhaps Microsoft would even create a development tool for Mac.  The reality is, Flex will have the Mac market so long as Visual Studio is Windows only.  If Adobe is to keep their choke hold on the RIA market for years to come, they need to take some lessons from VS2008.

Oct 29 2008

Heading off to <head>


Tomorrow is the start of the <head> conference, and yes I am lame and used <head> as a pun.

Earlier this week I was somewhat unsure of how everything was going to shape up.  After all, I have never been to an online conference.  Upon looking at some of the sessions lined up today I was pretty stoked.  On an equally positive note, how awesome is it not to have to fly anywhere, stay at an overpriced hotel, or pay an exorbitant amount to attend a 3-day sales pitch.

<head> looks like it is shaping up to eliminate all of those headaches.  If you haven’t had a chance check it out, it can’t hurt for $149.

Official website:

Oct 23 2008

RIA Myth Busting: Back Button, History, and SEO


I have touched on the topic of SEO in the past, however, that article the focused on a broad range of ideas to improve organic search.  I wanted to focus in on realities surrounding RIAs and commonly requested features, specifically to the combination of back button support, bookmarking, and search engine optimization.  All of these features would be wonderful in a single page interface, and with current technology and methodology, is it possible to have our cake and eat it too?

It is important to first have an understanding of the difference in objectives between a web application and a web site.  (Technically speaking, most web sites are web applications, but we are using the term in a looser sense).  Typical examples of an application in this scope would be GMail, Google Reader, and the user section of – sites with almost no need of searchable content.  Examples from the opposite end of the spectrum would be Bloomberg, A List Apart, Wired, and someone’s blog.  Therefore, we have two camps, one where the sole focus is on interaction with data and no search strategy is needed and the other dictates a solid search strategy.

A method that has been gaining steam in the RIA world is using a hash sign (#), or anchor, in the URL.  Many talented people have spent precious time creating solutions to history and back button support for AJAX and Flash applications.  This is fantastic for a web application, because it provides capability for standard user interactions supported in browsers that are typically unsupported in rich internet applications.

So now that there is history support, does that mean SEO has been fully considered?  An article I found on sheds some light on the subject using a CNN video player as a case study:

CNN uses links like the above for all the topical video segments that are published on its site. The URL in this case has the following components:

Component Value
Protocol http
Path video
Client Param #/video/tech/2008/02/19/vo.aus.sea.spider.ap

2.1.1 Things To Note

The browser is expected to do a GET of the URL leading up to the fragment, and the processing application, in this case, the JavaScript embedded in the HTML Response processes the portion of the URL following the #.
The fragment identifier has been intentionally identified as a client parameter.
Treating it as a regular fragment identifier in this usage would result in one incorrectly infering that the URL for the video resource being addressed is
This would result in all the video links on the CNN site getting the same URL.
Thus, the entire URL in this case is
A consumer of this URL who goes looking for an idwithin the Response that matches the #-suffix of this URL will fail.
The reported Content-Type for the resource is text/html. However the behavior of the #-suffix in this case is not defined by the HTML specification.
As used, the #-suffix is a first-class client parameter in that it gets consumed by a script that is served as part of the HTML document returned by the server upon receiving a GET request.
This embedded script examines the URL available to it as script variable content.location, strips off the # and uses the rest of the prefix as an argument to function that generates the actual URL.
Having constructed this content URL, the script then proceeds to instruct the browser to play the media at the newly constructed location.

Notice that “the browser is expected to do a GET of the URL leading up to the fragment…JavaScript embedded in the HTML Response processes the portion of the URL following the #.”  To paraphrase, Google does not look at client side interactions, the fragment is truncated from Google’s index.  From this several assumptions can be made:

  1. Any back link using is actually viewed as
  2. Back links pointing to URL fragments will have no individual page rank.
  3. In content rich scenarios, the use of URL fragments in leu of separate pages effectively dilutes almost all search traction.

Reflecting on how Google treats URL fragments, it can be clearly seen that a single page interface is not an effective strategy in scenarios with rich content.  Another big myth around single page interfaces is in the use of Flash, SWFAddress and/or Flex’s history manager.  Google will disregard URL fragments, the very foundation of SWFAddress and Flex’s history manager.  To reiterate, Googlebot just disregarded the URLs you have just crafted with SWFAddress.  It should be stated that some individuals wholeheartedly believe that using URL fragments is a successful SEO strategy.  Yet, when Google is typically the number one returning visitor, do you really want to take a chance at questioning the very foundation Google uses to spider your site?

Take for instance a designer’s personal site with tabs for Home, Resume, Portfolio, and Contact.  Would the designer want to implement a single page interface?  The answer would likely be no.  The content would gain more traction if it is separated properly.  To rehash the example of Google Reader, a single page interface is a good choice, for Google Reader would not benefit from having a separate page for each feed a user is subscribed to.

The advances made in RIA with regard to history and back button support encapsulate the innovative spirit that the web has embraced.  However, web workers tend to jump on bandwagons and this filters down to individuals with the power to poorly implement a technology – remember Flash intro pages?  Much like a seasoned web worker becomes very business and client savvy after years in the field, we need to be Google savvy.  Threfore, next time a wirefrime for a single page interface lands your desk, does the content dictate a search strategy?  If so, do some research on the reality of the solutions and ultimateley be kind to Google and Google will be kind to you.

Oct 22 2008

« Older Entries

Newer Entries »