<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jpcody)</title>
    <link>https://pinboard.in/u:jpcody/public/</link>
    <description>recent bookmarks from jpcody</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://kellegous.com/j/2013/02/27/innertext-vs-textcontent/"/>
	<rdf:li rdf:resource="http://code.flickr.net/2013/06/04/adventures-in-jank-busting-parallax-performance-and-the-new-flickr-home-page/"/>
	<rdf:li rdf:resource="http://rubylearning.com/blog/2013/06/19/how-do-i-benchmark-ruby-code/"/>
	<rdf:li rdf:resource="http://www.smashingmagazine.com/2013/06/10/pinterest-paint-performance-case-study/"/>
	<rdf:li rdf:resource="http://blog.pamelafox.org/2013/06/improving-backbone-app-performance.html"/>
	<rdf:li rdf:resource="http://www.leebrimelow.com/native-methods-jquery/"/>
	<rdf:li rdf:resource="http://devo.ps/blog/2013/03/06/troubleshooting-5minutes-on-a-yet-unknown-box.html"/>
	<rdf:li rdf:resource="http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2012/record-examine-fix/"/>
	<rdf:li rdf:resource="http://loadreport.wesleyhales.com/"/>
	<rdf:li rdf:resource="http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html"/>
	<rdf:li rdf:resource="https://developer.mozilla.org/en/JavaScript/Memory_Management"/>
	<rdf:li rdf:resource="https://developers.google.com/chrome-developer-tools/docs/heap-profiling"/>
	<rdf:li rdf:resource="http://gent.ilcore.com/2012/04/optimizing-with-timeline-panel.html"/>
	<rdf:li rdf:resource="http://www.webperformancetoday.com/2012/02/28/4-awesome-slides-showing-how-page-speed-correlates-to-business-metrics-at-walmart-com/"/>
	<rdf:li rdf:resource="http://www.stevesouders.com/blog/2012/02/10/the-performance-golden-rule/"/>
	<rdf:li rdf:resource="http://perfectionkills.com/profiling-css-for-fun-and-profit-optimization-notes/"/>
	<rdf:li rdf:resource="http://calendar.perfplanet.com/2011/advice-on-trusting-advice/"/>
	<rdf:li rdf:resource="http://redbot.org/"/>
	<rdf:li rdf:resource="http://www.wordsbyf.at/2011/11/23/selectors-selectoring/"/>
	<rdf:li rdf:resource="https://github.com/zgrossbart/jslim#readme"/>
	<rdf:li rdf:resource="http://gent.ilcore.com/2011/08/finding-memory-leaks.html"/>
	<rdf:li rdf:resource="http://www.ebaytechblog.com/2011/07/12/data-uri-sprites/"/>
	<rdf:li rdf:resource="http://www.html5rocks.com/tutorials/speed/html5/"/>
	<rdf:li rdf:resource="http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html"/>
	<rdf:li rdf:resource="http://pmuellr.github.com/weinre/"/>
	<rdf:li rdf:resource="http://loads.in/"/>
	<rdf:li rdf:resource="https://github.com/andyedinborough/stress-css"/>
	<rdf:li rdf:resource="http://pinboard.in/blog/173/"/>
	<rdf:li rdf:resource="http://net.tutsplus.com/articles/lectures/the-top-5-mistakes-of-massive-css/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader"/>
	<rdf:li rdf:resource="http://claude.betancourt.us/compress-javascript-and-css-as-part-of-your-build-process/"/>
	<rdf:li rdf:resource="http://www.garann.com/dev/2010/a-healthy-level-of-distrust/"/>
	<rdf:li rdf:resource="http://weightshift.com/memo/making-client-sites-faster"/>
	<rdf:li rdf:resource="http://www.slideshare.net/paul.irish/perfcompression"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/972757/yuicompressor-or-similar-in-php"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://kellegous.com/j/2013/02/27/innertext-vs-textcontent/">
    <title>kelly norton: innerText vs. textContent</title>
    <dc:date>2013-09-14T21:21:45+00:00</dc:date>
    <link>http://kellegous.com/j/2013/02/27/innertext-vs-textcontent/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Why does innerText require layout? I ended with that question in my previous post about layout thrashing. Just to recap briefly, there are very common patterns of use in the DOM APIs that cause terrible performance due to unnecessary layout. These posts highlight some of the oddities that I’ve found working on web performance for several years.

]]></description>
<dc:subject>html performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:71d8952629d3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://code.flickr.net/2013/06/04/adventures-in-jank-busting-parallax-performance-and-the-new-flickr-home-page/">
    <title>Adventures in Jank Busting: Parallax, performance, and the new Flickr Home Page | code.flickr.com</title>
    <dc:date>2013-07-01T03:13:32+00:00</dc:date>
    <link>http://code.flickr.net/2013/06/04/adventures-in-jank-busting-parallax-performance-and-the-new-flickr-home-page/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>performance javascript animation</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:85a3bc8e2b28/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:animation"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rubylearning.com/blog/2013/06/19/how-do-i-benchmark-ruby-code/">
    <title>How do I benchmark Ruby code?</title>
    <dc:date>2013-06-21T11:37:26+00:00</dc:date>
    <link>http://rubylearning.com/blog/2013/06/19/how-do-i-benchmark-ruby-code/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[o you’ve got some Ruby code and you want to make it faster. Maybe you’ve already got a new implementation in mind, or maybe you’re still cooking that up. But how do you make certain that your new implementation is faster?

]]></description>
<dc:subject>ruby performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6d105bfd4be8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.smashingmagazine.com/2013/06/10/pinterest-paint-performance-case-study/">
    <title>Gone In 60 Frames Per Second: A Pinterest Paint Performance Case Study | Smashing Magazine</title>
    <dc:date>2013-06-17T00:02:42+00:00</dc:date>
    <link>http://www.smashingmagazine.com/2013/06/10/pinterest-paint-performance-case-study/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Today we’ll discuss how to improve the paint performance of your websites and Web apps. This is an area that we Web developers have only recently started looking at more closely, and it’s important because it could have an impact on your user engagement and user experience.
]]></description>
<dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:832aa239e64e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.pamelafox.org/2013/06/improving-backbone-app-performance.html">
    <title>Improving Backbone App Performance</title>
    <dc:date>2013-06-07T19:28:29+00:00</dc:date>
    <link>http://blog.pamelafox.org/2013/06/improving-backbone-app-performance.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I figured, hey, maybe there were frontend improvements that we could make too. Here's what I did and what I learnt.]]></description>
<dc:subject>backbone javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6bf8a9faa36c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:backbone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.leebrimelow.com/native-methods-jquery/">
    <title>Native equivalents of jQuery functions</title>
    <dc:date>2013-05-20T13:26:42+00:00</dc:date>
    <link>http://www.leebrimelow.com/native-methods-jquery/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[If you checked out my last post you’ll know that I have been doing lots of JavaScript coding as of late, both inside and out of Brackets. I have also been doing a series of performance tests (1, 2, 3) between popular jQuery methods and their native DOM equivalents.

]]></description>
<dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:0f79917dab55/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://devo.ps/blog/2013/03/06/troubleshooting-5minutes-on-a-yet-unknown-box.html">
    <title>First 5 Minutes Troubleshooting A Server | devo.ps</title>
    <dc:date>2013-03-12T20:02:24+00:00</dc:date>
    <link>http://devo.ps/blog/2013/03/06/troubleshooting-5minutes-on-a-yet-unknown-box.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Back when our team was dealing with operations, optimization and scalability at our previous company, we had our fair share of troubleshooting poorly performing applications and infrastructures of various sizes, often large (think CNN or the World Bank). Tight deadlines, “exotic” technical stacks and lack of information usually made for memorable experiences.

]]></description>
<dc:subject>server performance devops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5a63561e465c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:server"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:devops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack">
    <title>High Performance Networking in Google Chrome - igvita.com</title>
    <dc:date>2013-03-10T14:08:55+00:00</dc:date>
    <link>http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Chrome's network stack is, quite literally, getting smarter every day, trying to hide or decrease the latency cost of each resource: it learns likely DNS lookups, it remembers the topology of the web, it preconnects to likely destination targets, and more. ]]></description>
<dc:subject>chrome browsers performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:c030735ac2e8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:browsers"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2012/record-examine-fix/">
    <title>Performance Calendar » Record, Examine, Fix</title>
    <dc:date>2012-12-20T16:07:18+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2012/record-examine-fix/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Being aware of how to measure and improve performance can be a useful skill and in this short post, I’ll give you a quick refresher on how this can be done with the Chrome DevTools Timeline and Profiles.


]]></description>
<dc:subject>javascript performance chrome devtools</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:9b1f2ec5cb75/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:devtools"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://loadreport.wesleyhales.com/">
    <title>Loadreport.js</title>
    <dc:date>2012-09-05T19:45:44+00:00</dc:date>
    <link>http://loadreport.wesleyhales.com/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This handy little script uses phantomjs to build a report of DOM and resource load times. The reports are created one-at-a-time to deliver the most accurate results - that's why it takes a few seconds.]]></description>
<dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:0dc56ebda683/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html">
    <title>Fastersite: How (not) to trigger a layout in WebKit</title>
    <dc:date>2012-06-25T01:54:31+00:00</dc:date>
    <link>http://gent.ilcore.com/2011/03/how-not-to-trigger-layout-in-webkit.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This often leaves developers asking the question: What triggers layout? Last week Dimitri Glazkov answered this question with this codesearch link. Trying to understand it better myself, I went through and translated it into a list of properties and methods. Here they are:]]></description>
<dc:subject>performance javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6e4c13867814/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developer.mozilla.org/en/JavaScript/Memory_Management">
    <title>Memory Management - MDN</title>
    <dc:date>2012-04-30T12:09:24+00:00</dc:date>
    <link>https://developer.mozilla.org/en/JavaScript/Memory_Management</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Low-level languages, like C, have low-level memory management primitives like malloc() and free(). On the other hand, JavaScript values are allocated when things (objects, strings, etc.) are created and "automatically" free'd when they are not used anymore. The latter process is called garbage collection. This "automatically" is a source of confusion and gives JavaScript (and high-level languages) developers the impression they can decide not to care about memory management. This is a mistake.

]]></description>
<dc:subject>javascript memory performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:9dacf883e534/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:memory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://developers.google.com/chrome-developer-tools/docs/heap-profiling">
    <title>Chrome Developer Tools: Heap Profiling - Chrome Developer Tools — Google Developers</title>
    <dc:date>2012-04-25T01:19:58+00:00</dc:date>
    <link>https://developers.google.com/chrome-developer-tools/docs/heap-profiling</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This tutorial explains how to use the Heap Profiler for uncovering memory leaks in your applications.]]></description>
<dc:subject>javascript memory chrome performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e2f568547d6b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:memory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gent.ilcore.com/2012/04/optimizing-with-timeline-panel.html">
    <title>Fastersite: Optimizing with the timeline panel</title>
    <dc:date>2012-04-25T01:11:18+00:00</dc:date>
    <link>http://gent.ilcore.com/2012/04/optimizing-with-timeline-panel.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA["I know I should look at Chrome's Timeline panel, but what do I do with it?"]]></description>
<dc:subject>chrome javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:3687cbf6f40e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.webperformancetoday.com/2012/02/28/4-awesome-slides-showing-how-page-speed-correlates-to-business-metrics-at-walmart-com/">
    <title>4 awesome slides showing how page speed correlates to business metrics at Walmart.com</title>
    <dc:date>2012-02-29T22:50:26+00:00</dc:date>
    <link>http://www.webperformancetoday.com/2012/02/28/4-awesome-slides-showing-how-page-speed-correlates-to-business-metrics-at-walmart-com/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[File this presentation under “I wish I’d been there in person.” Cliff Crocker, Aaron Kulick, and Balaji Ram joined forces at February’s SF Web Performance Meetup to tell a RUM (real user monitoring) story through the lens of three job functions at Walmart.com: the performance data analyst, the developer, and the business analyst.

]]></description>
<dc:subject>performance metrics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:b45cdc211f53/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:metrics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.stevesouders.com/blog/2012/02/10/the-performance-golden-rule/">
    <title>the Performance Golden Rule | High Performance Web Sites</title>
    <dc:date>2012-02-20T06:52:09+00:00</dc:date>
    <link>http://www.stevesouders.com/blog/2012/02/10/the-performance-golden-rule/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[80-90% of the end-user response time is spent on the frontend. 
]]></description>
<dc:subject>performance speed</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:0722f76ed9fe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:speed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://perfectionkills.com/profiling-css-for-fun-and-profit-optimization-notes/">
    <title>Perfection kills » Profiling CSS for fun and profit. Optimization notes.</title>
    <dc:date>2012-01-09T20:59:58+00:00</dc:date>
    <link>http://perfectionkills.com/profiling-css-for-fun-and-profit-optimization-notes/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I’ve been recently working on optimizing performance of a so-called one-page web app. The application was highly dynamic, interactive, and was heavily stuffed with new CSS3 goodness. I’m not talking just border-radius and gradients. It was a full stack of shadows, gradients, transforms, sprinkled with transitions, smooth half-transparent colors, clever pseudo-element -based CSS tricks, and experimental CSS features.

]]></description>
<dc:subject>css performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:fcc79f3db7ad/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://calendar.perfplanet.com/2011/advice-on-trusting-advice/">
    <title>Performance Calendar » Advice on Trusting Advice</title>
    <dc:date>2012-01-03T14:27:03+00:00</dc:date>
    <link>http://calendar.perfplanet.com/2011/advice-on-trusting-advice/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[But using SSL, just for the fun of it, is not a good idea. SSL impacts web performance negatively in several ways:

]]></description>
<dc:subject>performance ssl</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:754e1bd21190/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ssl"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://redbot.org/">
    <title>REDbot: &lt;&gt;</title>
    <dc:date>2011-12-26T00:12:52+00:00</dc:date>
    <link>http://redbot.org/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>performance http</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:69bf23b9becb/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:http"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.wordsbyf.at/2011/11/23/selectors-selectoring/">
    <title>selectors selectoring</title>
    <dc:date>2011-12-21T23:42:11+00:00</dc:date>
    <link>http://www.wordsbyf.at/2011/11/23/selectors-selectoring/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This article is my attempt at explaining what is going on at a high-level when you do $(). The code samples below are largely simplified from the actual jQuery/Sizzle source. If you find any inaccuracies or a point you would like further clarified, please let me know on twitter! Thanks!]]></description>
<dc:subject>javascript performance jquery</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:aba352259bea/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:jquery"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/zgrossbart/jslim#readme">
    <title>zgrossbart/jslim - GitHub</title>
    <dc:date>2011-09-14T14:30:34+00:00</dc:date>
    <link>https://github.com/zgrossbart/jslim#readme</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[JSlim is a JavaScript optimizer based on the Google Closure Compiler, but instead of optimizing your code it optimizes the code you use.

Most websites use JavaScript libraries like JQuery or Prototype, but they don't use the whole library. JSlim builds you a new version of your favorite JavaScript library with only the code you're using.]]></description>
<dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:335c90901ed4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://gent.ilcore.com/2011/08/finding-memory-leaks.html">
    <title>Fastersite: Finding memory leaks</title>
    <dc:date>2011-09-02T17:00:51+00:00</dc:date>
    <link>http://gent.ilcore.com/2011/08/finding-memory-leaks.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[For traditional pages where the user is encouraged to navigate from page to page, memory leaks should almost never be a problem. However, for any page that encourages interaction, memory management must be considered. Most realize that ultimately if too much memory is consumed the page will be killed, forcing the user to reload it. However, even before all memory is exhausted performance problems arise:
]]></description>
<dc:subject>javascript memory performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:f38ab6f820bc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:memory"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ebaytechblog.com/2011/07/12/data-uri-sprites/">
    <title>Data URI Sprites — eBay Tech Blog</title>
    <dc:date>2011-07-18T14:18:30+00:00</dc:date>
    <link>http://www.ebaytechblog.com/2011/07/12/data-uri-sprites/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[When brainstorming alternatives, we found what seemed to be an obvious solution: the image Data URI scheme. It works in all major browsers (except IE6 and IE7), and it solves our problem of too many HTTP calls. The code looks like this:

]]></description>
<dc:subject>performance css datauri</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:85233c4b1fae/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:datauri"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.html5rocks.com/tutorials/speed/html5/">
    <title>HTML5 Rocks - Improving the Performance of your HTML5 App</title>
    <dc:date>2011-05-30T14:44:14+00:00</dc:date>
    <link>http://www.html5rocks.com/tutorials/speed/html5/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This article will try to give you the tools and techniques to work on improving the experience of your own application.

]]></description>
<dc:subject>html5 javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:7953a43a8951/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html">
    <title>Coding Horror: Working with the Chaos Monkey</title>
    <dc:date>2011-05-30T14:02:17+00:00</dc:date>
    <link>http://www.codinghorror.com/blog/2011/04/working-with-the-chaos-monkey.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[One of the first systems our engineers built in AWS is called the Chaos Monkey. The Chaos Monkey’s job is to randomly kill instances and services within our architecture. If we aren’t constantly testing our ability to succeed despite failure, then it isn’t likely to work when it matters most – in the event of an unexpected outage.

]]></description>
<dc:subject>programming failure performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:8c580aa05b0d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pmuellr.github.com/weinre/">
    <title>weinre - Home</title>
    <dc:date>2011-05-27T19:13:59+00:00</dc:date>
    <link>http://pmuellr.github.com/weinre/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[It's a debugger for web pages, like FireBug (for FireFox) and Web Inspector (for WebKit-based browsers), except it's designed to work remotely, and in particular, to allow you debug web pages on a mobile device such as a phone.

]]></description>
<dc:subject>webkit iphone mobile performance debugger</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:df6a1273a9b2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:webkit"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:iphone"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:mobile"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:debugger"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://loads.in/">
    <title>loads.in - test how fast a webpage loads in a real browser from over 50 locations worldwide</title>
    <dc:date>2011-05-27T19:12:20+00:00</dc:date>
    <link>http://loads.in/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[How fast does your webpage load?

]]></description>
<dc:subject>performance speed</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:a19e6c8aa1c5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:speed"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/andyedinborough/stress-css">
    <title>andyedinborough/stress-css - GitHub</title>
    <dc:date>2011-05-02T15:39:00+00:00</dc:date>
    <link>https://github.com/andyedinborough/stress-css</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[It indexes all the elements and their classes, and then--class by class--it removes one, and times how long it takes to scroll the page. Classes that save a considerable amount of time when removed indicate problem areas.]]></description>
<dc:subject>css testing performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:7b95c46dc4e9/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:testing"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pinboard.in/blog/173/">
    <title>Anatomy of a Crushing (Pinboard Blog)</title>
    <dc:date>2011-03-13T22:02:37+00:00</dc:date>
    <link>http://pinboard.in/blog/173/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[A number of people asked about the technical aspects of the great Delicious exodus of 2010, and I've finally had some time to write it up. Note that times on all the graphs are UTC.

]]></description>
<dc:subject>architecture performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e85b94745df3/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:architecture"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://net.tutsplus.com/articles/lectures/the-top-5-mistakes-of-massive-css/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader">
    <title>The Top 5 Mistakes of Massive CSS | Nettuts+</title>
    <dc:date>2010-12-10T02:44:09+00:00</dc:date>
    <link>http://net.tutsplus.com/articles/lectures/the-top-5-mistakes-of-massive-css/?utm_source=feedburner&amp;utm_medium=feed&amp;utm_campaign=Feed%3A+nettuts+%28Nettuts%2B%29&amp;utm_content=Google+Reader</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Just because you didn’t get to go to that awesome conference doesn’t mean that you can’t still watch the lectures! Each weekend, we’ll feature a recommended web development lecture on Nettuts+.
This presentation, by Stoyan Stefanov and Nicole Sullivan, primarily details the huge performance benefits to using Object-Oriented CSS, as well as a crop of other common CSS hurdles.]]></description>
<dc:subject>oocss performance css video</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ddc2b2d129fe/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:oocss"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:video"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://claude.betancourt.us/compress-javascript-and-css-as-part-of-your-build-process/">
    <title>Compress JavaScript and CSS as Part of your Build Process — American Butifarra</title>
    <dc:date>2010-11-19T01:51:55+00:00</dc:date>
    <link>http://claude.betancourt.us/compress-javascript-and-css-as-part-of-your-build-process/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e0f654f40e7a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.garann.com/dev/2010/a-healthy-level-of-distrust/">
    <title>totes profesh» Blog Archive » a healthy level of distrust</title>
    <dc:date>2010-11-06T14:46:36+00:00</dc:date>
    <link>http://www.garann.com/dev/2010/a-healthy-level-of-distrust/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[We spend a whole lot of time making shit flashy and making it feel fast. That’s good, it provides a more pleasant user experience. But it should never be disingenuous. Sometimes it takes a second or two for an operation to complete. ]]></description>
<dc:subject>performance ux development ajax</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:4dcf95c42d05/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ux"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:development"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ajax"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://weightshift.com/memo/making-client-sites-faster">
    <title>Weightshift: Making Client Sites Faster</title>
    <dc:date>2010-11-06T14:35:38+00:00</dc:date>
    <link>http://weightshift.com/memo/making-client-sites-faster</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This past weekend, I had the opportunity to speak at WordCamp Chicago. The topic I presented, “Making WordPress Faster: Front-end Performance Tips,” was a introduction on how to analyze and speed up websites built with WordPress.]]></description>
<dc:subject>performance development</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:c6e663a2fe90/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:development"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slideshare.net/paul.irish/perfcompression">
    <title>jQuery Anti-Patterns for Performance &amp; Compression</title>
    <dc:date>2010-11-03T15:49:10+00:00</dc:date>
    <link>http://www.slideshare.net/paul.irish/perfcompression</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Paul Irish presentation on jQuery performance.]]></description>
<dc:subject>javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:b76c96127f92/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/972757/yuicompressor-or-similar-in-php">
    <title>YUICompressor or similar in PHP? - Stack Overflow</title>
    <dc:date>2010-10-15T20:09:00+00:00</dc:date>
    <link>http://stackoverflow.com/questions/972757/yuicompressor-or-similar-in-php</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Is there a decent on-the-fly JS compressor implemented in PHP? The only thing resembling this that I was able to find was Minify, but it's more of a full-blown compression solution with cache and everything. I want to keep the files separate and have the minimised files follow my own naming conventions, so Minify is a bit too complex for this purpose.

]]></description>
<dc:subject>php javascript performance</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:8d0d9cf271a0/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:php"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:performance"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>