<?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>TDickerson Technologies</title>
	<atom:link href="http://tdickerson.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://tdickerson.com</link>
	<description>Where I.T. Matters</description>
	<lastBuildDate>Fri, 27 Apr 2012 02:31:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>The Vendor Prefix Predicament: ALA’s Eric Meyer Interviews Tantek Çelik</title>
		<link>http://tdickerson.com/2012/02/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/</link>
		<comments>http://tdickerson.com/2012/02/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 13:00:52 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/</guid>
		<description><![CDATA[During a public meeting of the W3C CSS Working Group, Mozilla web standards lead Tantek Çelik precipitated a crisis in Web Standards Land when he complained about developers who misunderstand and abuse vendor prefixes by only supporting WebKit’s, thereby creating a browser monoculture. Tantek’s proposed solution—having Mozilla pretend to be WebKit—inflamed many in the standards [...]]]></description>
			<content:encoded><![CDATA[<p>During a public meeting of the W3C CSS Working Group, Mozilla web standards lead Tantek Çelik precipitated a crisis in Web Standards Land when he complained about developers who misunderstand and abuse vendor prefixes by only supporting WebKit’s, thereby creating a browser monoculture. Tantek’s proposed solution—having Mozilla pretend to be WebKit—inflamed many in the standards community, especially when representatives from Opera and Microsoft immediately agreed about the problem and announced similar plans to Mozilla’s. To get to the bottom of the new big brouhaha, exclusively for A List Apart, our Eric Meyer interviews Tantek on Mozilla’s controversial plan to support -webkit- prefixed properties.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/02/the-vendor-prefix-predicament-alas-eric-meyer-interviews-tantek-celik/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Every Time You Call a Proprietary Feature “CSS3,” a Kitten Dies</title>
		<link>http://tdickerson.com/2012/02/every-time-you-call-a-proprietary-feature-css3-a-kitten-dies/</link>
		<comments>http://tdickerson.com/2012/02/every-time-you-call-a-proprietary-feature-css3-a-kitten-dies/#comments</comments>
		<pubDate>Tue, 14 Feb 2012 13:00:34 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/every-time-you-call-a-proprietary-feature-css3-a-kitten-dies/</guid>
		<description><![CDATA[Any -webkit- feature that doesn’t exist in a specification (not even an Editor’s draft) is not CSS3. Yes, they are commonly evangelized as such, but they are not part of CSS at all. This distinction is not nitpicking. It’s important because it encourages certain vendors to circumvent the standards process, implement whatever they come up [...]]]></description>
			<content:encoded><![CDATA[<p>Any -webkit- feature that doesn’t exist in a specification (not even an Editor’s draft) is not CSS3. Yes, they are commonly evangelized as such, but they are not part of CSS at all.  This distinction is not nitpicking. It’s important because it encourages certain vendors to circumvent the standards process, implement whatever they come up with in WebKit, then evangelize it to developers as the best thing since sliced bread. In our eagerness to use the new bling, we often forget how many people fought in the past decade to enable us to write code without forks and hacks and expect it to work interoperably. Lea Verou explains why single-vendor solutions are not the same as standards and not healthy for your professional practice or the future of the web.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/02/every-time-you-call-a-proprietary-feature-css3-a-kitten-dies/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Pricing Strategy for Creatives</title>
		<link>http://tdickerson.com/2012/01/pricing-strategy-for-creatives/</link>
		<comments>http://tdickerson.com/2012/01/pricing-strategy-for-creatives/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:00:07 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/pricing-strategy-for-creatives/</guid>
		<description><![CDATA[Strategic pricing helps your brand and helps you to make more money. Issuing a price is like handing out a business card—it’s a great branding tool, but be careful about what it says to your market. Beginning relationships with customers at a high price makes the statement: “we’re good at what we do and we [...]]]></description>
			<content:encoded><![CDATA[<p>Strategic pricing helps your brand and helps you to make more money. Issuing a price is like handing out a business card—it’s a great branding tool, but be careful about what it says to your market. Beginning relationships with customers at a high price makes the statement: “we’re good at what we do and we know it.” Fighting with a competitor over a low price says “I’m uncertain about my abilities, so I’ll take what I can get.” Failing to use a considered pricing policy will leave you treading water in a sea of design mediocrity, allowing you to just stay afloat while you sell commodities. Jason Blumer explains how to become strategic about your pricing—including three things you can do immediately to kick-start your journey toward strategic pricing.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/01/pricing-strategy-for-creatives/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Responsive Images: How they Almost Worked and What We Need</title>
		<link>http://tdickerson.com/2012/01/responsive-images-how-they-almost-worked-and-what-we-need/</link>
		<comments>http://tdickerson.com/2012/01/responsive-images-how-they-almost-worked-and-what-we-need/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 12:00:05 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/responsive-images-how-they-almost-worked-and-what-we-need/</guid>
		<description><![CDATA[With a mobile-first responsive design approach, if any part of the process breaks down, your user can still receive a representative image and avoid an unnecessarily large request on a device that may have limited bandwidth. But with several newer browsers implementing an “image prefetching” feature that allows images to be fetched before parsing the [...]]]></description>
			<content:encoded><![CDATA[<p>With a mobile-first responsive design approach, if any part of the process breaks down, your user can still receive a representative image and avoid an unnecessarily large request on a device that may have limited bandwidth. But with several newer browsers implementing an  “image prefetching” feature that allows images to be fetched before parsing the document’s body, some of the web&#8217;s brightest developers are abandoning responsive images in favor of user agent detection, at least as a temporary solution. For us standardistas, UA detection leaves a bad taste in the mouth. More importantly, as the number and kinds of devices continue to grow, UA detection will quickly become untenable—just as browser detection did back in the bad old days before web standards. What&#8217;s really needed, argues Mat Marquis, is a new markup element that works the way the HTML5 video element works. Sound crazy? So crazy it just might work.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/01/responsive-images-how-they-almost-worked-and-what-we-need/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>An Important Time for Design</title>
		<link>http://tdickerson.com/2012/01/an-important-time-for-design/</link>
		<comments>http://tdickerson.com/2012/01/an-important-time-for-design/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 09:00:49 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/an-important-time-for-design/</guid>
		<description><![CDATA[Design is on a roll. Client services are experiencing a major uptick in demand, seasoned design professionals are abandoning client work in favor of entrepreneurship, and designer-co-founded startups such as Kickstarter and Airbnb are taking center stage. It’s becoming increasingly difficult to ignore the fact that design has a massive role to play in the [...]]]></description>
			<content:encoded><![CDATA[<p>Design is on a roll. Client services are experiencing a major uptick in demand, seasoned design professionals are abandoning client work in favor of entrepreneurship, and designer-co-founded startups such as Kickstarter and Airbnb are taking center stage. It’s becoming increasingly difficult to ignore the fact that design has a massive role to play in the evolution of the web and the next generation of web products. The result, says Cameron Koczon, is that designers have now been given a blank check—one that lets web designers band together as a community to change the way design is perceived; change the way products are built; and quite possibly change the world.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/01/an-important-time-for-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building Twitter Bootstrap</title>
		<link>http://tdickerson.com/2012/01/building-twitter-bootstrap/</link>
		<comments>http://tdickerson.com/2012/01/building-twitter-bootstrap/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 09:00:29 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/building-twitter-bootstrap/</guid>
		<description><![CDATA[Bootstrap is an open-source front-end toolkit created to help designers and developers quickly and efficiently build great stuff online. Its goal is to provide a refined, well-documented, and extensive library of flexible design components created with HTML, CSS, and JavaScript for others to build and innovate on. Today, it has grown to include dozens of [...]]]></description>
			<content:encoded><![CDATA[<p>Bootstrap is an open-source front-end toolkit created to help designers and developers quickly and efficiently build great stuff online. Its goal is to provide a refined, well-documented, and extensive library of flexible design components created with HTML, CSS, and JavaScript for others to build and innovate on. Today, it has grown to include dozens of components and has become the most popular project on GitHub, with more than 13,000 watchers and 2,000 forks. Mark Otto, the co-creator of Bootstrap, sheds light on how and why Bootstrap was made, the processes used to create it, and how it has grown as a design system.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/01/building-twitter-bootstrap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Pixel Identity Crisis</title>
		<link>http://tdickerson.com/2012/01/a-pixel-identity-crisis/</link>
		<comments>http://tdickerson.com/2012/01/a-pixel-identity-crisis/#comments</comments>
		<pubDate>Tue, 17 Jan 2012 09:00:03 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/a-pixel-identity-crisis/</guid>
		<description><![CDATA[The pixel has long been the atomic particle of screen based design: a knowable, concrete unit of measurement. But layouts based on the hardware pixel are fast becoming an endangered species. Even the introduction of a new, W3C standard reference pixel, although it promises stability in the long-term, can&#8217;t help us navigate the current chaos. [...]]]></description>
			<content:encoded><![CDATA[<p>The pixel has long been the atomic particle of screen based design: a knowable, concrete unit of measurement. But layouts based on the hardware pixel are fast becoming an endangered species. Even the introduction of a new, W3C standard reference pixel, although it promises stability in the long-term, can&#8217;t help us navigate the current chaos. Consider the two &#8220;standard&#8221; pixel definitions and 500 &#8220;standard&#8221; viewports your user&#8217;s Android device may support. To create designs that transcend platform differences—the promise of the web and standards—you must normalize pixels across devices. Scott Kellum shows how math and media queries can keep you sane and help you design consistently across platforms.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2012/01/a-pixel-identity-crisis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What I Learned About the Web in 2011</title>
		<link>http://tdickerson.com/2011/12/what-i-learned-about-the-web-in-2011/</link>
		<comments>http://tdickerson.com/2011/12/what-i-learned-about-the-web-in-2011/#comments</comments>
		<pubDate>Tue, 13 Dec 2011 07:00:26 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://tdickerson.com/blog/what-i-learned-about-the-web-in-2011/</guid>
		<description><![CDATA[As the year draws to a close, we asked some A List Apart readers to tell us what they learned about the web in 2011. Together their responses summarize the joys and challenges of this magical place we call the internet. We need to continue to iterate, to embrace change, and challenge complexity to keep [...]]]></description>
			<content:encoded><![CDATA[<p>As the year draws to a close, we asked some A List Apart readers to tell us what they learned about the web in 2011. Together their responses summarize the joys and challenges of this magical place we call the internet.  We need to continue to iterate, to embrace change, and challenge complexity to keep shipping.  Above all, we must continue to reach out to one another, to teach, to support, to help, and to build the community that sustains us.</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2011/12/what-i-learned-about-the-web-in-2011/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>slider 2</title>
		<link>http://tdickerson.com/2011/12/slider-2/</link>
		<comments>http://tdickerson.com/2011/12/slider-2/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 22:04:50 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[slider]]></category>

		<guid isPermaLink="false">http://tdickerson.com/?p=68371</guid>
		<description><![CDATA[test2]]></description>
			<content:encoded><![CDATA[<p>test2</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2011/12/slider-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>slider 1</title>
		<link>http://tdickerson.com/2011/12/slider-1/</link>
		<comments>http://tdickerson.com/2011/12/slider-1/#comments</comments>
		<pubDate>Wed, 07 Dec 2011 22:03:59 +0000</pubDate>
		<dc:creator>thomas</dc:creator>
				<category><![CDATA[slider]]></category>

		<guid isPermaLink="false">http://tdickerson.com/?p=68369</guid>
		<description><![CDATA[test]]></description>
			<content:encoded><![CDATA[<p>test</p>
]]></content:encoded>
			<wfw:commentRss>http://tdickerson.com/2011/12/slider-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

