Guest User Blog not rendering web page

a guest
Nov 18th, 2011
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:dc="">
  3.   <channel>
  4.     <title>Signal vs. Noise</title>
  5.     <link></link>
  6.     <language>en-us</language>
  7.     <ttl>40</ttl>
  8.     <description>Signal vs. Noise</description>
  9.     <item>
  10.       <dc:creator>Jamie</dc:creator>
  11.       <title>VIDEO: Inspiring stuff. Related SvN posts: The first…</title>
  12.       <description>&lt;iframe width="560" height="315" src="" frameborder="0" allowfullscreen&gt;&lt;/iframe&gt;
  13. &lt;p&gt;Inspiring stuff. Related SvN posts: &lt;a href=""&gt;The first step is to start&lt;/a&gt; and &lt;a href=""&gt;Four tips for learning how to program&lt;/a&gt;&lt;/p&gt;</description>
  14.       <pubDate>Wed, 16 Nov 2011 12:06:00 +0000</pubDate>
  15.       <guid></guid>
  16.       <link></link>
  17.     </item>
  18.     <item>
  19.       <dc:creator>Ryan</dc:creator>
  20.       <title>QUOTE: Designing a product is keeping five thousand…</title>
  21.       <description>&lt;p&gt;Designing a product is keeping five thousand things in your brain and fitting them all together in new and different ways to get what you want. And every day you discover something new that is a new problem or a new opportunity to fit these things together a little differently.&lt;/p&gt;
  24.     &lt;p&gt;And it’s that process that is the magic.&lt;/p&gt;
  25. &lt;p&gt;&amp;#8212;Steve Jobs (via &lt;a href=""&gt;Daring Fireball&lt;/a&gt;)&lt;/p&gt;</description>
  26.       <pubDate>Tue, 15 Nov 2011 23:58:00 +0000</pubDate>
  27.       <guid></guid>
  28.       <link></link>
  29.     </item>
  30.     <item>
  31.       <dc:creator>Joan</dc:creator>
  32.       <title>Welcome Shaun and Emily!</title>
  33.       <description>&lt;p&gt;A couple terrific people have joined our team recently: Shaun Hildner and Emily Wilder.&lt;/p&gt;
  36.     &lt;p&gt;Jason &lt;a href=""&gt;wrote a little bit about him in Inc.&lt;/a&gt;, so you might already know that Shaun joined us a little over a month ago as our new videographer. He made both the great logo animation and customer appreciation party video. Shaun is originally from Montana (also known in my area of the country as Western Real America) and now lives in Chicago. His application and &lt;a href=""&gt;demo reel&lt;/a&gt; really impressed everyone at 37signals and we’re very pleased to have him aboard.&lt;/p&gt;
  39.     &lt;p&gt;If you’ve sent in a support ticket or checked out our &lt;a href=""&gt;Smiley ratings&lt;/a&gt; in the past few weeks, you might have noticed a new face. Emily Wilder has joined our Customer Support team, which means we are seven members strong and finally able to compete in water polo.&lt;/p&gt;
  42.     &lt;p&gt;Emily was hired in an effort to replicate qualities from existing support team members: a redhead like Ann, a Northern California transplant to Austin like Merissa, and a passion for helping people like all of us. Emily told me her heroes are people she knows who manage to be brilliant while unfailingly kind, and her superpowers include the ability summon bagpipes with her mind and bake bread without a recipe.&lt;/p&gt;
  45.     &lt;p&gt;You can follow &lt;a href=""&gt;Emily&lt;/a&gt; and &lt;a href=""&gt;Shaun&lt;/a&gt; on Twitter or help us welcome them here!&lt;/p&gt;</description>
  46.       <pubDate>Thu, 10 Nov 2011 23:34:00 +0000</pubDate>
  47.       <guid></guid>
  48.       <link></link>
  49.     </item>
  50.     <item>
  51.       <dc:creator>Jason F.</dc:creator>
  52.       <title>PHOTO: Fisher Price toy.</title>
  53.       <description>&lt;img alt="7214820_0_9999_med_v1_m56577569830498825.jpg" height="300" src="" width="300" /&gt;
  54. &lt;p&gt;Fisher Price toy.&lt;/p&gt;</description>
  55.       <pubDate>Tue, 08 Nov 2011 18:50:00 +0000</pubDate>
  56.       <guid></guid>
  57.       <link></link>
  58.     </item>
  59.     <item>
  60.       <dc:creator>Jason F.</dc:creator>
  61.       <title>PHOTO: Hypercard.</title>
  62.       <description>&lt;img alt="hypercard.gif" height="342" src="" width="512" /&gt;
  63. &lt;p&gt;Hypercard.&lt;/p&gt;</description>
  64.       <pubDate>Mon, 07 Nov 2011 15:50:00 +0000</pubDate>
  65.       <guid></guid>
  66.       <link></link>
  67.     </item>
  68.     <item>
  69.       <dc:creator>Jason F.</dc:creator>
  70.       <title>Quick little UI feedback tip</title>
  71.       <description>&lt;p&gt;Sometimes when I&amp;#8217;m giving feedback on a UI, and I&amp;#8217;m pointing out a spacing detail, I upload a little screenshot to Basecamp or Campfire to help make sure the feedback is clear.&lt;/p&gt;
  74.     &lt;p&gt;I wanted to share a little tweak to the feedback which I think is ultimately more useful. In this example I&amp;#8217;m pointing out that the space above and below an element is not equal (and I think it should be).&lt;/p&gt;
  77.     &lt;p&gt;I used to do it like this:&lt;/p&gt;
  80.     &lt;p&gt;&lt;img src="" /&gt;&lt;/p&gt;
  83.     &lt;p&gt;Two lines. One line above the element (text, in this case) extending to the next element above it, and one line below the element extending to the next element below it. The length of the lines shows the different spacing. That works, but the difference &amp;#8211; especially when we&amp;#8217;re talking about small units of pixels &amp;#8211; isn&amp;#8217;t as clear as it could be.&lt;/p&gt;
  86.     &lt;p&gt;Then I switched to doing it like this:&lt;/p&gt;
  89.     &lt;p&gt;&lt;img src="" /&gt;&lt;/p&gt;
  92.     &lt;p&gt;Blocks like this are easier to see than thin one pixels lines. This is an improvement. But it&amp;#8217;s still not as clear as it could be because it&amp;#8217;s not as easy to judge the comparative volume of a rectangle as it is a square. So&amp;#8230;&lt;/p&gt;
  95.     &lt;p&gt;This is how I do it now:&lt;/p&gt;
  98.     &lt;p&gt;&lt;img src="" /&gt;&lt;/p&gt;
  101.     &lt;p&gt;The same vertical distance is covered, but now, since both blocks are perfect squares, we have related horizontal distance which helps you see how much bigger the difference is.&lt;/p&gt;
  104.     &lt;p&gt;Why not just say 24px vs 35px? Because I want to point out the physical difference, not the exact number of pixels. If we&amp;#8217;re just talking numbers then it&amp;#8217;s easy to assume 24px or 35px is right. But maybe the final size is 27px or 31px. I don&amp;#8217;t want to get stuck on numbers when I provide feedback like this. The final number isn&amp;#8217;t important as long as it&amp;#8217;s the same (and it looks right).&lt;/p&gt;
  107.     &lt;p&gt;I hope this was helpful.&lt;/p&gt;</description>
  108.       <pubDate>Fri, 04 Nov 2011 18:39:00 +0000</pubDate>
  109.       <guid></guid>
  110.       <link></link>
  111.     </item>
  112.     <item>
  113.       <dc:creator>David</dc:creator>
  114.       <title>PHOTO: scumbag-jason-2</title>
  115.       <description>&lt;img alt="scumbag-jason-2.png" height="675" src="" width="442" /&gt;
  116. </description>
  117.       <pubDate>Fri, 04 Nov 2011 04:21:00 +0000</pubDate>
  118.       <guid></guid>
  119.       <link></link>
  120.     </item>
  121.     <item>
  122.       <dc:creator>Shaun</dc:creator>
  123.       <title>Evolution of a Logo Animation</title>
  124.       <description>&lt;p&gt;I suppose this is my first SvN post, so by way of an introduction I thought I&amp;#8217;d share a bit about creating the animated 37signals logo.&lt;/p&gt;
  127.     &lt;p&gt;When I first came on as &amp;#8220;the video guy,&amp;#8221; I wanted to think about how to brand 37signals&amp;#8217; wide variety of content with an interesting and unifying bumper. We hadn&amp;#8217;t had to deal much with incorporating our logo into video, so it was time we gave it a bit of motion.&lt;/p&gt;
  130.     &lt;p&gt;37signals is all about building things&amp;#8212;from building a business to building software. I wanted the logo to &amp;#8220;build&amp;#8221; itself to reveal the design. &lt;/p&gt;
  133.     &lt;p&gt;I actually landed on the basic animation that would become the final product early on, but kept trying more and more complicated versions. I spent a week teaching myself new 3D software and countless hours tweaking every frame to get it just right, but as these things often go, we ended up back with a simple, clean design. The way the logo &amp;#8220;builds&amp;#8221; itself feels natural; it&amp;#8217;s hard to imagine it moving any other way.&lt;/p&gt;
  136.     &lt;p&gt;Not that it wasn&amp;#8217;t worth it to challenge myself&amp;#8212;I certainly enjoy learning new software and techniques, but it&amp;#8217;s a good lesson to learn. More often than not, the simplest solution is often the best.&lt;/p&gt;
  139.     &lt;p&gt;The chimes were a lucky coincidence. I needed some audio to give the animation a little more life. Using GarageBand and hitting four random keys on my keyboard, I came up with the chimes as a placeholder until someone with musical talent could get their ears on it. Like many things around here, it just worked&amp;#8212;so we left it in the final version.&lt;/p&gt;
  142.     &lt;p&gt;Here are a few of the different iterations we tossed around.&lt;/p&gt;
  145. &lt;iframe src=";amp;byline=0&amp;amp;portrait=0" width="440" height="248" frameborder="0" webkitAllowFullScreen allowFullScreen&gt;&lt;/iframe&gt;</description>
  146.       <pubDate>Thu, 03 Nov 2011 20:22:00 +0000</pubDate>
  147.       <guid></guid>
  148.       <link></link>
  149.     </item>
  150.     <item>
  151.       <dc:creator>Jason F.</dc:creator>
  152.       <title>INSIGHT: You break expectations by changing what someone…</title>
  153.       <description>&lt;p&gt;You break expectations by changing what someone&amp;#8217;s already used to. You change expectations by giving them something new. Understanding the difference is key to product design.&lt;/p&gt;</description>
  154.       <pubDate>Thu, 03 Nov 2011 18:11:00 +0000</pubDate>
  155.       <guid></guid>
  156.       <link></link>
  157.     </item>
  158.     <item>
  159.       <dc:creator>Ryan</dc:creator>
  160.       <title>QUOTE: Remember, a real engineer doesn&amp;#8217;t want…</title>
  161.       <description>&lt;p&gt;Remember, a real engineer doesn&amp;#8217;t want just a religion about how to solve the problem. Like &amp;#8216;object-oriented&amp;#8217;, or &amp;#8216;functional&amp;#8217;, or &amp;#8216;imperative&amp;#8217;, or &amp;#8216;logic programming&amp;#8217;. This piece of the problem wants to be a functional program. This piece of the program wants to be imperative. This piece wants to be object-oriented and guess what&amp;#8212;this piece want to be logic-based. And they all want to work together usefully, because of the way the problem is structured.&lt;/p&gt;
  162. &lt;p&gt;&amp;#8212;Gerald Jay Sussman, &lt;a href=""&gt;We Really Don&amp;#8217;t Know How to Compute!&lt;/a&gt;&lt;/p&gt;</description>
  163.       <pubDate>Tue, 01 Nov 2011 19:30:00 +0000</pubDate>
  164.       <guid></guid>
  165.       <link></link>
  166.     </item>
  167.     <item>
  168.       <dc:creator>Jamie</dc:creator>
  169.       <title>First Round Winners: Basecamp Tell a Friend Contest </title>
  170.       <description>&lt;p&gt;&lt;img src="" align="left" style="margin-top: 30px; margin-right: 20px; margin-bottom: 20px; border: none;" /&gt;&lt;/p&gt;
  173.     &lt;p&gt;We&amp;#8217;re happy to announce the first round of winners in our &lt;a href=""&gt;Basecamp Tell a Friend Contest&lt;/a&gt;:&lt;/p&gt;
  176.     &lt;p&gt;&lt;strong&gt;iPad Winners:&lt;/strong&gt;
  177. Darren from Victoria, Australia uses Basecamp at all three of his businesses: &lt;a href=""&gt;Pro Blogger&lt;/a&gt;, &lt;a href=""&gt;Digital Photography School&lt;/a&gt;, and &lt;a href=""&gt;FeelGooder&lt;/a&gt;. JoAnne from Smithtown, NY uses Basecamp at &lt;a href=""&gt;Lighthaus Design, Inc.&lt;/a&gt; and &lt;a href=""&gt;Getting Real Health&lt;/a&gt;.&lt;/p&gt;
  180.     &lt;p&gt;&lt;strong&gt;MacBook Air Winner:&lt;/strong&gt;
  181. Michael from New Hope, PA is a Basecamp fan, &lt;a href=""&gt;best-selling author, professional speaker, and entrepreneur&lt;/a&gt;.&lt;/p&gt;
  184.     &lt;p&gt;&lt;strong&gt;Tell your friends about Basecamp for a chance to win&lt;/strong&gt;&lt;br /&gt;
  185. We still have 9 more iPads, 2 MacBook Airs, and $5,000 cash to give away. Every friend that you sign up for Basecamp also gets $10 off their first month. Here’s how it works:&lt;/p&gt;
  188. &lt;ul&gt;
  189. &lt;li&gt;Sign up with your Basecamp account at &lt;a href=""&gt;;/a&gt;.&lt;/li&gt;
  190. &lt;li&gt;We&amp;#8217;ll give you a special link that you can tweet, share on Facebook, or email to your friends.&lt;/li&gt;
  191. &lt;li&gt;Every person that signs up from your link for a paid Basecamp plan will get $10 off their first month.&lt;/li&gt;
  192. &lt;li&gt;Every person you sign up counts as a &lt;a href=""&gt;chance to win one of our prizes&lt;/a&gt;.&lt;/li&gt;
  193. &lt;/ul&gt;
  195.     &lt;p&gt;This contest ends on January 2, 2012. &lt;a href=""&gt;Sign up today&lt;/a&gt; and start saving your friends $10 off their first month.&lt;/p&gt;</description>
  196.       <pubDate>Mon, 31 Oct 2011 13:43:00 +0000</pubDate>
  197.       <guid></guid>
  198.       <link></link>
  199.     </item>
  200.     <item>
  201.       <dc:creator>Jamis</dc:creator>
  202.       <title>QUOTE: When a friend calls to me from the road
  203. And…</title>
  204.       <description>&lt;p&gt;When a friend calls to me from the road&lt;br /&gt;
  205. And slows his horse to a meaning walk,&lt;br /&gt;
  206. I don&amp;#8217;t stand still and look around&lt;br /&gt;
  207. On all the hills I haven&amp;#8217;t hoed,&lt;br /&gt;
  208. And shout from where I am, What is it?&lt;br /&gt;
  209. No, not as there is a time to talk.&lt;br /&gt;
  210. I thrust my hoe in the mellow ground,&lt;br /&gt;
  211. Blade-end up and five feet tall,&lt;br /&gt;
  212. And plod: I go up to the stone wall&lt;br /&gt;
  213. For a friendly visit.&lt;/p&gt;
  214. &lt;p&gt;&amp;#8212;Robert Frost, &amp;#8220;A Time to Talk&amp;#8221;&lt;/p&gt;</description>
  215.       <pubDate>Fri, 28 Oct 2011 14:40:00 +0000</pubDate>
  216.       <guid></guid>
  217.       <link></link>
  218.     </item>
  219.     <item>
  220.       <dc:creator>Jason F.</dc:creator>
  221.       <title>A little customer get together in Chicago</title>
  222.       <description>&lt;p&gt;Last week our whole company got together. We try to do this a few times a year. We fly everyone in and all spend a few days together in Chicago. We share what we&amp;#8217;re working on, we talk, we debate, we review, we get some work done, and we have some fun.&lt;/p&gt;
  225.     &lt;p&gt;Usually we reserve one of the nights to all go out to dinner together, but this time we decided to host some of our Chicago-based customers at a party at our office instead. We invited about 50 customers &amp;#8211; some new, some old &amp;#8211; and all hung out for a few hours. We met, exchanged ideas, fielded feature requests, and just got to know each other. Everyone had a great time. Thanks to everyone who came.&lt;/p&gt;
  228.     &lt;p&gt;We put together a little video to share.&lt;/p&gt;
  231. &lt;iframe src=";amp;byline=0&amp;amp;portrait=0" width="530" height="298" frameborder="0" webkitAllowFullScreen allowFullScreen&gt;&lt;/iframe&gt;
  233.     &lt;p&gt;&lt;br /&gt;&lt;/p&gt;
  236.     &lt;p&gt;Special thanks to Steve Dale from &lt;a href=""&gt;Gyro&lt;/a&gt;, Jimmy Spencer Jr. from &lt;a href=""&gt;Love Without Agenda&lt;/a&gt;, Ray Hightower from &lt;a href=""&gt;Wisdom Group&lt;/a&gt;, Ben Greiner from &lt;a href=""&gt;Forget Computers&lt;/a&gt;, and Michael Carney from &lt;a href=""&gt;&lt;span class="caps"&gt;MWC&lt;/span&gt; Accounting&lt;/a&gt; for taking some extra time to be interviewed on camera.&lt;/p&gt;</description>
  237.       <pubDate>Tue, 25 Oct 2011 21:11:00 +0000</pubDate>
  238.       <guid></guid>
  239.       <link></link>
  240.     </item>
  241.     <item>
  242.       <dc:creator>Jason F.</dc:creator>
  243.       <title>QUOTE: And just as Steve loved ideas, and loved…</title>
  244.       <description>&lt;p&gt;And just as Steve loved ideas, and loved making stuff, he treated the process of creativity with a rare and a wonderful reverence. You see, I think he better than anyone understood that while ideas ultimately can be so powerful, they begin as fragile, barely formed thoughts, so easily missed, so easily compromised, so easily just squished.&lt;/p&gt;
  245. &lt;p&gt;&amp;#8212;Jonathan Ive at the &lt;a href=";#38;v=nPUsuY8JZJI"&gt;Steve Jobs Tribute&lt;/a&gt; on the Apple campus. His talk starts around 47:17 right after Tim Cook introduces him.&lt;/p&gt;</description>
  246.       <pubDate>Tue, 25 Oct 2011 13:31:00 +0000</pubDate>
  247.       <guid></guid>
  248.       <link></link>
  249.     </item>
  250.     <item>
  251.       <dc:creator>Jason Z.</dc:creator>
  252.       <title>INSIGHT: Who is the star of your product? Do you want…</title>
  253.       <description>&lt;p&gt;Who is the star of your product? Do you want people to think your product is awesome, or would you rather they felt awesome about themselves because they used your product? Does the UI say &amp;#8220;Look at how beautiful this app is&amp;#8221; or &amp;#8220;Look at how beautiful your content is&amp;#8221;?&lt;/p&gt;</description>
  254.       <pubDate>Thu, 20 Oct 2011 19:16:00 +0000</pubDate>
  255.       <guid></guid>
  256.       <link></link>
  257.     </item>
  258.     <item>
  259.       <dc:creator>37signals</dc:creator>
  260.       <title>New in Highrise: LinkedIn profiles</title>
  261.       <description>&lt;p&gt;Today we’re introducing LinkedIn profiles in &lt;a href=""&gt;Highrise&lt;/a&gt;.
  262. You can now add LinkedIn URLs to your contacts to see their profiles in Highrise instantly.
  263. You’ll have easy access to all the specialties and qualifications listed in their LinkedIn profiles.&lt;/p&gt;
  266.     &lt;p&gt;&lt;img src="" /&gt;&lt;/p&gt;
  269. &lt;h2&gt;How to set it up&lt;/h2&gt;
  271.     &lt;p&gt;It&amp;#8217;s simple: Just go to a contact, click the &amp;#8220;Edit&amp;#8221; link in the top right corner, then scroll down to the &amp;#8220;Social media&amp;#8221; section on the edit screen. Enter the person&amp;#8217;s public LinkedIn profile &lt;span class="caps"&gt;URL&lt;/span&gt; and click save. Then you&amp;#8217;ll see a &amp;#8220;LinkedIn&amp;#8221; tab at the top of their contact page. Click that link and you&amp;#8217;ll have access to their LinkedIn profile.&lt;/p&gt;
  274.     &lt;p&gt;To make the most of this feature you’ll need to have an account on LinkedIn.
  275. Highrise uses your LinkedIn account to grab the latest profile each time you view one of your contacts.
  276. This ensures the profile information you see is always up to date.&lt;/p&gt;
  279.     &lt;p&gt;Integration with LinkedIn has been a popular customer request since we launched Highrise.
  280. We’re pleased to make it a reality today and we hope it makes Highrise more useful to you everyday.&lt;/p&gt;</description>
  281.       <pubDate>Tue, 18 Oct 2011 12:40:00 +0000</pubDate>
  282.       <guid></guid>
  283.       <link></link>
  284.     </item>
  285.     <item>
  286.       <dc:creator>Ryan</dc:creator>
  287.       <title>Watch Ryan sketch and code a UI from scratch on PeepCode</title>
  288.       <description>&lt;p&gt;Last month the folks from PeepCode visited our office and asked to record my design process. Geoffrey told me not to prepare anything. He said he&amp;#8217;d show up with a sample problem and simply record whatever I did with it. The result is two 75-minute videos (&lt;a href=""&gt;Part One&lt;/a&gt;, &lt;a href=""&gt;Part Two&lt;/a&gt;) that show my thought process step-by-step, starting with paper sketches and then moving on to &lt;span class="caps"&gt;HTML&lt;/span&gt;/CSS.&lt;/p&gt;
  291.     &lt;p&gt;The hard thing about demonstrating design is the sample problem. The problem should be simple enough that the details don&amp;#8217;t bog down the audience, but complicated enough that you run into real-life conflicts and constraints.&lt;/p&gt;
  294.     &lt;p&gt;Fortunately Geoffrey picked a really good sample domain. He asked me to design a UI for picking the top five finishers out of 200 participants in a pro bicycling race. The task was rich and interesting enough that we spent the first 75 minutes purely sketching and analyzing the approach.&lt;/p&gt;
  297.     &lt;p&gt;The first video, &lt;a href=""&gt;Part One&lt;/a&gt;, covers the sketching process. A lot of good material came out of this section, including:&lt;/p&gt;
  300. &lt;ul&gt;
  301. &lt;li&gt;How to tackle a UI problem by dividing it into tasks that each have a beginning, middle and end&lt;/li&gt;
  302. &lt;li&gt;How to use sketching as a response to uncertainty, and when to stop sketching and move on to &lt;span class="caps"&gt;HTML&lt;/span&gt;&lt;/li&gt;
  303. &lt;li&gt;How to focus on the most natural solution so that people will intuitively grasp a design&lt;/li&gt;
  304. &lt;li&gt;How to focus your design process on conflicts and friction points, attacking them one by one until the design works&lt;/li&gt;
  305. &lt;/ul&gt;
  307.     &lt;p&gt;This video also gave me a chance to explain the UI design process through an analogy to software testing. Kent Beck&amp;#8217;s &lt;a href=""&gt;Test-Driven Development&lt;/a&gt; had a huge influence on me, and I&amp;#8217;ve always had trouble explaining the connection. In both videos I continually refer to setting up &amp;#8220;tests&amp;#8221; &amp;mdash; specific things in the design that aren&amp;#8217;t working or aren&amp;#8217;t resolved &amp;mdash; and then design against those tests until they &amp;#8220;pass&amp;#8221; (that is, until the problem goes away). This loose analogy articulates that tricky and hard-to-pin-down process where a designer continually moves their focus among pieces of a problem and along the way settles conflicts step-by-step in a constructive sequence.&lt;/p&gt;
  310.     &lt;p&gt;I think the process will be interesting to both designers and coders. Designers can compare the process to their own, while coders can use the analogies to software testing to see design as an extension of concepts they already know.&lt;/p&gt;
  313.     &lt;p&gt;In the second video, &lt;a href=""&gt;Part Two&lt;/a&gt;, I take the sketches and ideas from the first session and build them out in &lt;span class="caps"&gt;HTML&lt;/span&gt; and &lt;span class="caps"&gt;CSS&lt;/span&gt;. Along the way I dip in and out of Photoshop, explaining the time and place for each tool.&lt;/p&gt;
  316.     &lt;p&gt;Part Two especially focuses on getting quick results in the browser. I sketch out dom elements, give them classes to communicate their purpose, and  gradually decorate them with inline styles until the design comes together in the browser.&lt;/p&gt;
  319.     &lt;p&gt;I would prefer videos like this to be free. But Geoffrey had the idea to begin with and his PeepCode team did all the hard work. I just showed up one Friday morning for a couple hours of design practice. So if the material is useful to you I hope you&amp;#8217;ll support their effort and buy the videos at $12/each.&lt;/p&gt;
  322.     &lt;p&gt;Here are the links:&lt;/p&gt;
  325. &lt;ol&gt;
  326. &lt;li&gt;&lt;a href=""&gt;PeepCode Play by Play: Ryan Singer Part One&lt;/a&gt;&lt;/li&gt;
  327. &lt;li&gt;&lt;a href=""&gt;PeepCode Play by Play: Ryan Singer Part Two&lt;/a&gt;&lt;/li&gt;
  328. &lt;/ol&gt;
  330.     &lt;p&gt;There&amp;#8217;s also a &lt;a href=""&gt;10 minute preview&lt;/a&gt; on the Part One page.&lt;/p&gt;
  333.     &lt;p&gt;I hope they&amp;#8217;re useful!&lt;/p&gt;</description>
  334.       <pubDate>Sun, 16 Oct 2011 22:35:00 +0000</pubDate>
  335.       <guid></guid>
  336.       <link></link>
  337.     </item>
  338.     <item>
  339.       <dc:creator>Jason F.</dc:creator>
  340.       <title>INSIGHT: Some designs are evil &amp;#8211; you know they…</title>
  341.       <description>&lt;p&gt;Some designs are evil &amp;#8211; you know they&amp;#8217;re bad right away. Others are like love at first sight. And some you just need to live with for a while before making up your mind.&lt;/p&gt;</description>
  342.       <pubDate>Sat, 15 Oct 2011 15:45:00 +0000</pubDate>
  343.       <guid></guid>
  344.       <link></link>
  345.     </item>
  346.     <item>
  347.       <dc:creator>37signals</dc:creator>
  348.       <title>Fast and great support from the 37signals team</title>
  349.       <description>&lt;p&gt;Our support team works hard every day to make our customers happy, and we&amp;#8217;re always proud to &lt;a href=""&gt;show how great a job they do&lt;/a&gt;.&lt;/p&gt;
  352.     &lt;p&gt;In addition to making customers happy, our fantastic team also answers questions &lt;b&gt;&lt;i&gt;fast&lt;/i&gt;&lt;/b&gt;. Across the last 500 new cases we&amp;#8217;ve received during our normal hours, we&amp;#8217;ve responded to 97% in less than hour, with the average case answered in 14 minutes and solved in 25 minutes.&lt;/p&gt;
  355.     &lt;p&gt;Our team has been steadily improving at this too. Over the last few months, we&amp;#8217;ve steadily cut down response times, all while maintaining or improving customer happiness.&lt;/p&gt;
  358.     &lt;p&gt;&lt;a href = " " target="_blank"&gt;&lt;img src="" width="530" style="border:none" /&gt;&lt;/a&gt;&lt;/p&gt;
  361.     &lt;p&gt;Congratulations to Michael, Ann, Kristin, Merissa, Joan, and Chase!&lt;/p&gt;</description>
  362.       <pubDate>Thu, 13 Oct 2011 16:35:00 +0000</pubDate>
  363.       <guid></guid>
  364.       <link></link>
  365.     </item>
  366.     <item>
  367.       <dc:creator>Jason F.</dc:creator>
  368.       <title>Questions I ask when reviewing a design</title>
  369.       <description>&lt;p&gt;I&amp;#8217;ve been thinking more about how I review a design &amp;#8211; both my own and someone else&amp;#8217;s. So over the past couple days I&amp;#8217;ve been writing down every question I&amp;#8217;ve been asking when I look at a design-in-progress. Some of these I say out loud, some just go through my head, some are in person, others are posted to Basecamp or Campfire.&lt;/p&gt;
  372.     &lt;p&gt;These are in no particular order, and I don&amp;#8217;t ask all of them every time.&lt;/p&gt;
  375.     &lt;ul&gt;
  376.     &lt;li&gt;What does it say?&lt;/li&gt;
  377.         &lt;li&gt;What does it mean?&lt;/li&gt;
  378.         &lt;li&gt;Is what it says and what it means the same thing?&lt;/li&gt;
  379.         &lt;li&gt;Do we want that?&lt;/li&gt;
  380.         &lt;li&gt;Why do we need to say that here?&lt;/li&gt;
  381.         &lt;li&gt;If you stopped reading here, what&amp;#8217;s the message?&lt;/li&gt;
  382.         &lt;li&gt;What&amp;#8217;s the take away after 8 seconds?&lt;/li&gt;
  383.         &lt;li&gt;How does this make you feel?&lt;/li&gt;
  384.         &lt;li&gt;What&amp;#8217;s down below?&lt;/li&gt;
  385.         &lt;li&gt;How else can we say this?&lt;/li&gt;
  386.         &lt;li&gt;What&amp;#8217;s memorable about this?&lt;/li&gt;
  387.         &lt;li&gt;What&amp;#8217;s that for?&lt;/li&gt;
  388.         &lt;li&gt;Who needs to know that?&lt;/li&gt;
  389.         &lt;li&gt;Who needs to see that?&lt;/li&gt;
  390.         &lt;li&gt;How does that change behavior?&lt;/li&gt;
  391.         &lt;li&gt;What&amp;#8217;s the payoff?&lt;/li&gt;
  392.         &lt;li&gt;What does someone know now that they didn&amp;#8217;t know before?&lt;/li&gt;
  393.         &lt;li&gt;How does that work?&lt;/li&gt;
  394.         &lt;li&gt;Why is that worth a click?&lt;/li&gt;
  395.         &lt;li&gt;Is that worth scrolling?&lt;/li&gt;
  396.         &lt;li&gt;What&amp;#8217;s the simpler version of this?&lt;/li&gt;
  397.         &lt;li&gt;Are we assuming too much?&lt;/li&gt;
  398.         &lt;li&gt;Why that order?&lt;/li&gt;
  399.         &lt;li&gt;Why would this make them choose that?&lt;/li&gt;
  400.         &lt;li&gt;What does a more polished version of this look like?&lt;/li&gt;
  401.         &lt;li&gt;Why would someone leave at this point?&lt;/li&gt;
  402.         &lt;li&gt;What&amp;#8217;s missing?&lt;/li&gt;
  403.         &lt;li&gt;Why are we saying this twice?&lt;/li&gt;
  404.         &lt;li&gt;Is it worth pulling attention away from that?&lt;/li&gt;
  405.         &lt;li&gt;Does that make it clearer?&lt;/li&gt;
  406.         &lt;li&gt;What&amp;#8217;s the obvious next step?&lt;/li&gt;
  407.         &lt;li&gt;How would someone know that?&lt;/li&gt;
  408.         &lt;li&gt;Would it matter if someone missed that?&lt;/li&gt;
  409.         &lt;li&gt;Does that make it easier or harder?&lt;/li&gt;
  410.         &lt;li&gt;Would this be better as a sentence or a picture?&lt;/li&gt;
  411.         &lt;li&gt;Where&amp;#8217;s the verb?&lt;/li&gt;
  412.         &lt;li&gt;Why is that there?&lt;/li&gt;
  413.         &lt;li&gt;What matters here?&lt;/li&gt;
  414.         &lt;li&gt;What would happen if we got rid of that?&lt;/li&gt;
  415.         &lt;li&gt;Why isn&amp;#8217;t that clear?&lt;/li&gt;
  416.         &lt;li&gt;Why is this better?&lt;/li&gt;
  417.         &lt;li&gt;How can we make this more obvious?&lt;/li&gt;
  418.         &lt;li&gt;What happens when this expands?&lt;/li&gt;
  419.         &lt;li&gt;If we got rid of this, does that still work?&lt;/li&gt;
  420.         &lt;li&gt;Is it obvious what happens next?&lt;/li&gt;
  421.         &lt;li&gt;What just happened?&lt;/li&gt;
  422.         &lt;li&gt;Where&amp;#8217;s the idea?&lt;/li&gt;
  423.         &lt;li&gt;What problem is that solving?&lt;/li&gt;
  424.         &lt;li&gt;How does this change someone&amp;#8217;s mind?&lt;/li&gt;
  425.         &lt;li&gt;What makes this a must have?&lt;/li&gt;
  426.     &lt;/ul&gt;</description>
  427.       <pubDate>Tue, 11 Oct 2011 16:20:00 +0000</pubDate>
  428.       <guid></guid>
  429.       <link></link>
  430.     </item>
  431.     <item>
  432.       <dc:creator>David</dc:creator>
  433.       <title>Why programs become territorial</title>
  434.       <description>&lt;p&gt;&amp;#8220;Can you ask Sam about that? Stacker is his domain&amp;#8221;, &amp;#8220;I&amp;#8217;d rather let Josh look at the router, he wrote it&amp;#8221;, &amp;#8220;Jon is better versed in associations, send it to him&amp;#8221;.&lt;/p&gt;
  437.     &lt;p&gt;The natural progression of programs is towards the territorial. When a programmer has weaved an intricate web of considerable complexity, others are loathe to enter his lair and he is loathe for them to do so.&lt;/p&gt;
  440.     &lt;p&gt;This is despite the fact that we all agree that it&amp;#8217;s bad for programs to become territorial. When only one or a few people know how to work on something, you get bottlenecks where progress is stunted until the master is ready. You risk the hit-by-a-bus factor where nobody knows how the system works if the master leaves. You ensure the annoyance of stakeholders who can&amp;#8217;t understand why another minion can&amp;#8217;t fix his urgent problem.&lt;/p&gt;
  443.     &lt;p&gt;But this problem can&amp;#8217;t be solved with a slogan. You can proclaim that &amp;#8220;we shouldn&amp;#8217;t have territorial parts of our program&amp;#8221; until you turn blue, but nothing is going to change until you accept the cost of avoidance.&lt;/p&gt;
  446.     &lt;p&gt;The first step of acceptance is to recognize that sending someone fresh in to fix a single issue in a complex part of the code is expensive. It&amp;#8217;s going to take Pratik five to ten times the effort to fix a single issue in Stacker that it&amp;#8217;s going to take Sam. And the odds are that even that is not enough to appreciate the internal coherency of the system, which means that the fix is likely to be a butcher&amp;#8217;s job, and Sam will have to rewrite it afterwards anyway.&lt;/p&gt;
  449.     &lt;p&gt;To broaden the base of knowledge, you&amp;#8217;re going to have to let someone else not only spend considerable effort getting up to speed. Then you&amp;#8217;re going to have them deal with more than just a quick fix. Let them deal with a raft of issues and let them spend the time of the original creator to learn it all.&lt;/p&gt;
  452.     &lt;p&gt;To do all that, they can&amp;#8217;t do anything else at the same time. That feature you want do is now going to be pushed a few days or a a week out. Until you&amp;#8217;re ready to delay things you really want done, it&amp;#8217;s fruitless to bemoan that parts of the code base territorial.&lt;/p&gt;</description>
  453.       <pubDate>Tue, 11 Oct 2011 15:49:00 +0000</pubDate>
  454.       <guid></guid>
  455.       <link></link>
  456.     </item>
  457.     <item>
  458.       <dc:creator>David</dc:creator>
  459.       <title>QUESTION: The home button on the iPhone 4 stopped working…</title>
  460.       <description>&lt;p&gt;The home button on the iPhone 4 stopped working properly for both Jason and I recently. Requiring hard presses or multiple tries to work. It appears that lots of people have this problem. Has it happened to you yet? Let&amp;#8217;s track this.&lt;/p&gt;</description>
  461.       <pubDate>Fri, 07 Oct 2011 21:07:00 +0000</pubDate>
  462.       <guid></guid>
  463.       <link></link>
  464.     </item>
  465.     <item>
  466.       <dc:creator>Jason F.</dc:creator>
  467.       <title>Steve Jobs changed</title>
  468.       <description>&lt;p&gt;He changed computers.&lt;br /&gt;
  469. He changed software.&lt;br /&gt;
  470. He changed design.&lt;br /&gt;
  471. He changed publishing.&lt;br /&gt;
  472. He changed film.&lt;br /&gt;
  473. He changed music.&lt;br /&gt;
  474. He changed advertising.&lt;br /&gt;
  475. He changed retail.&lt;br /&gt;
  476. He changed business.&lt;/p&gt;
  479.     &lt;p&gt;He changed beige.&lt;/p&gt;
  482.     &lt;p&gt;He changed expectations.&lt;br /&gt;
  483. He changed our minds.&lt;br /&gt;&lt;/p&gt;
  486.     &lt;p&gt;He changed them.&lt;br /&gt;
  487. He changed us.&lt;br /&gt;
  488. He changed you.&lt;/p&gt;
  491.     &lt;p&gt;&amp;#8220;Don&amp;#8217;t be sad because it&amp;#8217;s over. Smile because it happened.&amp;#8221; &amp;#8211; Dr. Seuss&lt;/p&gt;
  494.     &lt;p&gt;&lt;em&gt;Now what are you going to change?&lt;/em&gt;&lt;/p&gt;</description>
  495.       <pubDate>Thu, 06 Oct 2011 14:02:00 +0000</pubDate>
  496.       <guid></guid>
  497.       <link></link>
  498.     </item>
  499.     <item>
  500.       <dc:creator>Ann</dc:creator>
  501.       <title>37colors</title>
  502.       <description>&lt;p&gt;This weekend during the Ravenswood Art Walk, I visited &lt;a href=""&gt;Lorna&amp;#8217;s Laces&lt;/a&gt;. They hand-dye yarns in some really beautiful color combinations. I took some photos to share, because sometimes it&amp;#8217;s nice to look at pretty things!&lt;/p&gt;
  505.     &lt;p&gt;Designers, how do you put colors together? Where do you find inspiration?&lt;/p&gt;
  508.     &lt;p&gt;&lt;img src="" /&gt;&lt;/p&gt;
  509. &lt;p&gt;&lt;a href=""&gt;More...&lt;/a&gt;&lt;/p&gt;</description>
  510.       <pubDate>Mon, 03 Oct 2011 22:42:00 +0000</pubDate>
  511.       <guid></guid>
  512.       <link></link>
  513.     </item>
  514.     <item>
  515.       <dc:creator>Noah</dc:creator>
  516.       <title>The rhythms of 37signals</title>
  517.       <description>&lt;p&gt;I was thinking this morning about what I perceived to be my normal working pattern&amp;#8212;lots in the morning, then tapering out from mid-day on with an occasional bump in the evenings. I wanted to see if this was quantifiable through git logs, and I decided to look across a wide range of our repositories.&lt;/p&gt;
  520.     &lt;p&gt;The chart below shows the portion of each person&amp;#8217;s commits that occur within a given hour of the day in their local time.&lt;/p&gt;
  523.     &lt;p&gt;&lt;a href="" target="_blank"&gt;&lt;img src="" width='550' style="border: none;"/&gt;&lt;/a&gt;&lt;/p&gt;
  526.     &lt;p&gt;As you can see, there&amp;#8217;s a wide range in preferred working hours &amp;#8211; one of the great advantages of working in &lt;a href=""&gt;slow time&lt;/a&gt; is that this is absolutely fine. There&amp;#8217;s enough overlap in hours for people to be able to work together, but enough flexibility to work when you want to.&lt;/p&gt;</description>
  527.       <pubDate>Thu, 29 Sep 2011 20:47:00 +0000</pubDate>
  528.       <guid></guid>
  529.       <link></link>
  530.     </item>
  531.   </channel>
  532. </rss>
RAW Paste Data