<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Alan Storm's Link List: Links for the working programmer.</title>
<link href="http://alanstorm.com//links"></link>
<id>urn:uuid:2a149ca4-5a68-752b-da2c-76e34a508cf8</id>
<updated>2012-07-06T13:53:49-07:00</updated>
<author><name>Alan Storm</name>
</author>
<entry>
<title>Statement Of Purpose</title>
<link href="http://alanstorm.com/links/"></link>
<id>urn:uuid:2060ac95-6674-9abd-5758-9f2780c5179d</id>
<updated>2012-07-06T13:45:51-07:00</updated>
<published>2012-07-06T13:13:35-07:00</published>
<summary type="html"><![CDATA[<p>Is linking your new link list in your new link list gauche?  I&#8217;ve been working on this in my spare time for the past few months, slowly populating content and tweaking the backend scripts I&#8217;m using to publish things.  My goals here are</p>

<ol>
<li><p>Creating a place where I can talk about topics not related to programming.  This link list is more my idle thoughts on a topic, whereas the main <a href="http://alanstorm.com">alanstorm.com</a> articles will continue to be programming tutorials</p></li>
<li><p>Create a place where I can, and will, write everyday</p></li>
<li><p>Create a space where I can, and will, play around with the design on a regular, possibly daily basis.  I&#8217;ve been out of the frontend game for a few years and need to see what&#8217;s changed.  I&#8217;ll also be abandoning my general practice of <a href="http://alanstorm.com/magento_javascript_events">keeping</a> old <a href="http://alanstorm.com/magento_models_orm">site</a> designs <a href="http://alanstorm.com/tt4/local_w3c">active</a> after a redesign</p></li>
<li><p>Write some backend publishing software to figure out what&#8217;s really needed for small publishers in 2012 vs. what&#8217;s in most modern CMS publishing systems</p></li>
</ol>

<p>For now I&#8217;m going to keep this link list separate from my main site until the kinks are worked out.  Contents will shift during flight, don&#8217;t get too attached.</p>

<p><a href="http://alanstorm.com//links/2012/07/statement-of-purpose">Permanent Link to Statement Of Purpose</a></p>
]]></summary>
</entry>
<entry>
<title>Retina Balkanization</title>
<link href="http://www.red-sweater.com/blog/2568/target-the-forward-fringe"></link>
<id>urn:uuid:c3ae32cb-19f9-1ede-e191-92075f0da0b8</id>
<updated>2012-07-06T13:25:09-07:00</updated>
<published>2012-07-06T12:18:16-07:00</published>
<summary type="html"><![CDATA[<p>If you&#8217;re creating an iPhone, iPad, or even Mac OS application not updating for the retina display seems like a foolish, short sighted move.  The rest of the web is left with a tricky choice.  </p>

<p>Most day to web production centers around coding up a version of your site that works in a leading edge browser, and then making choices when it comes to browsers that aren&#8217;t that leading edge browser.  Sometimes the choice is leaving a visual flourish on the table, other times it&#8217;s rewriting your solution to better accommodate the older browser, sometimes it&#8217;s patching things up with an IE specific style sheet.  Those choices depends on a lot of the business, project, and individuals involved in the project.</p>

<p>The past five years, (marked by the introduction of the iphone), have seen that model turned upside down.  The proliferation of devices, screen sizes, and resolutions has left day to day web producers with an uncomfortable choice &#8212; abandon the above model and take on insane production burdens, or leave some devices on the table. This increased balkanization has given &#8220;The Web&#8221; a less coherent sense of place, which (personally) makes it a much less interesting medium. </p>

<p>Regardless of whether <strong>you</strong> adopt a retina display, there&#8217;s going to be a lot of websites and companies that choose to skip it, and that&#8217;s going to lead to an ugly web experience for people using these retina devices.  I find this depressing, especially when I imagine a meeting that had to happen at some point inside Apple Inc.</p>

<blockquote>
  <p><strong>Engineer</strong>: OK, what can we do with safari and webkit to ensure our users have the best experience possible when viewing websites on a retina display</p>
  
  <p><strong>Decision Maker</strong>: &#8230;</p>
</blockquote>

<p>It&#8217;s not so much that there&#8217;s a secret cabal of executive deep inside Apple who are plotting the demise of The Web — more that The Web itself no longer has a strong advocate, and it slowly atrophying into something unrecognizable and arguably inferior to what came before.</p>

<p><a href="http://alanstorm.com//links/2012/07/retina-balkanization">Permanent Link to Retina Balkanization</a></p>
]]></summary>
</entry>
<entry>
<title>Ipv4 For Sale</title>
<link href="http://tech.slashdot.org/story/12/05/24/1526258/sales-of-unused-ipv4-addresses-gaining-steam"></link>
<id>urn:uuid:0fd0a227-1be0-bce4-9f53-8c47bf682eb7</id>
<updated>2012-05-24T16:49:07-07:00</updated>
<published>2012-05-24T13:11:37-07:00</published>
<summary type="html"><![CDATA[<p>Some people are obsessed with peak oil, I&#8217;m obsessed with peak IPv4. </p>

<ol>
<li><p>Large organizations hate infrastructure projects like IPv6</p></li>
<li><p>Meaning blocks of IPv4 addresses will continue to grow in value</p></li>
<li><p>At some point all that &#8220;easy&#8221; money will become too tempting for the large shared hosts, and they&#8217;ll sell their IP blocks and close up shop</p></li>
</ol>

<p>I know shared hosting isn&#8217;t cutting edge stuff, but the business and cultural echos of losing shared hosting are sure to felt far and wide.</p>

<p><a href="http://alanstorm.com//links/2012/05/ipv4-market">Permanent Link to Ipv4 For Sale</a></p>
]]></summary>
</entry>
<entry>
<title>Not That Daring</title>
<link href="http://kickingbear.com/blog/archives/305"></link>
<id>urn:uuid:fcc3da4e-421c-e069-3575-f2b8487645b5</id>
<updated>2012-05-24T16:26:12-07:00</updated>
<published>2012-05-24T16:26:12-07:00</published>
<summary type="html"><![CDATA[<p><cite>Guy English</cite> writes</p>

<blockquote>
  <p>I believe that many Apple observers have been too invested in picking off the low hanging fruit of obviously out-of-touch commentators, columnists, and analysts. Apple is winning. It’s fun to pick on the idiots, and we do tune in for the affirmation that engenders, but that’s not insight. It’s a tag team wedgie patrol</p>
</blockquote>

<p>Yup.</p>

<p><a href="http://alanstorm.com//links/2012/05/not-that-daring">Permanent Link to Not That Daring</a></p>
]]></summary>
</entry>
<entry>
<title>Dustin Curtis is a Villain.</title>
<link href="http://dcurt.is/"></link>
<id>urn:uuid:84418da3-dd0f-d727-40d4-8b875f79a7c3</id>
<updated>2012-05-17T19:00:57-07:00</updated>
<published>2012-05-17T19:00:57-07:00</published>
<summary type="html"><![CDATA[<p>First trade press blog in a long time that didn&#8217;t leave me wanting to punch somebody.</p>

<p><a href="http://alanstorm.com//links/2012/05/dcurtis">Permanent Link to Dustin Curtis is a Villain.</a></p>
]]></summary>
</entry>
<entry>
<title>Terminal Log</title>
<link href="http://hints.macworld.com/article.php?story=20120507163311559"></link>
<id>urn:uuid:72087df1-9330-ac87-38cd-a997c54f8d8b</id>
<updated>2012-05-13T14:25:34-07:00</updated>
<published>2012-05-13T14:25:34-07:00</published>
<summary type="html"><![CDATA[<p>A quick shell tip for logging your terminal session to a file.  It&#8217;s on the OS X tips site but <code>script</code> is a generic UNIX command.  Seems like a nice crutch for those of us who still have troubling greping live text streams.</p>

<p><a href="http://alanstorm.com//links/2012/05/terminal-log">Permanent Link to Terminal Log</a></p>
]]></summary>
</entry>
<entry>
<title>VIM Advanced Functionality</title>
<link href="http://zmievski.org/files/talks/codeworks-2009/vim-for-php-programmers.pdf"></link>
<id>urn:uuid:e526d679-c474-bd39-7ab3-3837e6278829</id>
<updated>2012-05-13T13:56:44-07:00</updated>
<published>2012-05-13T13:56:44-07:00</published>
<summary type="html"><![CDATA[<p>Back when I was in college someone had left a xerox with a the title <em>How to use VI</em> behind in the libraries &#8220;VAX&#8221; area.  It warms the remaining cockles of my heart to see VI/VIM still in active use today.</p>

<p><a href="http://alanstorm.com//links/2012/05/vi-slides">Permanent Link to VIM Advanced Functionality</a></p>
]]></summary>
</entry>
<entry>
<title>Development Environment</title>
<link href="http://thinkupapp.com/docs/contribute/developers/index.html"></link>
<id>urn:uuid:5879c956-e062-8450-7afd-133c9b707d55</id>
<updated>2012-05-13T13:44:00-07:00</updated>
<published>2012-05-13T13:44:00-07:00</published>
<summary type="html"><![CDATA[<p>I used to be amazed when a company, especially a company that used contract developers, didn&#8217;t have strict procedures on how to run tests and how source code should and shouldn&#8217;t be submitted/merged/etc.  Not because there&#8217;s a global, I.B.M. style,  right or wrong way to do things, but because a team needs a consistent set of expectations for how to do and submit their work, otherwise days will be lost during deployments, on-boarding, and the like. </p>

<p>If you&#8217;re a team leader and don&#8217;t have a document like ThinkUp&#8217;s, make one now.  If you&#8217;re considering a job ask development team members what their procedure is.  If you get that blank &#8220;brogrammer stare&#8221; back, procede with caution.</p>

<p><a href="http://alanstorm.com//links/2012/05/development-environment">Permanent Link to Development Environment</a></p>
]]></summary>
</entry>
<entry>
<title>Git Should Not Be Hard</title>
<link href="http://think-like-a-git.net/"></link>
<id>urn:uuid:9f1a3f88-d348-a6e3-f589-616f5335dfd7</id>
<updated>2012-05-05T19:16:17-07:00</updated>
<published>2012-05-05T19:16:17-07:00</published>
<summary type="html"><![CDATA[<p>Back when the git crowd was trying to displace subversion as every developer&#8217;s favorite version control system, it always rankled when claims were made about how much easier branching/merging/etc were.  These actions, and the git model, were no easier than subversion&#8217;s. The problem with branching and merging has always been one of expectation: Reasonable people disagree on how a certain situation should be handled, and when their software acts differently they get frustrated until they learn the new model.</p>

<p><a href="http://think-like-a-git.net/">Think Like (a) Git</a> looks like it&#8217;s one of the few git tutorials out there that</p>

<ol>
<li><p>Acknowledges git is hard</p></li>
<li><p>Attempts to explain it&#8217;s model to smart people who know nothing about git</p></li>
</ol>

<p><a href="http://alanstorm.com//links/2012/05/git-should-not-be-hard">Permanent Link to Git Should Not Be Hard</a></p>
]]></summary>
</entry>
<entry>
<title>RubyMotion</title>
<link href="http://www.rubymotion.com/"></link>
<id>urn:uuid:d9841cd2-f7bf-dab7-e35a-876044951b31</id>
<updated>2012-05-03T22:34:37-07:00</updated>
<published>2012-05-03T22:34:37-07:00</published>
<summary type="html"><![CDATA[<p>A commercial ruby development environment for iOS applications.  This is the sort of thing the old anti-flash <a href="http://daringfireball.net/2010/04/iphone_agreement_bans_flash_compiler">section 3.3.1</a> nonsense might have banned.  </p>

<p>This is also an interesting development in the world of software tools/IDEs. The pendulum is swinging away from strictly open-source tools and more towards commercial/open-source hybrids.</p>

<p><a href="http://alanstorm.com//links/2012/05/commercial-ide">Permanent Link to RubyMotion</a></p>
]]></summary>
</entry>
<entry>
<title>As Long As Its Black</title>
<link href="http://www.youtube.com/watch?v=RGQTaHGQ04Q"></link>
<id>urn:uuid:0f48f9be-3994-fb20-b037-52cacd0702ae</id>
<updated>2012-05-03T22:17:37-07:00</updated>
<published>2012-05-03T22:17:37-07:00</published>
<summary type="html"><![CDATA[<p>This video mock-up of an improved iOS keyboard is what bums me out most about Apple&#8217;s desire/need to lock down their OS.  Fifteen years ago the development community would have mocked up a prototype and/or product to actually give you this functionality, in the future we get a mock-up and empty-hopes that Apple will build something like this.</p>

<!-- Thursday; May 3, 2012 -->

<p><a href="http://alanstorm.com//links/2012/05/as-long-as-its-black">Permanent Link to As Long As Its Black</a></p>
]]></summary>
</entry>
<entry>
<title>Amanda Palmer Kickstarter and Everything</title>
<link href="http://whatever.scalzi.com/2012/05/03/amanda-palmer-kickstarter-and-everything/"></link>
<id>urn:uuid:27ed58c8-9771-3b7d-325e-432b68fb3053</id>
<updated>2012-05-03T10:54:32-07:00</updated>
<published>2012-05-03T10:54:32-07:00</published>
<summary type="html"><![CDATA[<p>Solid analysis of Amanda Palmer&#8217;s success via Kickstarter.  TL;DR; It&#8217;s not a magic money machine, it&#8217;s one part of of running a small business.</p>

<p>I know disintermediation is the buzzword, but we&#8217;re not eliminating middle men, we&#8217;re just setting up a new generation of middle men with different agreements.</p>

<!-- Thursday; May 3, 2012 -->

<p><a href="http://alanstorm.com//links/2012/05/amanda-palmer-kickstarter">Permanent Link to Amanda Palmer Kickstarter and Everything</a></p>
]]></summary>
</entry>
<entry>
<title>Serializing is Hard</title>
<link href="http://news.ycombinator.com/item?id=3900224"></link>
<id>urn:uuid:ba57b34c-0a79-e431-2f88-deef5c6e20c0</id>
<updated>2012-04-27T13:13:49-07:00</updated>
<published>2012-04-27T13:13:49-07:00</published>
<summary type="html"><![CDATA[<p>A bit of WTF style fun in a hacker news thread.</p>

<p><a href="http://alanstorm.com//links/2012/04/serializing-is-hard">Permanent Link to Serializing is Hard</a></p>
]]></summary>
</entry>
<entry>
<title>Hints of the Coming Agency Technology Crisis</title>
<link href="http://5by5.tv/webahead"></link>
<id>urn:uuid:4b86aee2-839b-cc5e-2b68-2cf985700af8</id>
<updated>2012-04-26T23:51:16-07:00</updated>
<published>2012-04-26T23:51:16-07:00</published>
<summary type="html"><![CDATA[<p>There were <a href="http://5by5.tv/webahead/20">two</a> <a href="http://5by5.tv/webahead/21">recent</a> episode&#8217;s of Jen Simmons&#8217;s The Web Ahead podcast where you can start to see the cracks showing in how design/interactive/advertising agencies handle their technology and software design needs, and how that&#8217;s trickling down into stressful/futile production situations.</p>

<!-- Thursday; April 26, 2012 11:44 PM -->

<p><a href="http://alanstorm.com//links/2012/04/web-ahead">Permanent Link to Hints of the Coming Agency Technology Crisis</a></p>
]]></summary>
</entry>
<entry>
<title>Meteor Javascript Framework</title>
<link href="http://www.meteor.com/"></link>
<id>urn:uuid:86cf05b5-bcd0-330e-1d23-953ef588060c</id>
<updated>2012-04-26T23:36:03-07:00</updated>
<published>2012-04-26T23:36:03-07:00</published>
<summary type="html"><![CDATA[<p>This feels like it&#8217;s worth paying attention to. There&#8217;s a ton of great work being done with javascript these days, but most of it&#8217;s happening behind closed doors at secretive speculative R&amp;D companies (i.e. &#8220;start ups&#8221;).  Meteor looks like it&#8217;s trying to bring these techniques out into the open.</p>

<p>That said, the only distribution (<a href="https://github.com/meteor/meteor">outside of a contextless github account</a>) is one of those weird &#8220;download and immediately execute this shell script&#8221; things, which is sort of squiky.</p>

<!-- Thursday; April 26, 2012 11:36 PM -->

<p><a href="http://alanstorm.com//links/2012/04/meteor-javascript-framework">Permanent Link to Meteor Javascript Framework</a></p>
]]></summary>
</entry>
</feed>