{"id":495,"date":"2012-05-28T13:46:19","date_gmt":"2012-05-28T17:46:19","guid":{"rendered":"http:\/\/wcarss.ca\/log\/?p=495"},"modified":"2012-05-28T13:56:25","modified_gmt":"2012-05-28T17:56:25","slug":"readin","status":"publish","type":"post","link":"https:\/\/wcarss.ca\/log\/2012\/05\/readin\/","title":{"rendered":"Reading"},"content":{"rendered":"<p>Any time I need to answer a question about REST, I end up spending 2-3 hours reading. I&#8217;m not sure if that&#8217;s a good thing or a bad thing&#8230; anyway, while doing some of that reading I was on InfoQ at <a title=\"a bunch of REST anti-patterns (2008)\" href=\"http:\/\/www.infoq.com\/articles\/rest-anti-patterns\">this post<\/a>, and that lead to <a title=\"Sam Ruby and Leo Richardson talkin' REST (2007)\" href=\"http:\/\/www.infoq.com\/articles\/richardson-ruby-restful-ws\">this post<\/a>, and that lead to <a title=\"there's a typo in the link from the previous post! I emailed stefan about it -- this post inspired leo richardson to write a book about REST\" href=\"http:\/\/lesscode.org\/2006\/03\/19\/rest-wins-noone-goes-home\/\">this post<\/a>, and at the end of the post the guy said:<\/p>\n<blockquote><p>So run away screaming from anyone who dismisses these as \u201cjust implementation details\u201d \u2013 implementation details matter. They cost money, and break hearts.<\/p><\/blockquote>\n<p>And it&#8217;s an excellent quote. I&#8217;ve still got <a title=\"linked from the post above\" href=\"http:\/\/naeblis.cx\/rtomayko\/2005\/05\/28\/ibm-poop-heads\">this page<\/a>, which looks like its mime-type is wrong, and <a title=\"oooooh neat\" href=\"http:\/\/en.wikipedia.org\/wiki\/Fallacies_of_Distributed_Computing\">this wikipedia page<\/a>, because it looks interesting, and <a title=\"more specifically the codebase behind it\" href=\"http:\/\/www.blosxom.com\/\">this website<\/a>, because it&#8217;s what inspired Sam Ruby to get off his SOAPbox to take a little REST (haha I&#8217;m <em>so<\/em> clever) and <a title=\"all about web caching! something I don't understand \/at all\/\" href=\"http:\/\/www.mnot.net\/cache_docs\/\">this article<\/a> because it seriously sounds like an insanely useful read. I might save it for another day.\u00a0This is a good time to just toss <a title=\"insanely good introduction to javascript\/dom events!\" href=\"http:\/\/www.quirksmode.org\/js\/introevents.html\">this<\/a> in here, which should have been included yesterday, but wasn&#8217;t. It&#8217;s about the javascript event model, which prior to reading that article, I had never really considered the existence of, and it&#8217;s made so much magic plain in my mind.\u00a0<a href=\"http:\/\/www.quirksmode.org\/\">quirksmode<\/a> and <a href=\"http:\/\/www.infoq.com\/\">infoQ<\/a> are really excellent websites, by the way.<\/p>\n<p>Echoing yesterday&#8217;s words, every time I look into the internet, it grows deeper. I can&#8217;t help but wonder about whether there&#8217;s something worthy hidden in rpc-style communication, but I&#8217;ve heard the horror stories, and I know that no technology is a panacea, even if working with JSON tends to feel an order of magnitude less painful than working with XML, and all the big SOAP things I&#8217;ve worked with were XML-based.<\/p>\n<p>Also, I completed day 21 of blogging, yesterday. My last two posts kind of sucked. Well, no, they really sucked. They&#8217;re just me rambling! I need to have a focus and a plan in the future, or at least a bunch of exposition and links like I&#8217;ve got here.<\/p>\n<h2>What&#8217;s next<\/h2>\n<p>My plan for the next 21 days is ambitious, and maybe a little reckless. I&#8217;m going to be speed reading. Here&#8217;s how it breaks down, with each phase lasting a full week:<\/p>\n<p>Phase 1: Read at least 10 pages of at least 2 books, every day.<br \/>\nPhase 2: Read at least 20 pages of at least 3 books, every day.<br \/>\nPhase 3: Read at least 30 pages of at least 4 books, every day.<\/p>\n<p>I&#8217;m going to review this plan as I go forward, because I have absolutely no idea how realistic it is. It ends with me reading 120 pages a day, which at the moment feels totally outside of my ability to fit into my life. It starts with reading 20 pages a day, which feels doable, but like it&#8217;ll take effort. If I&#8217;m going to reach a point where I&#8217;m burning through 120 pages of material a day, then I think I&#8217;ll have to be speed reading. I&#8217;ll definitely need to break 200 words per minute &#8212; let&#8217;s make some estimates:<\/p>\n<p>A book has on average 50 lines per page (I know, most have 40, but I&#8217;m going to be reading the Feynman Lectures on Physics as part of this, which have ~60 lines of text per page), and has, on average, about 14 words per line (again I&#8217;m pulling this up from 12ish because the Feynman book averages about 16). So we&#8217;ve got 50 * 14 = 700 words per page. 20*700 = 14000 words, and at 200 wpm that means 70 minutes of reading. To start. On the high end, 120 pages, we&#8217;ve got 6 times as much, which means 420 minutes of reading. That&#8217;s insane.<\/p>\n<p>If I can get up to 500 wpm, I can cut 70 minutes down to 28 minutes, and 420 down to 168. I think I can manage to read for 3 hours in a day, but seven is impossible for me. If I can get up to 800 words per minute (my dream goal), then I could read 120 pages in just 105 minutes. Just under 2 hours of solid reading every day. Scary, but I&#8217;d love to accomplish it.<\/p>\n<p>Today, I&#8217;ll just read my normal speed on whatever books I have around two of (The Illiad, Red Mars, Feynman, and Walden). Starting tomorrow I&#8217;ll grab a book that I&#8217;ve read previously so that I can focus on speed without worrying about my loss of comprehension. My other book will be Stand on Zanzibar, which has a &#8220;stream of content&#8221; delivery, and may be best consumed at a lightning-fast pace with slight misunderstanding. Blog posts for the next 21 days will be responses to or summaries of the content I&#8217;ve read; they may be done with a day&#8217;s lag. Not sure yet! And as usual, I&#8217;ll occasionally leave updates with regards to the process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Any time I need to answer a question about REST, I end up spending 2-3 hours reading. I&#8217;m not sure if that&#8217;s a good thing or a bad thing&#8230; anyway, while doing some of that reading I was on InfoQ at this post, and that lead to this post, and that lead to this post, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/495"}],"collection":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/comments?post=495"}],"version-history":[{"count":5,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/495\/revisions"}],"predecessor-version":[{"id":500,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/posts\/495\/revisions\/500"}],"wp:attachment":[{"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/media?parent=495"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/categories?post=495"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wcarss.ca\/log\/wp-json\/wp\/v2\/tags?post=495"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}