<?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="https://medium.com/medium-eng/engineering-values-7143c0db0bd6#.sqydue8xx"/>
	<rdf:li rdf:resource="https://medium.com/@padday/meetings-e27767bcf6b6#.nzn3ypl9l"/>
	<rdf:li rdf:resource="http://firstround.com/review/this-90-day-plan-turns-engineers-into-remarkable-managers/"/>
	<rdf:li rdf:resource="https://blog.intercom.io/the-engineering-values-we-live-by/"/>
	<rdf:li rdf:resource="http://www.catehuston.com/blog/2015/12/02/technical-interview-questions-and-time-management/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed"/>
	<rdf:li rdf:resource="https://github.com/clef/handbook"/>
	<rdf:li rdf:resource="http://www.ploxiln.net/make.html"/>
	<rdf:li rdf:resource="https://gist.github.com/isaacs/62a2d1825d04437c6f08"/>
	<rdf:li rdf:resource="http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html?"/>
	<rdf:li rdf:resource="http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf"/>
	<rdf:li rdf:resource="https://blog.intercom.io/how-we-build-software/"/>
	<rdf:li rdf:resource="https://medium.com/@raffi/what-does-a-vp-of-engineering-do-again-553817fbbf2a"/>
	<rdf:li rdf:resource="https://medium.com/@gerstenzang/21-management-things-i-learned-at-imgur-7abb72bdf8bf"/>
	<rdf:li rdf:resource="https://tech.bellycard.com/blog/sass-mixins-vs-extends-the-data/"/>
	<rdf:li rdf:resource="https://42floors.com/blog/startups/thirty-percent-feedback"/>
	<rdf:li rdf:resource="http://mcfunley.com/choose-boring-technology"/>
	<rdf:li rdf:resource="http://blog.intercom.io/product-strategy-means-saying-no/"/>
	<rdf:li rdf:resource="http://sockpuppet.org/blog/2015/03/06/the-hiring-post/"/>
	<rdf:li rdf:resource="https://news.ycombinator.com/item?id=4613543"/>
	<rdf:li rdf:resource="http://blog.tjll.net/ssh-kung-fu/"/>
	<rdf:li rdf:resource="http://alistapart.com/article/creating-style-guides"/>
	<rdf:li rdf:resource="https://github.com/bensmithett/style/blob/master/Makefile"/>
	<rdf:li rdf:resource="https://gist.github.com/toolmantim/6200029"/>
	<rdf:li rdf:resource="https://algorithms.rdio.com/post/make/"/>
	<rdf:li rdf:resource="http://dev.tutsplus.com/articles/what-you-may-not-know-about-the-z-index-property--webdesign-16892"/>
	<rdf:li rdf:resource="http://blog.zachorr.com/nginx-setup/"/>
	<rdf:li rdf:resource="http://resumablejs.com/"/>
	<rdf:li rdf:resource="http://www.slashfilm.com/qa-imax-theatre-real-imax-liemax/"/>
	<rdf:li rdf:resource="https://konklone.com/post/switch-to-https-now-for-free?hn"/>
	<rdf:li rdf:resource="http://jliszka.github.io/2013/10/01/how-traffic-actually-works.html"/>
	<rdf:li rdf:resource="http://rsync.samba.org/how-rsync-works.html"/>
	<rdf:li rdf:resource="http://www.pathname.com/fhs/pub/fhs-2.3.html"/>
	<rdf:li rdf:resource="http://matthewrobertson.org/blog/2013/08/06/active-record-serializers-from-scratch/"/>
	<rdf:li rdf:resource="http://dev.opera.com/articles/view/mutation-observers-tutorial/"/>
	<rdf:li rdf:resource="http://blog.lexfriedman.com/post/2856721099/dns-servers-specific-domains"/>
	<rdf:li rdf:resource="http://kellegous.com/j/2013/02/27/innertext-vs-textcontent/"/>
	<rdf:li rdf:resource="http://fitzgeraldnick.com/weblog/50/"/>
	<rdf:li rdf:resource="http://know.cujojs.com/tutorials/aop/intro-to-aspect-oriented-programming"/>
	<rdf:li rdf:resource="http://ozkatz.github.io/converting-an-existing-backbonejs-project-to-requirejs.html"/>
	<rdf:li rdf:resource="http://www.karlgroves.com/2013/05/14/links-are-not-buttons-neither-are-divs-and-spans/"/>
	<rdf:li rdf:resource="http://davidwalsh.name/add-rules-stylesheets"/>
	<rdf:li rdf:resource="http://craig.is/killing/mice"/>
	<rdf:li rdf:resource="http://engineering.appfolio.com/2013/06/17/ruby-mixins-activesupportconcern/"/>
	<rdf:li rdf:resource="http://www.nczonline.net/blog/2013/06/25/eval-isnt-evil-just-misunderstood/"/>
	<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://chancejs.com/#true-random"/>
	<rdf:li rdf:resource="http://rubylearning.com/blog/2013/06/19/how-do-i-benchmark-ruby-code/"/>
	<rdf:li rdf:resource="http://trulia.github.io/hologram/"/>
	<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://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/"/>
	<rdf:li rdf:resource="http://www.leebrimelow.com/native-methods-jquery/"/>
	<rdf:li rdf:resource="http://blog.jcoglan.com/2013/05/08/how-ruby-method-dispatch-works/"/>
	<rdf:li rdf:resource="http://engineering.appfolio.com/2012/11/16/css-architecture/"/>
	<rdf:li rdf:resource="http://pomax.github.io/bezierinfo/"/>
	<rdf:li rdf:resource="http://substack.net/weaning_yourself_off_jquery"/>
	<rdf:li rdf:resource="http://tech.pro/tutorial/1226/basic-rubygem-development"/>
	<rdf:li rdf:resource="http://www.elasticspace.com/2013/03/no-to-no-ui"/>
	<rdf:li rdf:resource="https://github.com/dejan/rails_panel/blob/master/README.md"/>
	<rdf:li rdf:resource="http://alexsexton.com/blog/2013/03/deploying-javascript-applications/"/>
	<rdf:li rdf:resource="http://ozkatz.github.com/avoiding-common-backbonejs-pitfalls.html?tagref=js"/>
	<rdf:li rdf:resource="http://blog.martinfjordvald.com/2012/08/understanding-the-nginx-configuration-inheritance-model/"/>
	<rdf:li rdf:resource="http://www.chartjs.org/docs/"/>
	<rdf:li rdf:resource="http://stackoverflow.com/questions/12930272/javascript-closures-vs-anonymous-functions"/>
	<rdf:li rdf:resource="http://paulstamatiou.com/responsive-retina-blog-development-part-2#footnote-1"/>
	<rdf:li rdf:resource="http://blog.tinfoilsecurity.com/ruby-demystified-and-vs"/>
	<rdf:li rdf:resource="http://devo.ps/blog/2013/03/06/troubleshooting-5minutes-on-a-yet-unknown-box.html"/>
	<rdf:li rdf:resource="http://blog.martinfjordvald.com/2010/07/nginx-primer/"/>
	<rdf:li rdf:resource="http://www.igvita.com/posa/high-performance-networking-in-google-chrome/#network-stack"/>
	<rdf:li rdf:resource="http://viljamis.com/blog/2013/prototyping-responsive-typography/"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="https://medium.com/medium-eng/engineering-values-7143c0db0bd6#.sqydue8xx">
    <title>Engineering Values — Medium Engineering — Medium</title>
    <dc:date>2016-01-04T17:27:03+00:00</dc:date>
    <link>https://medium.com/medium-eng/engineering-values-7143c0db0bd6#.sqydue8xx</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[We all have value systems: what we hold true, what we consider good, what we consider to be bad. These values define how we respond to situations and how we make decisions.
]]></description>
<dc:subject>values</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:b1c503730235/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:values"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@padday/meetings-e27767bcf6b6#.nzn3ypl9l">
    <title>Meetings — Medium</title>
    <dc:date>2016-01-04T17:26:48+00:00</dc:date>
    <link>https://medium.com/@padday/meetings-e27767bcf6b6#.nzn3ypl9l</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Meetings can be fantastic or terrible. I’ve experienced some serious pros run meetings, and when they do, everyone feels great afterwards. Everyone feels like progress was made, that things are clearer than before, that there is continued momentum.
]]></description>
<dc:subject>meetings</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:1667b11f1564/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:meetings"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://firstround.com/review/this-90-day-plan-turns-engineers-into-remarkable-managers/">
    <title>This 90-Day Plan Turns Engineers into Remarkable Managers | First Round Review</title>
    <dc:date>2016-01-04T17:26:33+00:00</dc:date>
    <link>http://firstround.com/review/this-90-day-plan-turns-engineers-into-remarkable-managers/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[There’s an all-too-common cycle in tech these days. Startup avoids management. Founder makes all the decisions. Startup gets traction. Hiring takes off. Management is suddenly needed. Founder turns to his best engineer: “I’m drowning. Can you manage this team for me?"

]]></description>
<dc:subject>management leadership</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:714d65a45bb2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:leadership"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.intercom.io/the-engineering-values-we-live-by/">
    <title>Engineering values – the secret to our growth - Inside Intercom</title>
    <dc:date>2015-12-14T20:05:45+00:00</dc:date>
    <link>https://blog.intercom.io/the-engineering-values-we-live-by/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:2fbe4aa7c191/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.catehuston.com/blog/2015/12/02/technical-interview-questions-and-time-management/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed">
    <title>Technical Interview Questions and Time Management « Accidentally in Code</title>
    <dc:date>2015-12-11T15:12:11+00:00</dc:date>
    <link>http://www.catehuston.com/blog/2015/12/02/technical-interview-questions-and-time-management/#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Three criteria of  a good interview question:

Gives a sense of problem-solving and understanding.
Explorable and extendable.
Deeply understood by the interviewer.]]></description>
<dc:subject>interview</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:c3444faaa259/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:interview"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/clef/handbook">
    <title>clef/handbook</title>
    <dc:date>2015-10-08T18:50:12+00:00</dc:date>
    <link>https://github.com/clef/handbook</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[At Clef we’re working to build an inclusive company with a value-driven culture. That’s an easy thing to want and say, but it’s difficult to practice because exclusion is the default in our industry. It takes active effort to find the hidden biases in our companies and remove them.]]></description>
<dc:subject>business culture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:15aafe5ee02c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:business"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:culture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.ploxiln.net/make.html">
    <title>Make</title>
    <dc:date>2015-09-29T22:13:33+00:00</dc:date>
    <link>http://www.ploxiln.net/make.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[make is a widely used and valuable development tool. It's a "build" tool: it builds programs and documentation according to a "recipe". It could really be used for anything where someone edits some files, and then runs a series of processing steps to generate some other form from the edited files. For the most part, however, it's just used to build and install software. make has its origins in Unix somewhere, and these days each BSD project and the GNU project have their own version.]]></description>
<dc:subject>make</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:74e698e463f5/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:make"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gist.github.com/isaacs/62a2d1825d04437c6f08">
    <title>Makefile</title>
    <dc:date>2015-09-29T22:12:14+00:00</dc:date>
    <link>https://gist.github.com/isaacs/62a2d1825d04437c6f08</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[# Hello, and welcome to makefile basics.
#
# You will learn why `make` is so great, and why, despite its "weird" syntax,
# it is actually a highly expressive, efficient, and powerful way to build
# programs.]]></description>
<dc:subject>make</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:f7e61e18ceec/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:make"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html?">
    <title>How we ended up with microservices.</title>
    <dc:date>2015-09-11T10:58:32+00:00</dc:date>
    <link>http://philcalcado.com/2015/09/08/how_we_ended_up_with_microservices.html?</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[When I was at SoundCloud, I was responsible for the migration from a monolithic Ruby on Rails application to a constellation of microservices. I’ve told the technical side of this story multiple times, both in presentations, and as a multi-part series for SoundCloud’s engineering blog. These engineering bits are what people are most interested in hearing about, but recently I realised I never explained to a wider audience how we ended up using microservices to begin with.

]]></description>
<dc:subject>software architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5434611607e7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf">
    <title>How Complex Systems Fail</title>
    <dc:date>2015-09-07T16:44:54+00:00</dc:date>
    <link>http://web.mit.edu/2.75/resources/random/How%20Complex%20Systems%20Fail.pdf</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Being a Short Treatise on the Nature of Failure; How Failure is Evaluated; How Failure is Attributed to Proximate Cause; and the Resulting New Understanding of Patient Safety]]></description>
<dc:subject>failure systems complexity</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:40b870adaf51/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:failure"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:systems"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:complexity"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://blog.intercom.io/how-we-build-software/">
    <title>Lessons learned from scaling a product team - Inside Intercom</title>
    <dc:date>2015-09-01T02:55:30+00:00</dc:date>
    <link>https://blog.intercom.io/how-we-build-software/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>product process business</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:892c1db1b679/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:product"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:process"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:business"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@raffi/what-does-a-vp-of-engineering-do-again-553817fbbf2a">
    <title>What does a VP of Engineering do, again? — Medium</title>
    <dc:date>2015-08-12T11:32:48+00:00</dc:date>
    <link>https://medium.com/@raffi/what-does-a-vp-of-engineering-do-again-553817fbbf2a</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The VPE job is not to actually execute everything by himself, but rather to set up an environment so that execution gets easier, better, and faster over time.]]></description>
<dc:subject>leadership management</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:cf99d51571f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:leadership"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:management"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://medium.com/@gerstenzang/21-management-things-i-learned-at-imgur-7abb72bdf8bf">
    <title>21 management things I learned at Imgur — Medium</title>
    <dc:date>2015-06-22T11:15:14+00:00</dc:date>
    <link>https://medium.com/@gerstenzang/21-management-things-i-learned-at-imgur-7abb72bdf8bf</link>
    <dc:creator>jpcody</dc:creator><dc:subject>management leadership</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e808177f278b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:management"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:leadership"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://tech.bellycard.com/blog/sass-mixins-vs-extends-the-data/">
    <title>Sass Mixins vs Extends: The Data - Belly Card Engineering</title>
    <dc:date>2015-04-22T16:38:54+00:00</dc:date>
    <link>https://tech.bellycard.com/blog/sass-mixins-vs-extends-the-data/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I have to say though, I’m surprised. I was an advocate of extends for the longest time, and went into this test thinking it would be a close race but felt extends would win purely on file size. Upon jumping into the test and watching gzip go to work I’ve been proven wrong.

From here on out I’ll be using mixins and would recommend you favor them over extends too. ]]></description>
<dc:subject>sass mixins css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:9d56cc089515/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:sass"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:mixins"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://42floors.com/blog/startups/thirty-percent-feedback">
    <title>Thirty Percent Feedback - 42Floors Blog</title>
    <dc:date>2015-04-06T11:03:56+00:00</dc:date>
    <link>https://42floors.com/blog/startups/thirty-percent-feedback</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I didn’t polish anything and he made sure not to critique things he knew I would fix later.  It was really freeing. I knew I wasn’t putting my best foot forward and he didn’t care.  He was able to help me shift course without the sunk cost of throwing away a ton of work.  Really awesome.]]></description>
<dc:subject>feedback</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:583627a64dab/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:feedback"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://mcfunley.com/choose-boring-technology">
    <title>Dan McKinley :: Choose Boring Technology</title>
    <dc:date>2015-03-30T16:08:08+00:00</dc:date>
    <link>http://mcfunley.com/choose-boring-technology</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Mindful choice of technology gives engineering minds real freedom: the freedom to contemplate bigger questions. Technology for its own sake is snake oil.]]></description>
<dc:subject>essentials</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:65fe8d124574/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:essentials"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.intercom.io/product-strategy-means-saying-no/">
    <title>Product Strategy Means Saying No - Inside Intercom</title>
    <dc:date>2015-03-09T14:51:01+00:00</dc:date>
    <link>http://blog.intercom.io/product-strategy-means-saying-no/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The thing is, no one keeps crap ideas in their roadmap. Identifying and eliminating the bad ideas is the easy bit. Real product decisions aren’t easy. They require you to look at a proposal and say “This is a really great idea, I can see why our customers would like it. Well done. But we’re not going to build it. Instead, here’s what we’re doing.”.]]></description>
<dc:subject>product</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:370dd92cfe5a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:product"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://sockpuppet.org/blog/2015/03/06/the-hiring-post/">
    <title>The Hiring Post — Quarrelsome</title>
    <dc:date>2015-03-09T10:46:38+00:00</dc:date>
    <link>http://sockpuppet.org/blog/2015/03/06/the-hiring-post/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The software developer job interview doesn’t work. Companies should stop relying on them. The savviest teams will outcompete their peers by devising alternative hiring schemes.]]></description>
<dc:subject>hiring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:19d524e9b3f8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:hiring"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://news.ycombinator.com/item?id=4613543">
    <title>HN comment on efficacy of work-sample tests</title>
    <dc:date>2015-03-09T10:46:24+00:00</dc:date>
    <link>https://news.ycombinator.com/item?id=4613543</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[If you are hiring for any kind of job in the United States, prefer a work-sample test as your hiring procedure. If you are hiring in most other parts of the world, use a work-sample test in combination with a general mental ability test.]]></description>
<dc:subject>hiring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:3047484a8b38/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:hiring"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.tjll.net/ssh-kung-fu/">
    <title>Tyblog | SSH Kung Fu</title>
    <dc:date>2014-04-29T16:09:52+00:00</dc:date>
    <link>http://blog.tjll.net/ssh-kung-fu/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[I rely on ssh every day for multiple purposes and feel the need to share the love for this excellent tool. What follows is a list for some of my use cases that leverage the power of ssh.

]]></description>
<dc:subject>ssh</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e3fc1ca9c6f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ssh"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alistapart.com/article/creating-style-guides">
    <title>Creating Style Guides · An A List Apart Article</title>
    <dc:date>2014-04-20T23:00:36+00:00</dc:date>
    <link>http://alistapart.com/article/creating-style-guides</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Several years ago, I was working on a large, complex application. It was a bit of a legacy project: many different designers and front-end developers had come and gone, each appending a new portion to the sprawling application. By the time I arrived, the CSS was huge, the styles were varied, and it took a lot of effort to find out if anything was reusable.

]]></description>
<dc:subject>styleguide css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:1b8117b1d839/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:styleguide"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/bensmithett/style/blob/master/Makefile">
    <title>style/Makefile at master · bensmithett/style</title>
    <dc:date>2014-04-17T00:16:37+00:00</dc:date>
    <link>https://github.com/bensmithett/style/blob/master/Makefile</link>
    <dc:creator>jpcody</dc:creator><dc:subject>make</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:f3bca6a5e3ca/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:make"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://gist.github.com/toolmantim/6200029">
    <title>An example of using Make instead of Grunt for fast, simple and maintainable front-end asset compilation.</title>
    <dc:date>2014-04-17T00:16:31+00:00</dc:date>
    <link>https://gist.github.com/toolmantim/6200029</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[An example of using Make instead of Grunt for fast, simple and maintainable front-end asset compilation.
]]></description>
<dc:subject>make</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:e22c4aea1d97/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:make"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://algorithms.rdio.com/post/make/">
    <title>Algorithm and Blues</title>
    <dc:date>2014-04-17T00:16:19+00:00</dc:date>
    <link>https://algorithms.rdio.com/post/make/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>make</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:d213ae8bd72c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:make"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.tutsplus.com/articles/what-you-may-not-know-about-the-z-index-property--webdesign-16892">
    <title>What You May Not Know About the Z-Index Property – Development – Tuts+ Tutorials</title>
    <dc:date>2014-01-11T23:32:58+00:00</dc:date>
    <link>http://dev.tutsplus.com/articles/what-you-may-not-know-about-the-z-index-property--webdesign-16892</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The z-index property in CSS seems simple enough, but there's a lot to discover beneath the surface if you really want to understand how it works. In this tutorial we'll clarify the inner workings of z-index, by looking at stacking contexts and a few practical examples.

]]></description>
<dc:subject>css html zindex</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:8864d20251b9/</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:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:zindex"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.zachorr.com/nginx-setup/">
    <title>Battle ready Nginx - an optimization guide</title>
    <dc:date>2014-01-11T23:32:30+00:00</dc:date>
    <link>http://blog.zachorr.com/nginx-setup/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Most setup guides for Nginx tell you the basics - apt-get a package, modify a few lines here and there, and you’ve got a web server! And, in most cases, a vanilla nginx install will work just fine for serving your website. However, if you’re REALLY trying to squeeze performance out of nginx, you’ll have to go a few steps further. In this guide, I’ll explain which settings in nginx can be fine tuned in order to optimize performance for handling a large number of clients. As a note, this isn’t a comprehensive guide for fine-tuning. It’s a breif overview of some settings that can be tuned in order to improve performance. Your mileage may vary.
]]></description>
<dc:subject>nginx devops</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:a189e20191d8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:nginx"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:devops"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://resumablejs.com/">
    <title>Resumable.js, JavaScript magic for simultaneous, stable and resumable uploads</title>
    <dc:date>2013-12-12T14:15:32+00:00</dc:date>
    <link>http://resumablejs.com/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[It’s a JavaScript library providing multiple simultaneous, stable and resumable uploads via the HTML5 File API.]]></description>
<dc:subject>javascript html5</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:28ea12cf87c5/</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:html5"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.slashfilm.com/qa-imax-theatre-real-imax-liemax/">
    <title>Q&amp;A: How Do I Know If My IMAX Theatre is Real 70mm IMAX or lieMAX (Digital IMAX)? | /Film</title>
    <dc:date>2013-10-15T20:15:03+00:00</dc:date>
    <link>http://www.slashfilm.com/qa-imax-theatre-real-imax-liemax/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[So the question is: Do you know where to experience these films in full 70mm IMAX? Or have you been watching Digital IMAX, known to most film geeks as “LIEmax”? Because the difference can be EVERYTHING. We will explain the difference, chronicle the history, and answer the question in this week’s edition of Q&A!


]]></description>
<dc:subject>movies film</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:f7373c3f3171/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:movies"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:film"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://konklone.com/post/switch-to-https-now-for-free?hn">
    <title>Switch to HTTPS Now, For Free</title>
    <dc:date>2013-10-09T03:00:08+00:00</dc:date>
    <link>https://konklone.com/post/switch-to-https-now-for-free?hn</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This post shows how to do your part in building a surveillance-resistant Internet by switching your site to HTTPS. Though it takes a bunch of steps, each one is very simple, and you should be able to finish this in under an hour.

]]></description>
<dc:subject>ssl https security</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:b4e57438a024/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ssl"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:https"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:security"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://jliszka.github.io/2013/10/01/how-traffic-actually-works.html">
    <title>How traffic actually works</title>
    <dc:date>2013-10-09T02:49:34+00:00</dc:date>
    <link>http://jliszka.github.io/2013/10/01/how-traffic-actually-works.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Every so often this article makes the rounds and it annoys me. That isn’t how traffic works and the proposed solutions won’t fix anything. Maybe you can eliminate the annoying stop-and-go, but no one gets home any faster. In fact you can prove that you and everyone behind you get home strictly later than if you had just gone along with the stop-and-go traffic.

]]></description>
<dc:subject>cars traffic</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:c52bec3aceb7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:cars"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:traffic"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://rsync.samba.org/how-rsync-works.html">
    <title>How Rsync Works</title>
    <dc:date>2013-10-08T11:50:03+00:00</dc:date>
    <link>http://rsync.samba.org/how-rsync-works.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[The original Rsync technical report and Andrew Tridgell's Phd thesis (pdf) Are both excellent documents for understanding the theoretical mathematics and some of the mechanics of the rsync algorithm. Unfortunately they are more about the theory than the implementation of the rsync utility (hereafter referred to as Rsync).

]]></description>
<dc:subject>rsync</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6cd985ea6b9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rsync"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.pathname.com/fhs/pub/fhs-2.3.html">
    <title>Filesystem Hierarchy Standard</title>
    <dc:date>2013-09-19T03:13:37+00:00</dc:date>
    <link>http://www.pathname.com/fhs/pub/fhs-2.3.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems.

]]></description>
<dc:subject>standards unix</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:332d9fb580dc/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:unix"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://matthewrobertson.org/blog/2013/08/06/active-record-serializers-from-scratch/">
    <title>ActiveRecord Serializers From Scratch - Matthew Robertson</title>
    <dc:date>2013-09-18T11:45:04+00:00</dc:date>
    <link>http://matthewrobertson.org/blog/2013/08/06/active-record-serializers-from-scratch/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In this post I am going to go over how you can roll your own JSON serialization solution to use in a Rails app in less than 40 lines of code. The idea makes use of basic object oriented techniques (inheritance and hook methods) to leverage the serialization functionality provided by Rails out of the box. ]]></description>
<dc:subject>json rails ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:9eee85b5f38b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:json"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.opera.com/articles/view/mutation-observers-tutorial/">
    <title>Getting to know mutation observers - Dev.Opera</title>
    <dc:date>2013-09-18T11:31:41+00:00</dc:date>
    <link>http://dev.opera.com/articles/view/mutation-observers-tutorial/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Indeed, mutation events are messy enough to have been deprecated in the DOM, Level 3 specification. But if mutation events are deprecated, we need something to replace them. That's where mutation observers come in.
]]></description>
<dc:subject>html javascript dom</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:7267efe73f3c/</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:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:dom"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.lexfriedman.com/post/2856721099/dns-servers-specific-domains">
    <title>Use different DNS servers for specific domains | Lex Friedman | Lex, Briefly</title>
    <dc:date>2013-09-17T16:59:54+00:00</dc:date>
    <link>http://blog.lexfriedman.com/post/2856721099/dns-servers-specific-domains</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[There’s a solution. You want your Mac to use Google or OpenDNS for most websites, but to use your local ISP’s DNS when you visit sites like Netflix. Configuring custom DNS servers for specific websites is doable. I’ll explain how. But first, I’ll explain why I actually care.

]]></description>
<dc:subject>dns football</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:35acaa90ca3d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:dns"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:football"/>
</rdf:Bag></taxo:topics>
</item>
<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://fitzgeraldnick.com/weblog/50/">
    <title>Destructuring Assignment in ECMAScript 6</title>
    <dc:date>2013-09-05T17:40:07+00:00</dc:date>
    <link>http://fitzgeraldnick.com/weblog/50/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Destructuring assignment allows you to assign the properties of an array or object to variables using syntax that looks similar to array or object literals. This syntax can be extremely terse, while still exhibiting more clarity than the traditional property access.

]]></description>
<dc:subject>javascript es6</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:897cf249eb8d/</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:es6"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://know.cujojs.com/tutorials/aop/intro-to-aspect-oriented-programming">
    <title>Intro to Aspect Oriented Programming | know cujoJS</title>
    <dc:date>2013-09-05T16:56:08+00:00</dc:date>
    <link>http://know.cujojs.com/tutorials/aop/intro-to-aspect-oriented-programming</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Aspect Oriented Programming (AOP) is a technique for augmenting the behavior of objects, methods, and functions non-invasively. AOP allows you to add new behaviors and to combine and modify existing behaviors "from the outside".

]]></description>
<dc:subject>javascript programming</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:d3cbc4853d85/</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:programming"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ozkatz.github.io/converting-an-existing-backbonejs-project-to-requirejs.html">
    <title>Converting an existing Backbone.js project to Require.js | Eventual Consistency</title>
    <dc:date>2013-09-03T13:36:51+00:00</dc:date>
    <link>http://ozkatz.github.io/converting-an-existing-backbonejs-project-to-requirejs.html</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Recently, I've undertaken the task of converting a rather large Backbone.js app to using Require.js. Since the process can get tricky at times, here's a quick recap of what I had to do to get it done.
]]></description>
<dc:subject>requirejs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:291ee4ba041d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:requirejs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.karlgroves.com/2013/05/14/links-are-not-buttons-neither-are-divs-and-spans/">
    <title>Links are not buttons. Neither are DIVs and SPANs | Karl Groves</title>
    <dc:date>2013-08-13T20:52:51+00:00</dc:date>
    <link>http://www.karlgroves.com/2013/05/14/links-are-not-buttons-neither-are-divs-and-spans/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[We’ve been doing a lot of testing here at Simply Accessible lately. A lot. In fact, recently, Jeff, Joanna, and I have been doing testing almost exclusively, with support by Derek and Elle. There’s been one development practice we’ve noticed frequently that I’d like to discuss today: use of links as buttons.

]]></description>
<dc:subject>accessibility buttons css</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:94da949cfbb6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:accessibility"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:buttons"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:css"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://davidwalsh.name/add-rules-stylesheets">
    <title>Add Rules to Stylesheets with JavaScript</title>
    <dc:date>2013-07-15T04:00:39+00:00</dc:date>
    <link>http://davidwalsh.name/add-rules-stylesheets</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Another way we can make our pages efficient and fast is to dynamically add and remove styles directly to a stylesheet instead of constantly querying the DOM for elements and applying styles.  Here's how it works!]]></description>
<dc:subject>javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:bda348ba3859/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://craig.is/killing/mice">
    <title>Mousetrap - Keyboard shortcuts in Javascript</title>
    <dc:date>2013-07-13T22:14:41+00:00</dc:date>
    <link>http://craig.is/killing/mice</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[A simple library for handling keyboard shortcuts in Javascript.
Try pressing some of the keys here:]]></description>
<dc:subject>javascript keyboard</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:10c2754799bb/</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:keyboard"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.appfolio.com/2013/06/17/ruby-mixins-activesupportconcern/">
    <title>Ruby Mixins &amp; ActiveSupport::Concern | Appfolio Engineering</title>
    <dc:date>2013-07-12T16:29:49+00:00</dc:date>
    <link>http://engineering.appfolio.com/2013/06/17/ruby-mixins-activesupportconcern/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[A few people have asked: what is the dealio with ActiveSupport::Concern? My answer: it encapsulates a few common patterns for building modules intended for mixins. Before understanding why ActiveSupport::Concern is useful, we first need to understand Ruby mixins.

]]></description>
<dc:subject>mixins rails</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:ee25ded5ee23/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:mixins"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rails"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.nczonline.net/blog/2013/06/25/eval-isnt-evil-just-misunderstood/">
    <title>eval() isn’t evil, just misunderstood | NCZOnline</title>
    <dc:date>2013-07-01T13:01:54+00:00</dc:date>
    <link>http://www.nczonline.net/blog/2013/06/25/eval-isnt-evil-just-misunderstood/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In all of JavaScript, I’m not sure there is a more maligned piece than eval(). This simple function designed to execute a string as JavaScript code has been the more source of more scrutiny and misunderstanding during the course of my career than nearly anything else. ]]></description>
<dc:subject>javascript security</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:677ab172eaf9/</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:security"/>
</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://chancejs.com/#true-random">
    <title>Chance.js: Utility library to generate anything random for JavaScript</title>
    <dc:date>2013-06-25T03:06:15+00:00</dc:date>
    <link>http://chancejs.com/#true-random</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Chance is a minimalist generator of random [1] strings, numbers, etc. to help reduce some monotony particularly while writing automated tests.

]]></description>
<dc:subject>javascript testing</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5ac05547687b/</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:testing"/>
</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://trulia.github.io/hologram/">
    <title>Hologram - Style Documentation Build System</title>
    <dc:date>2013-06-21T11:25:25+00:00</dc:date>
    <link>http://trulia.github.io/hologram/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Hologram is a Ruby gem that parses comments in your CSS and turns them into a beautiful style guide.

]]></description>
<dc:subject>css styleguide</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:35c362dbf6af/</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:styleguide"/>
</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://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/">
    <title>Understanding JavaScript Closures | JavaScript, JavaScript...</title>
    <dc:date>2013-05-25T03:26:58+00:00</dc:date>
    <link>http://javascriptweblog.wordpress.com/2010/10/25/understanding-javascript-closures/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In JavaScript, a closure is a function to which the variables of the surrounding context are bound by reference.

]]></description>
<dc:subject>javascript closure</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:6eb3d1235bb8/</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:closure"/>
</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://blog.jcoglan.com/2013/05/08/how-ruby-method-dispatch-works/">
    <title>How Ruby method dispatch works – The If Works</title>
    <dc:date>2013-05-12T22:28:13+00:00</dc:date>
    <link>http://blog.jcoglan.com/2013/05/08/how-ruby-method-dispatch-works/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[ I’m going to explain how Ruby’s object system works, including method lookup, inheritance, super calls, classes, mixins, and singleton methods.]]></description>
<dc:subject>ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:574daaf89f5b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.appfolio.com/2012/11/16/css-architecture/">
    <title>CSS Architecture | Appfolio Engineering</title>
    <dc:date>2013-05-12T03:08:22+00:00</dc:date>
    <link>http://engineering.appfolio.com/2012/11/16/css-architecture/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[To many Web developers, being good at CSS means you can take a visual mock-up and replicate it perfectly in code. You don’t use tables, and you pride yourself on using as few images as possible. If you’re really good, you use the latest and greatest techniques like media queries, transitions and transforms. While all this is certainly true of good CSS developers, there’s an entirely separate side to CSS that rarely gets mentioned when assessing one’s skill.

]]></description>
<dc:subject>css bestpractices architecture</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:dbd80f86712c/</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:bestpractices"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:architecture"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://pomax.github.io/bezierinfo/">
    <title>Bézier curve framework</title>
    <dc:date>2013-04-30T19:41:13+00:00</dc:date>
    <link>http://pomax.github.io/bezierinfo/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[So, what if you need to program them yourself? What are the pitfalls? How do you draw them? What are the bounding boxes, how do you determine intersections, how can you extrude a curve, in short: how do you do everything that you might want when you do with these curves? That's what this page is for. Prepare to be mathed.

]]></description>
<dc:subject>code math</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:7f1efebb62a2/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:code"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:math"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://substack.net/weaning_yourself_off_jquery">
    <title>weaning yourself off jquery</title>
    <dc:date>2013-04-21T03:07:24+00:00</dc:date>
    <link>http://substack.net/weaning_yourself_off_jquery</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Tiny reusable components are great for organizing and reusing front-end code but some dependencies like jquery will make a tiny frontend module much bigger and more cumbersome than it needs to be.

]]></description>
<dc:subject>javascript jquery</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:eb2c43d1bf7c/</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:jquery"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://tech.pro/tutorial/1226/basic-rubygem-development">
    <title>Basic RubyGem Development - Tech.Pro</title>
    <dc:date>2013-04-19T03:30:35+00:00</dc:date>
    <link>http://tech.pro/tutorial/1226/basic-rubygem-development</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[If you've used Ruby for any period a time, you've probably used a RubyGem before. RubyGems are those things installed with gem install, and can contain libraries or applications written using Ruby. This tutorial will teach you how to make your own RubyGem, the standard practices associated with it, and how to upload it so that others can install it using gem install.

]]></description>
<dc:subject>ruby rubygems</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:bc0f9f3fece4/</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:rubygems"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.elasticspace.com/2013/03/no-to-no-ui">
    <title>No to NoUI – Timo Arnall</title>
    <dc:date>2013-04-07T11:57:15+00:00</dc:date>
    <link>http://www.elasticspace.com/2013/03/no-to-no-ui</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[‘The best design is invisible’ is the interaction design phrase of the moment. The images above are from my ever-expanding collection of quotes about how design and technology will ‘disappear’, become ‘invisible’ or how the ‘best interface is no interface’.

]]></description>
<dc:subject>design ui ux</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:cabfe15d1e8e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ui"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ux"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://github.com/dejan/rails_panel/blob/master/README.md">
    <title>rails_panel/README.md at master · dejan/rails_panel · GitHub</title>
    <dc:date>2013-03-27T21:01:25+00:00</dc:date>
    <link>https://github.com/dejan/rails_panel/blob/master/README.md</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[RailsPanel is a Chrome extension for Rails development that will end your tailing of development.log. Have all information about your Rails app requests in the browser - in the Developer Tools panel. Provides insight to db/rendering/total times, parameter list, rendered views and more.

]]></description>
<dc:subject>rails chrome</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:51f2d585deff/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:rails"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:chrome"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://alexsexton.com/blog/2013/03/deploying-javascript-applications/">
    <title>Deploying JavaScript Applications - Alex Sexton</title>
    <dc:date>2013-03-27T20:22:19+00:00</dc:date>
    <link>http://alexsexton.com/blog/2013/03/deploying-javascript-applications/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Much of this comes from my experience deploying applications at Bazaarvoice as a large third party vendor, and should probably be tailored to your specific environment. I’m sure someone does the opposite of me in each step of this with good results.

]]></description>
<dc:subject>javascript deployment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:809c4a967a23/</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:deployment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://ozkatz.github.com/avoiding-common-backbonejs-pitfalls.html?tagref=js">
    <title>Avoiding Common Backbone.js Pitfalls | Eventual Consistency</title>
    <dc:date>2013-03-27T13:25:57+00:00</dc:date>
    <link>http://ozkatz.github.com/avoiding-common-backbonejs-pitfalls.html?tagref=js</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[This sometimes creates a bit of friction when getting started, as we face common problems, expecting Backbone to take care of them for us, when in reality we may leave "holes" or hidden bugs in our app. Here are some common ones, that are easily avoided, once we realize they exist.

]]></description>
<dc:subject>backbone javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:44c18e1a7668/</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:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.martinfjordvald.com/2012/08/understanding-the-nginx-configuration-inheritance-model/">
    <title>Understanding the Nginx Configuration Inheritance Model | Martin Fjordvald</title>
    <dc:date>2013-03-20T13:27:03+00:00</dc:date>
    <link>http://blog.martinfjordvald.com/2012/08/understanding-the-nginx-configuration-inheritance-model/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[To understand the inheritance model of nginx you first need to know that nginx operates with multiple blocks of configuration. In nginx such a block is referred to as a context, for instance, a configuration directive placed in server context resides within a server { } block just like a directive placed in http context resides in the http { } block.

]]></description>
<dc:subject>nginx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:86846901af42/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:nginx"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.chartjs.org/docs/">
    <title>Chart.js Documentation</title>
    <dc:date>2013-03-18T12:18:31+00:00</dc:date>
    <link>http://www.chartjs.org/docs/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>design javascript dataviz</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:4bb685926320/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:design"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:dataviz"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://stackoverflow.com/questions/12930272/javascript-closures-vs-anonymous-functions">
    <title>scope - JavaScript closures vs. anonymous functions - Stack Overflow</title>
    <dc:date>2013-03-18T12:17:26+00:00</dc:date>
    <link>http://stackoverflow.com/questions/12930272/javascript-closures-vs-anonymous-functions</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Now who is using closures and who isn't?

Note that both solutions print 0 to 9 on the console delayed, so they solve the original problem, but we want to understand which of those two solutions uses closures to accomplish this.]]></description>
<dc:subject>javascript</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:98ad6851bcf7/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:javascript"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://paulstamatiou.com/responsive-retina-blog-development-part-2#footnote-1">
    <title>Developing a responsive, Retina-friendly site (Part 2) — PaulStamatiou.com</title>
    <dc:date>2013-03-15T02:58:45+00:00</dc:date>
    <link>http://paulstamatiou.com/responsive-retina-blog-development-part-2#footnote-1</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[In particular, I'll show how to use HiDPI image assets as well as cover responsive images and some history around that.]]></description>
<dc:subject>html5 css3 responsive</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5ae2cd8b221d/</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:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:responsive"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://blog.tinfoilsecurity.com/ruby-demystified-and-vs">
    <title>Ruby Demystified: and vs. &amp;&amp; - Website Security Blog | Tinfoil Security</title>
    <dc:date>2013-03-15T02:45:49+00:00</dc:date>
    <link>http://blog.tinfoilsecurity.com/ruby-demystified-and-vs</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[When I first started learning Ruby, I was excited to discover that Ruby has the keywords and and or as boolean operators. I quickly got into the habit of writing all of my boolean statements with these, instead of the more conventional && and ||, because my code became so much readable. I thought the word versions of the boolean operators were part of Ruby’s mission to make code more like spoken language.]]></description>
<dc:subject>ruby</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:4f099fddd82d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:ruby"/>
</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://blog.martinfjordvald.com/2010/07/nginx-primer/">
    <title>Nginx: An Introduction to the Nginx Configuration File | Martin Fjordvald</title>
    <dc:date>2013-03-12T11:26:22+00:00</dc:date>
    <link>http://blog.martinfjordvald.com/2010/07/nginx-primer/</link>
    <dc:creator>jpcody</dc:creator><description><![CDATA[Nginx is a fairly simple HTTP server, though there are a few gotchas people need to be aware of before they start using this 8th wonder. The most important is that nginx is a reverse proxy first and HTTP server second, it does not necessarily have a concept of file, this will change the way we handle our configuration a bit.

]]></description>
<dc:subject>server nginx</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:232ae00767f7/</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:nginx"/>
</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://viljamis.com/blog/2013/prototyping-responsive-typography/">
    <title>Prototyping Responsive Typography</title>
    <dc:date>2013-03-09T23:29:09+00:00</dc:date>
    <link>http://viljamis.com/blog/2013/prototyping-responsive-typography/</link>
    <dc:creator>jpcody</dc:creator><dc:subject>typography responsive</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jpcody/b:5730b7887718/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:typography"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jpcody/t:responsive"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>