<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

  <title><![CDATA[Tyson Tate's Blog]]></title>
  <link href="http://tysontate.github.com/atom.xml" rel="self"/>
  <link href="http://tysontate.github.com/"/>
  <updated>2012-03-17T14:58:27-07:00</updated>
  <id>http://tysontate.github.com/</id>
  <author>
    <name><![CDATA[Tyson Tate]]></name>
    <email><![CDATA[tyson@tysontate.com]]></email>
  </author>
  <generator uri="http://octopress.org/">Octopress</generator>

  
  <entry>
    <title type="html"><![CDATA[Setting up a new iPad]]></title>
    <link href="http://tysontate.github.com/blog/2012/03/17/setting-up-a-new-ipad/"/>
    <updated>2012-03-17T14:46:00-07:00</updated>
    <id>http://tysontate.github.com/blog/2012/03/17/setting-up-a-new-ipad</id>
    <content type="html"><![CDATA[<p>I bought the new iPad yesterday, and this was my entire setup process migrating from my old iPad:</p>

<ol>
<li>Unbox and turn on new iPad.</li>
<li>Enter some preliminary settings (language, wi-fi, etc.) and my iCloud username and password.</li>
<li>Come back in an hour or so.</li>
<li>Re-enter a few email / other account passwords (which iCloud doesn&#8217;t store).</li>
</ol>


<p>And that was it. If it wasn&#8217;t for the new screen, I wouldn&#8217;t be able to tell you which iPad was which.</p>

<p>The setup process for my <em>running watch</em> requires more steps than that.</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[A Modest Parking Proposal]]></title>
    <link href="http://tysontate.github.com/blog/2012/03/05/a-modest-parking-proposal/"/>
    <updated>2012-03-05T22:46:00-08:00</updated>
    <id>http://tysontate.github.com/blog/2012/03/05/a-modest-parking-proposal</id>
    <content type="html"><![CDATA[<p>San Francisco has a problem<sup id='fnref:a-modest-parking-proposal:1'><a href='#fn:a-modest-parking-proposal:1' rel='footnote'>1</a></sup>.</p>

<p>There&#8217;s no parking for the people who live here. Tourists, sure. Parking for them is a veritable cournacoupia of meters and garages and, for some reason, red curbs and other people&#8217;s driveways. But for its residents, San Francisco is a wasteland.</p>

<p>In my neighborhood, Alamo Square<sup id='fnref:a-modest-parking-proposal:2'><a href='#fn:a-modest-parking-proposal:2' rel='footnote'>2</a></sup>, you can easily spend upwards of half an hour looking for a parking space in the late afternoon or evening. On several occasions, I&#8217;ve spent an entire hour circling my neighborhood in ever-widening concentric circles blasting ever-angrier music looking for a parking spot.</p>

<p>If you&#8217;ve never lived in a large city, you might think I&#8217;m exaggerating. I am not.</p>

<p>And when you <em>do</em> find a parking space, you wont get to keep it for long. Most streets in San Francisco are swept on a weekly basis &#8211; some more than once per week. You&#8217;ve got to repeat the parking journey once or twice every week, and that&#8217;s not including the times you actually use your car for something other than looking for parking.</p>

<p>This results in a secondary problem: hundreds of frustrated drivers slowly weaving through the streets at all hours of the day trying to find parking. And people looking for parking aren&#8217;t attentive, safe drivers, either. They are distracted, unsafe drivers. To find a parking space, you have to be constantly scanning both sides of the road rather than paying attention to minor details like, say, other drivers, pedestrians, and cyclists. Is that a driveway? Is that space big enough? Is that curb red? Are there any fire hydrants near that spot? Where&#8217;s the sign that tells me when this side of the street is swept? Are there any signs hidden in the trees that invariably have some bizarre requirement that I&#8217;ll get a ticket for? Is that person leaving or did they just park? Why am I sweating so much?</p>

<p>I think the situation can be made a lot safer with a single stripe of paint. Take, for example, this fairly typical parking scenario:</p>

<p><img src="http://tysontate.github.com/images/parking-in-sf/street_1_before.jpg" width="600"></p>

<p>There&#8217;s a nice big spot not 20 yards ahead, right? Wrong — it&#8217;s two driveways. And you wont be able to tell until you&#8217;ve driven closer and looked away from the road to check.</p>

<p>What if instead of looking at buildings and signs and curbs, you could keep your eyes on the road? What if we added a bright stripe that delineated the areas that you could park?</p>

<p><img src="http://tysontate.github.com/images/parking-in-sf/street_1_after.jpg" width="600"></p>

<p>You can instantly tell from far away that what appears to be a rare and precious parking space is, instead, off-limits.</p>

<p>The benefits of this simple stripe would be many: Drivers looking for parking would be able to keep their eyes on the road and drive more predictably, with fewer erratic stops. That&#8217;s safer for everyone.</p>

<p>Again: Look, two parking spaces in the distance!</p>

<p><img src="http://tysontate.github.com/images/parking-in-sf/street_2_before.jpg" width="600"></p>

<p>Nope. Two driveways. But add in the stripe:</p>

<p><img src="http://tysontate.github.com/images/parking-in-sf/street_2_after.jpg" width="600"></p>

<p>And now you can easily see from far away that you can&#8217;t park there instead of needing to slow down and look away from the road to check.</p>

<p>Then again, it&#8217;s a cheap and practical idea, which means San Francisco would never even begin to consider doing such a thing. Instead, they&#8217;d probably just remove half the parking spots and turn them into parklets or organic free-range snail farms.</p>

<div class="footnotes">
  <ol>
            <li id="fn:a-modest-parking-proposal:1">
          Well, <a href="http://whytherearenogirls.blogspot.com">two problems</a>. <a href='#fnref:a-modest-parking-proposal:1' rev='footnote'>↩</a>
        </li>
        <li id="fn:a-modest-parking-proposal:2">
          Don&#8217;t be creepy. <a href='#fnref:a-modest-parking-proposal:2' rev='footnote'>↩</a>
        </li>

  </ol>
</div>



]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[iTunes Match Complaints and Grievances]]></title>
    <link href="http://tysontate.github.com/blog/2011/12/25/itunes-match-complaints-and-grievances/"/>
    <updated>2011-12-25T22:41:00-08:00</updated>
    <id>http://tysontate.github.com/blog/2011/12/25/itunes-match-complaints-and-grievances</id>
    <content type="html"><![CDATA[<p><a href="http://www.apple.com/icloud/features/">iTunes Match</a> is a fantastic service. If you have more than one Apple device, it makes managing your music dead simple&#8211;all of your music becomes easily available on all of your Apple devices. It even lets you re-download high quality versions your poorly-encoded MP3s, regardless of origin.</p>

<p>Unfortunately, it&#8217;s not perfect. Here are my current iTunes Match complaints and grievances:</p>

<ul>
<li>It will frequently match your &#8220;explicit&#8221; songs with their &#8220;clean&#8221; versions, turning your prized early-90s gangster rap collection into an episode of Yo Gabba Gabba. Thankfully, my George Carlin MP3s escaped this mangling. (Can you even <em>imagine</em>?)</li>
<li>It will refuse to match or even upload songs encoded below 96kbps. Ostensibly, this is to ensure the accuracy of the audio fingerprinting. However, this doesn&#8217;t make sense to me for two reasons: One, I see no plausible reason not to allow low-bitrate songs to be uploaded. Two, I <a href="https://github.com/tysontate/bitrate_forcer">upconverted my MP3s</a> and iTunes Match had no real problem matching my 5,000 songs with very good accuracy.</li>
<li>It provides no method to replace your ID3 tags with correct ones in cases where your tags are incorrect / incomplete.</li>
</ul>

]]></content>
  </entry>
  
</feed>

