<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Technology Innovation from Strategic Direction</title>
    <link>http://strategicdirection.mypublicsquare.com/</link>
    <pubDate>Mon, 28 Apr 2008 05:40:59 GMT</pubDate>
    <description>Stories on Technology Innovation from Strategic Direction</description>
    <item>
      <title>Help Wanted</title>
      <link>http://strategicdirection.mypublicsquare.com/view/help-wanted</link>
      <guid>http://strategicdirection.mypublicsquare.com/view/help-wanted</guid>
      <description>You&#8217;re a web developer. You want a new job. There are a zillion choices. So where do you begin your search?

For those of us that chose web development as a career path some time ago, the evolution of web sites from simple storefronts to widgets and rich applications has been particularly vindicating. For many, the growth of web development has also been quite lucrative as it&#8217;s an industry with a very low barrier to entry; no degree required, just a few visits to W3Schools, a free FTP software client, a domain to work on and you&#8217;re up and running. But running to where?

&lt;h4&gt;A Good Starting Point&lt;/h4&gt;
There are primarily two types of organizations that employ web developers&#8212;web application development firms and interactive advertising agencies. The former is concerned with using technology to build tools and innovate resources on the internet whereas the latter is concerned with using the web as a marketing channel to generate fast, demonstrable return on investment (ROI). Having worked at both, I&#8217;ve experienced the difference in climate and culture firsthand, and seen some noteworthy themes emerge. These themes are important because they can help provide guidance to the aspiring developer and make sure that there is an alignment between 1) the aspects of a job that the individual finds fulfilling and 2) the kind of skills and behaviors that the organization needs to be competitive in its industry. 
&lt;br&gt;
This is the career insight I wish I had a decade ago when I was faced with the question, &#8220;Where should I work?&#8221;
&lt;br&gt;
&lt;h4&gt;Interactive Advertising&lt;/h4&gt;&lt;h5&gt;Environment&lt;/h5&gt;
Fast-paced and aggressive, interactive ad agencies are home to a mix of excitement and chaos.  They will test a developer&#8217;s talent and as well as her resolve. The timelines are tight, the clients are demanding, and agencies typically emphasize aesthetics over functionality. Necessity isn&#8217;t just the mother of invention here, necessity is the only thing that justifies the time spent inventing.  You probably won&#8217;t find any learning laboratories in the office space, but you will beef up your portfolio rapidly with highly recognized brand names and ultra-cool campaigns. Finally, the fundamental tenets of software development are alien to agencies (i.e., requirements definition, information architecture, version control).
&lt;br&gt;

Some examples of well-known interactive agencies include G2 Interactive, Avenue A Razorfish, and Ogilvy Interactive.

&lt;h5&gt;Skills Emphasized&lt;/h5&gt;
Versatility is the name of the game. Agency developers must wear a lot of hats and feel comfortable multi-tasking on a range of projects simultaneously. There is never a shortage of work, never a dull moment, and rarely a moment of free time. It&#8217;s a clock-watcher&#8217;s heaven&#8212;the days go by very quickly and the weekends arrive in no time. Knowledge acquired at an agency is usually broad and shallow.
&lt;br&gt;

Creative professionals expect &#8220;pixel perfection&#8221;. They want their graphical designs cut-up and coded to look precisely the way they do in comps. They don&#8217;t want to hear about browser compatibility issues, semantic integrity, or CSS 3.0. That is why mastery of presentational skills such as CSS is key to success in this industry. Developers that show a knack for layout tricks and design will find themselves in leadership roles pretty quickly, acting as mentors to others. Interactive advertising was slow to adopt standards-based design (&#8220;table-less&#8221; web development), so many agencies regard developers with this skill set as gurus and will pay a higher price for their expertise. 

Remember DHTML? Often mistakenly referred to as its close relative AJAX, DHTML skills are a handy weapon in the web developer&#8217;s arsenal. Frequently, advertising customers will ask for a user experience design that calls for some kind of JavaScript function and, though many functions and libraries are just search engine away, devs can save a lot of time with existing knowledge in this area. And remember: time is of the essence.

A decent understanding of Search Engine Optimization (SEO) doesn&#8217;t hurt. Using search engines as a means to market web content exploded in the past few years, and web developers are on the front lines of executing tactical recommendations. 

&lt;h4&gt;Web Application Development&lt;/h4&gt;&lt;h5&gt;Environment&lt;/h5&gt;
Rational and deliberate, web application development firms go through iterative cycles to produce and continuously improve software tools for the Internet. They adhere to the principle that &#8220;haste makes waste&#8221; and work within a well-defined software development methodology. Web app companies foray into more sophisticated, database-driven technology environments, where components like data entity relationship diagrams, web services integration, and application programming interfaces (APIs) are part of the standard vernacular. These kinds of organizations make their living on continuous innovation and are therefore more likely to invest time and money toward the creation of big, hairy, audacious frameworks by which to extend existing products with new ideas.

Some examples of well-known web application development firms include Mozilla, Facebook, Google, and 37signals.

&lt;h5&gt;Skills Emphasized&lt;/h5&gt;
Skills specialization is prevalent. Web applications are usually developed in separate tiers, clearly separating concerns between database administration, business logic, UI structure, and layout &amp; presentation. It is not uncommon to find a firm that employs a &#8220;graphic design guy&#8221;, an &#8220;UI guy&#8221;, a &#8220;JavaScript/behavior guy&#8221;, an &#8220;application developer guy&#8221;, and a &#8220;database administrator guy&#8221; (or gal). So developers in these companies wear one hat and wear it very well. In other words, unlike agencies, knowledge acquired at application development firm is usually deep and narrow.
&lt;br&gt;

AJAX lives here. Client-side data processing and asynchronous server requests have become a convention in user interface design because they make interactions with websites feel more intuitive and desktop-ish. AJAX is also a helpful term for hiring managers to use as a filter on a job-related resume search.

Form fields abound, so it helps to know your way around the functionality and presentation quirks involved with these elements. Particularly crafty developers will employ all sorts of homemade alternatives to traditional form fields, with clever use of anchors and JavaScript functions.

Unit testing pays off. Quality assurance reigns supreme in app development. Developers that can check their own work get farther faster.

&lt;h4&gt;That&#8217;s It?&lt;/h4&gt;
So is that all you need to consider in taking the next step on your job hunt? 

No. 

It goes without saying that there are multitudes of other factors that should weigh in your ultimate career decision, but it is helpful to be cognizant of the more salient aspects of the industry that your stepping into. The extent to which these aspects are consistent with your working style and provide opportunities for you to grow and excel will play a central role in your overall contentment (or frustration) in your daily life at work. And that&#8217;s what it&#8217;s all about&#8212;trying to achieve a little bit of zen on the job.

&lt;h5&gt;Bio&lt;/h5&gt; 
Walter Stevenson is an Executive Producer at Ignite Health, an Inventiv Health company that specializes in interactive advertising for the healthcare industry. He is the proud author of the Task microformat draft specification and maintains a personal web site at www.walterstevenson.com.

</description>
      <pubDate>Mon, 28 Apr 2008 05:40:59 GMT</pubDate>
      <author></author>
      <category>Marketing &amp; Communications</category>
      <category>Technology Innovation</category>
    </item>
    <item>
      <title>Practice Makes Perfect</title>
      <link>http://strategicdirection.mypublicsquare.com/view/practice-makes</link>
      <guid>http://strategicdirection.mypublicsquare.com/view/practice-makes</guid>
      <description>&lt;p&gt;No web site is perfect. For that matter, no development team, management methodology or project workflow is perfect either. Cosmic forces are working against us to keep projects firmly rooted in the real world, reminding us that our lofty ideals are simply unachievable. Does that mean we stop striving? No (well, most of us don&#8217;t). We push for excellence because we know that if we fall just short of it, we&#8217;re still in pretty good shape. Doing a good job is not just important for keeping customers happy, but it gives our work and our life more meaning. For interactive agencies, doing a great job translates to developing with best practices. But what are best practices? According to California State University (2006), best practices are &#8220;processes and activities that have been shown in practice to be the most effective.&#8221; In other words, &#8216;doing a great job&#8217;! For web developers, doing a great job typically means building solutions that are:&lt;/p&gt;    &lt;p&gt;* Easy to maintain
* Easy to find
* Easy to use&lt;/p&gt;    &lt;p&gt;To achieve these goals, development teams have finally started warming up to the following practices because have shown consistent effectiveness over time. The concepts aren&#8217;t new, but widespread adoption would be.&lt;/p&gt;    &lt;p&gt;h2. Separate concerns.&lt;/p&gt;    &lt;p&gt;The main concept behind separating concerns is to reduce dependencies between an application&#8217;s different features and functions, as well as the dependencies between the people who administer these different aspects of the application. You&#8217;ve probably heard the terms &#8220;presentation layer&#8221; or &#8220;data tier&#8221; before. Jesse James Garret offers &lt;a href="http://www.jjg.net/elements/pdf/elements_ch02.pdf"&gt;this accurate breakdown of concerns&lt;/a&gt; as a &lt;span class="caps"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;PDF&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; on the elements of user experience. &lt;a href="http://www.alistapart.com/articles/separationdilemma"&gt;This &amp;#8220;Separation Anxiety&amp;#8221; article&lt;/a&gt; introduces the idea of separation of concerns from the perspective of the developer.&lt;/p&gt;    &lt;p&gt;h2. Optimize content.&lt;/p&gt;    &lt;p&gt;Web site users and search engines are after the same thing&#8212;relevant content. In &lt;a href="http://www.alistapart.com/articles/accessibilityseo"&gt;this &lt;span class="caps"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;&lt;span class="caps"&gt;ALA&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; article&lt;/a&gt;, Andy Hagans describes how to leverage accessible content for optimization efforts. In &lt;a href="http://www.alistapart.com/articles/seo"&gt;this complimentary article&lt;/a&gt;, the author explores some of the specifics of execution.&lt;/p&gt;    &lt;p&gt;h2. Design with web standards.&lt;/p&gt;    &lt;p&gt;The Web Standards Project provides &lt;a href="http://www.webstandards.org/learn/faq/#p1"&gt;this informative introduction&lt;/a&gt; to the topic of designing with web standards. Additionally, Jeffery Zeldman&#8217;s Happy Cog Studios offers &lt;a href="http://happycog.com/lectures/dwws/"&gt;this great presentation&lt;/a&gt;, putting web standards into a rich historical context.&lt;/p&gt;    &lt;p&gt;h3. What&#8217;s your take?&lt;/p&gt;    &lt;p&gt;Does your organization take web standards seriously? Are best practices considered a newfangled concept, a nice-to-have item, a competitive differentiator or a virtual necessity for survival in today&#8217;s dynamic web?&lt;/p&gt;    &lt;p&gt;&lt;strong&gt;*&lt;/strong&gt;&lt;/p&gt;    &lt;p&gt;&lt;b&gt;References&lt;/b&gt;&lt;br /&gt;California State University. 2006. Retrieved on December 19, 2006 from &lt;a href="http://it.csumb.edu/departments/data/glossary.html"&gt;http://it.csumb.edu/departments/data/glossary.html&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Wed, 28 Mar 2007 02:03:28 GMT</pubDate>
      <author>Walter Stevenson</author>
      <category>Technology Innovation</category>
    </item>
  </channel>
</rss>
