<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Many, many, blog posts by Alex Kessinger (frequent inventor of words). on Rumproarious</title>
    <link>https://rumproarious.com/</link>
    <description>Recent content in Many, many, blog posts by Alex Kessinger (frequent inventor of words). on Rumproarious</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 10 Apr 2026 12:00:00 -0600</lastBuildDate><atom:link href="https://rumproarious.com/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>It&#39;s Going to Get Weird</title>
      <link>https://rumproarious.com/2026/04/10/its-going-to-get-weird/</link>
      <pubDate>Fri, 10 Apr 2026 12:00:00 -0600</pubDate>
      
      <guid>https://rumproarious.com/2026/04/10/its-going-to-get-weird/</guid>
      <description>I was a front-end engineer before the iPhone existed.
As apps increased in use, a thought occurred to me: what if websites just&amp;hellip; disappear? What does that mean for my job? My gut reaction was I guess it&amp;rsquo;s time to learn Objective-C. I tried it. It wasn&amp;rsquo;t fun. It wasn&amp;rsquo;t my world.
Cut to today, Websites didn&amp;rsquo;t disappear. But more importantly, I realized my job was never &amp;ldquo;writing front-end code.&amp;rdquo; My job was delivering value to people sustainably and efficiently.</description>
    </item>
    
    <item>
      <title>Your File System Is Already a Graph Database</title>
      <link>https://rumproarious.com/2026/04/04/your-file-system-is-already-a-graph-database/</link>
      <pubDate>Sat, 04 Apr 2026 10:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/2026/04/04/your-file-system-is-already-a-graph-database/</guid>
      <description>Karpathy recently posted about using LLMs to build personal knowledge bases — collecting raw sources into a directory, having an LLM &amp;ldquo;compile&amp;rdquo; them into a wiki of interlinked markdown files, and viewing the whole thing in Obsidian. He followed it up with an &amp;ldquo;idea file,&amp;rdquo; a gist you can hand to your agent so it builds the system for you.
This is a great idea, I&amp;rsquo;ve been doing some form of this for over a decade.</description>
    </item>
    
    <item>
      <title>The StaffEng Podcast is Back</title>
      <link>https://rumproarious.com/2026/01/21/the-staffeng-podcast-is-back/</link>
      <pubDate>Wed, 21 Jan 2026 10:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/2026/01/21/the-staffeng-podcast-is-back/</guid>
      <description>After a long hiatus, David and I are bringing the StaffEng podcast back. We&amp;rsquo;re back because our work is changing dramatically, weekly, and we want want to learn from folks who are riding this wave with us.
You can read more here: We&amp;rsquo;re Back
When we started the podcast back in 2021, we were exploring what it meant to be a Staff-plus engineer. We talked to practitioners about setting technical direction, mentorship, sponsorship, and all the things that set senior individual contributors apart.</description>
    </item>
    
    <item>
      <title>Curiosity: An Unreasonably Powerful Tool</title>
      <link>https://rumproarious.com/2023/06/11/curiosity-an-unreasonably-powerful-tool/</link>
      <pubDate>Sun, 11 Jun 2023 09:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2023/06/11/curiosity-an-unreasonably-powerful-tool/</guid>
      <description>You want to get hard things done, and you want to tackle progressively bigger things. We all do. If you are reading this you chose to do a hard thing. You probably use hard work and elbow grease to do the job. While that kind of work is valuable, at a certain level of complexity, those tools loose their usefulness. And yet, you still want to do the hard thing. This is a good news/bad news deal.</description>
    </item>
    
    <item>
      <title>A Morbid Sense of Pride</title>
      <link>https://rumproarious.com/2022/12/17/a-morbid-sense-of-pride/</link>
      <pubDate>Sat, 17 Dec 2022 16:38:21 -0700</pubDate>
      
      <guid>https://rumproarious.com/2022/12/17/a-morbid-sense-of-pride/</guid>
      <description>Once you&amp;rsquo;ve decided to adopt a new view of safety, and want to help an organization change, how do you know if you are changing anything? How do you know if you are successful? Especially considering the total organization overhaul you hope to achieve. It can be useful to identify some markers somewhere between nothing, and total success. What are some markers that demonstrate we are on our way?
A recent incident, which involved a system I am partially accountable/responsible for, left me with a morbid sense of pride.</description>
    </item>
    
    <item>
      <title>How my biggest work failure led to success</title>
      <link>https://rumproarious.com/2022/04/10/how-my-biggest-work-failure-led-to-success/</link>
      <pubDate>Sun, 10 Apr 2022 01:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2022/04/10/how-my-biggest-work-failure-led-to-success/</guid>
      <description>From my tiny West Berkeley apartment, with my family asleep upstairs, I typed into the search box: “python Berkeley”. It was 2015 and for the past 6 years, I commuted hours a day all over the Bay Area. My goal was eventually to create a startup. But, My latest gig had imploded and I was tired and mis-wanting to be a startup founder was reason number one . While I still enjoyed programming, I needed a refuge from the hustle, if possible a job I could walk to.</description>
    </item>
    
    <item>
      <title>Expertise is all around - it&#39;s just not evenly distributed.</title>
      <link>https://rumproarious.com/2020/12/22/expertise-is-all-around-its-just-not-evenly-distributed./</link>
      <pubDate>Tue, 22 Dec 2020 01:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2020/12/22/expertise-is-all-around-its-just-not-evenly-distributed./</guid>
      <description>Writing down remediation items is a seductively simple outcome for a post-mortem. It’s satisfying. &amp;ldquo;Yea, there was an issue but if we do these 3 things, we will be better off&amp;rdquo;. It’s all wrapped up in a nice bow. Although remediation feels like the right outcome, it’s not the most powerful reason to do a post-mortem. The most valuable part of a post-mortem is the ability to radiate expertise into your organization.</description>
    </item>
    
    <item>
      <title>Debriefing Facilitation Guide </title>
      <link>https://rumproarious.com/notes/debriefing-facilitation-guide/</link>
      <pubDate>Tue, 22 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/debriefing-facilitation-guide/</guid>
      <description>Software is key to a growing number of businesses. Which means working with software safely isn’t just prudent, it’s existential to many. The wrong kind of accident could wipe you out. Investigating incidents is a technique many businesses use to remediate issues that led to accidents in the first place. They hope it will help them reduce the number and scope of accidents in the future. While traditional accident investigation is problematic, Etsy use&amp;rsquo;s a &amp;ldquo;New View&amp;rdquo; of safety to create better outcomes.</description>
    </item>
    
    <item>
      <title>The Amazon Kinesis Event</title>
      <link>https://rumproarious.com/2020/11/29/the-amazon-kinesis-event/</link>
      <pubDate>Sun, 29 Nov 2020 09:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2020/11/29/the-amazon-kinesis-event/</guid>
      <description>(A hypothetical dependency graph that led to a systemic failure in AWS us-east-1 from @0xdabbad00)
Like many, I was personally affected by the AWS outage last week. I was on-call, and was paged for a couple of reasons. While I was paged, I owe a lot to the infrastructure team I work with. They managed all of the issues I was paged for, and outside of a few spurious pages, I was mostly insulated from the issue.</description>
    </item>
    
    <item>
      <title>A Season for Reflection</title>
      <link>https://rumproarious.com/2020/11/24/a-season-for-reflection/</link>
      <pubDate>Tue, 24 Nov 2020 01:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2020/11/24/a-season-for-reflection/</guid>
      <description>Striving to be better, made me. Even though, it almost broke me. Over the last few years, I’ve tried to find a way to balance my daily duties and routines with my drive to be better and do better. Besides being a great time to be with family and friends, for me the time between Thanksgiving and New Years&#39; allows me to burn through my inbox, collect my thoughts, maybe write.</description>
    </item>
    
    <item>
      <title> The Goal</title>
      <link>https://rumproarious.com/notes/the-goal/</link>
      <pubDate>Sun, 22 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/the-goal/</guid>
      <description>Alex Rogo is a harried plant manager working ever more desperately to try improve performance. His factory is rapidly heading for disaster. So is his marriage. He has ninety days to save his plant - or it will be closed by corporate HQ, with hundreds of job losses. It takes a chance meeting with a professor from student days - Jonah - to help him break out of conventional ways of thinking to see what needs to be done. The story of Alex&amp;rsquo;s fight to save his plant is more than compulsive reading. It contains a serious message for all managers in industry and explains the ideas, which underline the Theory of Constraints (TOC), developed by Eli Goldratt.</description>
    </item>
    
    <item>
      <title>Site Reliability Engineering</title>
      <link>https://rumproarious.com/notes/site-reliability-engineering/</link>
      <pubDate>Sun, 22 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/site-reliability-engineering/</guid>
      <description>Members of the SRE team explain how their engagement with the entire software lifecycle has enabled Google to build, deploy, monitor, and maintain some of the largest software systems in the world.</description>
    </item>
    
    <item>
      <title>The Five Dysfunctions of a Team: A Leadership Fable</title>
      <link>https://rumproarious.com/notes/five-dysfunctions-team-leadership-fable/</link>
      <pubDate>Sat, 14 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/five-dysfunctions-team-leadership-fable/</guid>
      <description>Lencioni reveals the five dysfunctions which go to the very heart of why teams even the best ones-often struggle. He outlines a powerful model and actionable steps that can be used to overcome these common hurdles and build a cohesive, effective team.</description>
    </item>
    
    <item>
      <title>Daily Stand-Up Meetings Start Breaking the Rules </title>
      <link>https://rumproarious.com/notes/daily-stand-up-meetings-start-breaking-the-rules/</link>
      <pubDate>Sun, 01 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/daily-stand-up-meetings-start-breaking-the-rules/</guid>
      <description>A group of researches who&amp;rsquo;ve studied the daily standup for over a decade summarize their research and provide recommendations for how to make standups more valuable.</description>
    </item>
    
    <item>
      <title>Selecting Empirical Methods for Software Engineering Research</title>
      <link>https://rumproarious.com/notes/selecting-empirical-methods-for-software-engineering-research/</link>
      <pubDate>Fri, 30 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/selecting-empirical-methods-for-software-engineering-research/</guid>
      <description>Researchers studying software engineering often choose inappropriate methods. This chapter from, &amp;lsquo;Guide to Advanced Empirical Software Engineering&amp;rsquo;, is intended to help folks understand how to choose the right methods.</description>
    </item>
    
    <item>
      <title>Just The Gimlet Episodes of StartUp</title>
      <link>https://rumproarious.com/2020/10/29/just-the-gimlet-episodes-of-startup/</link>
      <pubDate>Thu, 29 Oct 2020 16:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2020/10/29/just-the-gimlet-episodes-of-startup/</guid>
      <description>When it comes to creating a start-up there&amp;rsquo;s prevailing wisdom. There&amp;rsquo;s even a school you can go to to learn it. But, for every company that does it &amp;ldquo;right&amp;rdquo;, there is one that does it their own way. One that is introspective and honest (ish). That other way is epitomized by Gimlet, the podcast company, at least if their podcast is any representation of how they work.
I’ve brought up the podcast a few times with friends and co-workers because it&amp;rsquo;s entertaining, and it instructive for folks who work in growing businesses.</description>
    </item>
    
    <item>
      <title>Experiences from conducting semi-structured interviews in empirical software engineering research</title>
      <link>https://rumproarious.com/notes/experiences-from-conducting-semi-structured-interviews-in-empirical-software-engineering-research/</link>
      <pubDate>Sun, 25 Oct 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/experiences-from-conducting-semi-structured-interviews-in-empirical-software-engineering-research/</guid>
      <description>Interviews provide a rich set of qualitative experiences to analyze, but they require a high level of effort to achieve high quality results. This paper provides recommendations based on available literature and the experience of the authors.</description>
    </item>
    
    <item>
      <title>The Field Guide to Understanding &#39;Human Error&#39;</title>
      <link>https://rumproarious.com/notes/the-field-guide-understand-human-error/</link>
      <pubDate>Mon, 27 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/the-field-guide-understand-human-error/</guid>
      <description>The Field Guide to Understanding ’Human Error’ will help you understand a new way of dealing with a perceived &amp;lsquo;human error&amp;rsquo; problem in your organization. It will help you trace how your organization juggles inherent trade-offs between safety and other pressures and expectations, suggesting that you are not the custodian of an already safe system.</description>
    </item>
    
    <item>
      <title>The Phoenix Project</title>
      <link>https://rumproarious.com/notes/the-phoenix-project/</link>
      <pubDate>Sat, 25 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/the-phoenix-project/</guid>
      <description>Bill is an IT manager at Parts Unlimited. It&amp;rsquo;s Tuesday morning and on his drive into the office, Bill gets a call from the CEO.The company&amp;rsquo;s new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill&amp;rsquo;s entire department will be outsourced.</description>
    </item>
    
    <item>
      <title>The Fifth Discipline</title>
      <link>https://rumproarious.com/notes/the-fifth-discipline/</link>
      <pubDate>Fri, 24 Jan 2020 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/notes/the-fifth-discipline/</guid>
      <description>In The Fifth Discipline, Senge describes how companies can rid themselves of the learning “disabilities” that threaten their productivity and success by adopting the strategies of learning organizations—ones in which new and expansive patterns of thinking are nurtured, collective aspiration is set free, and people are continually learning how to create results they truly desire.</description>
    </item>
    
    <item>
      <title>The Case of What To Call My Role</title>
      <link>https://rumproarious.com/2019/12/24/the-case-of-what-to-call-my-role/</link>
      <pubDate>Tue, 24 Dec 2019 22:16:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/24/the-case-of-what-to-call-my-role/</guid>
      <description>In my professional roles the word engineer is in the title somewhere. For instance I&amp;rsquo;m currently a Principal Engineer at Stitch Fix, but I&amp;rsquo;ve been a Software Engineer, Front-end Engineer and so fourth over the years. The word engineer isn&amp;rsquo;t really apt for what I do though. In the last year I found a new promising word: Symmathecist.
I learned about it from this post &amp;ldquo;The Origins of Opera and the Future of Programming&amp;rdquo; by Jessica Kerr.</description>
    </item>
    
    <item>
      <title>Give Thanks for Simple Tools</title>
      <link>https://rumproarious.com/2019/12/23/give-thanks-for-simple-tools/</link>
      <pubDate>Mon, 23 Dec 2019 21:10:24 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/23/give-thanks-for-simple-tools/</guid>
      <description>The infrastructure of my productivity is a set of tools that revolve around plain text files. Try as I might it doesn&amp;rsquo;t work any other way.
I&amp;rsquo;ve tried tools with more &amp;ldquo;stuff&amp;rdquo; in them. Often when I try and import my modest1 set of files they grind to a halt. So, I go back to my tried and true tools.
I&amp;rsquo;m thankful they exist and continue to work. It&amp;rsquo;s a patchwork of folks and tools that keep this stuff running.</description>
    </item>
    
    <item>
      <title>A Kind Legacy For Go</title>
      <link>https://rumproarious.com/2019/12/22/a-kind-legacy-for-go/</link>
      <pubDate>Sun, 22 Dec 2019 19:27:54 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/22/a-kind-legacy-for-go/</guid>
      <description>I use Go off and on. I&amp;rsquo;ve recently had the opportunity to use it again. I feel comfortable now with a handful of languages including Go. More importantly I&amp;rsquo;ve fought fires in production, developed new services, and tried to refactor balls of mud in a handful of languages. Out of them all no language is more kind to it&amp;rsquo;s user then Go.
That fact is on display in this talk Go at Google: Language Design in the Service of Software Engineering.</description>
    </item>
    
    <item>
      <title>In The Beginning Was the Command Line</title>
      <link>https://rumproarious.com/2019/12/21/in-the-beginning-was-the-command-line/</link>
      <pubDate>Sat, 21 Dec 2019 22:19:04 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/21/in-the-beginning-was-the-command-line/</guid>
      <description>There is a book. Called &amp;ldquo;In The Beginning Was the Command Line&amp;rdquo; written by Neal Stephenson. 1 You might know him from such books as Snowcrash or Cryptonomicon, but he&amp;rsquo;s written some non-fiction as well.
It&amp;rsquo;s hard to describe but it&amp;rsquo;s about the act of computing and the choices that surround folks who computed, especially in the late 90&amp;rsquo;s.
It&amp;rsquo;s compelling for many reasons, but I think I can point to at least one reason what I was so fascinated by the command line and by linux.</description>
    </item>
    
    <item>
      <title>What&#39;ll Programming Be Like</title>
      <link>https://rumproarious.com/2019/12/20/whatll-programming-be-like/</link>
      <pubDate>Fri, 20 Dec 2019 15:11:27 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/20/whatll-programming-be-like/</guid>
      <description>I think about this sometimes. Like, people used to punch holes in cards to program. That&amp;rsquo;s insane to me, but I can only imagine what it will look like in the future.
I think the biggest questions is like, will we even write code? Or, will we train, direct, or work with some &amp;hellip; thing.
Here&amp;rsquo;s an interesting post that talks about near to far future: &amp;ldquo;Programming: 50, 100 years from now&amp;rdquo;.</description>
    </item>
    
    <item>
      <title>Big Software Projects Are Failing</title>
      <link>https://rumproarious.com/2019/12/19/big-software-projects-are-failing/</link>
      <pubDate>Thu, 19 Dec 2019 08:28:13 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/19/big-software-projects-are-failing/</guid>
      <description>I have worked on projects that missed the deadline by years. It&amp;rsquo;s soul-crushing.
Whats worse is that it sounds like it&amp;rsquo;s endemic. Big projects are failing all over the place.
 Most IT experts agree that such failures occur far more often than they should. What’s more, the failures are universally unprejudiced: they happen in every country; to large companies and small; in commercial, nonprofit, and governmental organizations; and without regard to status or reputation.</description>
    </item>
    
    <item>
      <title>Conventional Wisdom</title>
      <link>https://rumproarious.com/2019/12/18/conventional-wisdom/</link>
      <pubDate>Wed, 18 Dec 2019 07:19:27 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/18/conventional-wisdom/</guid>
      <description>&lt;p&gt;Conventional Wisdom can be a bunch of BS. It can be a bludgeon to keep the troops in line. When it goes unexamined it can create group think that prevents healthy discourse.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Cryptographic Right Answers</title>
      <link>https://rumproarious.com/2019/12/17/cryptographic-right-answers/</link>
      <pubDate>Tue, 17 Dec 2019 20:02:48 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/17/cryptographic-right-answers/</guid>
      <description>I like most people am deathly afraid of crypto. There are just too many gotchas. Therefor I appreciate posts like these where smart folks break down the answers.
 We’re less interested in empowering developers and a lot more pessimistic about the prospects of getting this stuff right.
 https://latacora.singles/2018/04/03/cryptographic-right-answers.html</description>
    </item>
    
    <item>
      <title>Good API Design</title>
      <link>https://rumproarious.com/2019/12/16/good-api-design/</link>
      <pubDate>Mon, 16 Dec 2019 08:18:29 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/16/good-api-design/</guid>
      <description>It&amp;rsquo;s easy to see Kubernetes as &amp;ldquo;a way to run containerized workloads&amp;rdquo;. If you look at the comparisons that&amp;rsquo;s what they all do: ECS, Docker, and Mesos, etc. But, I don&amp;rsquo;t think that&amp;rsquo;s the vision for Kubernetes.
Here are a few tweets from Kelsey Hightower:
 The future where Kubernetes clusters disappear and we just leverage Kubernetes style APIs to deploy workloads is fast approaching. 1
  The cloud made the hypervisor disappear.</description>
    </item>
    
    <item>
      <title>Performance Matters</title>
      <link>https://rumproarious.com/2019/12/15/performance-matters/</link>
      <pubDate>Sun, 15 Dec 2019 12:41:40 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/15/performance-matters/</guid>
      <description>I&amp;rsquo;m torn between two axes. The first is being user-oriented. Thinking about the problems from their perspective and ensuring you are always working on something that improves value. The second is that good software is often fast software.
While it&amp;rsquo;s hard to make a case that keeping a service at a p99 of 500ms will increase the value to your users, I&amp;rsquo;ve found that trying to make it is important. The reality of the situation is always that it depends.</description>
    </item>
    
    <item>
      <title>Devops</title>
      <link>https://rumproarious.com/2019/12/14/devops/</link>
      <pubDate>Sat, 14 Dec 2019 21:45:42 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/14/devops/</guid>
      <description>DevOps, at least as I understand it, is about delivering value.
It sounds simple, but delivering that value happens via a pipeline. The stages of that pipeline often represent whole groupes of people. Ofthen those groups can have competing priorities. Thus increasing friction in the pipeline and slowing down the deliver of value.
That&amp;rsquo;s where DevOps comes to the rescue. By working with everyone in the pipeline and building a shared vision of how to deliver value, you can get everyone to optimize for the shared global goal of value delivery.</description>
    </item>
    
    <item>
      <title>Easy Simple Complicated Complex</title>
      <link>https://rumproarious.com/2019/12/13/easy-simple-complicated-complex/</link>
      <pubDate>Fri, 13 Dec 2019 18:54:39 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/13/easy-simple-complicated-complex/</guid>
      <description>The biggest irony in dev work is that we all want to build easy to use systems, but that&amp;rsquo;s hard to impossible to do.
Easy is hard.
Rich Hickey in his talk &amp;ldquo;Simple Made Easy&amp;rdquo; walks us through this irony and why its so important that we continue to try and build easy to use systems. 1
  Here is a transcript of the talk as well. &amp;#x21a9;&amp;#xfe0e;
   </description>
    </item>
    
    <item>
      <title>Anything From Julia Evans</title>
      <link>https://rumproarious.com/2019/12/12/anything-from-julia-evans/</link>
      <pubDate>Thu, 12 Dec 2019 08:09:01 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/12/anything-from-julia-evans/</guid>
      <description>It&amp;rsquo;s not often that anyone can take up basic linux literacy and make it interesting, but Julia Evans1 does it with style. Here is her zine on pipes2:
She doesn&amp;rsquo;t just illuminate linux, she will often bring that same clarity to more advanced topics such as service discovery. Here is a zine from a blog post 3 she wrote on Stripes engineering blog.
So, checkout the zines, or one of her many posts on kubernetes or networking and learn something.</description>
    </item>
    
    <item>
      <title>Helpful Numbers for Designing Technical Systems</title>
      <link>https://rumproarious.com/2019/12/11/helpful-numbers-for-designing-technical-systems/</link>
      <pubDate>Wed, 11 Dec 2019 07:56:26 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/11/helpful-numbers-for-designing-technical-systems/</guid>
      <description>When I design a new service, I want it to be efficient. Mostly, for any humans involved, but also for the technical components. Why make two HTTP calls when you can make 1. When thinking about tradeoffs it can be helpful to consider how long common operations take.
Not surprisingly, lists have been made of these common operations. As far as I can tell starting with Peter Norvig, and then re-popularised by Jeff Dean.</description>
    </item>
    
    <item>
      <title>A Taxonomy of Ignorance</title>
      <link>https://rumproarious.com/2019/12/10/a-taxonomy-of-ignorance/</link>
      <pubDate>Tue, 10 Dec 2019 08:00:01 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/10/a-taxonomy-of-ignorance/</guid>
      <description>Given I don&amp;rsquo;t know what I don&amp;rsquo;t know, but I want to find out. This taxonomy of ignorance and interesting thought experiment.
The Five Orders of Ignorance 1
Lack of Ignorance. Lack of Knowledge. Lack of Awareness Lack of Process. Meta Ignorance    http://losangeles.acm.org/Archives/laacm0512-Article%2002%20The%205%20Orders%20of%20Ignorance%20OCT%202000.pdf &amp;#x21a9;&amp;#xfe0e;
   </description>
    </item>
    
    <item>
      <title>Finding Out What You Dont Know</title>
      <link>https://rumproarious.com/2019/12/09/finding-out-what-you-dont-know/</link>
      <pubDate>Mon, 09 Dec 2019 08:25:01 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/09/finding-out-what-you-dont-know/</guid>
      <description>We don&amp;rsquo;t know what we don&amp;rsquo;t know. Clearly. But, sometimes the keys to a project exist in the unknown. Yet many of our project planning and execution tools don&amp;rsquo;t take this into account.
 If you just do the same thing over and over again, you will probably get better at performing that sequence, but you won’t learn anything new.
 That&amp;rsquo;s a quote from &amp;ldquo;Introducing Deliberate Discovery&amp;rdquo; by Dan North 1.</description>
    </item>
    
    <item>
      <title>A good commit message</title>
      <link>https://rumproarious.com/2019/12/08/a-good-commit-message/</link>
      <pubDate>Sun, 08 Dec 2019 11:34:54 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/08/a-good-commit-message/</guid>
      <description>There will be commit messages. Many. Of. Them.
Your team will read them. Your boss will read them. Strangers will read them. You will read them.
Future self is skeptical of present self.
You owe it to everyone to try and write better commit messages.
I&amp;rsquo;m not suggesting that I always do, it&amp;rsquo;s a lofty goal, but here is some help:
  Separate subject from body with a blank line Limit the subject line to 50 characters Capitalize the subject line Do not end the subject line with a period Use the imperative mood in the subject lineWrap the body at 72 characters Use the body to explain what and why vs.</description>
    </item>
    
    <item>
      <title>Value Over Tests</title>
      <link>https://rumproarious.com/2019/12/07/value-over-tests/</link>
      <pubDate>Sat, 07 Dec 2019 17:34:54 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/07/value-over-tests/</guid>
      <description>I am a fan of tests, but my testing journey was long and fraught.
One of the hardest ideas for me to understand was where do you draw the line. How much is enough?
I tried many different ways to understand this, but it wasn&amp;rsquo;t until I read this quote from Kent Beck that a key idea crystalized.
 I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence 1</description>
    </item>
    
    <item>
      <title>The Three Ways</title>
      <link>https://rumproarious.com/2019/12/06/the-three-ways/</link>
      <pubDate>Fri, 06 Dec 2019 07:43:58 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/06/the-three-ways/</guid>
      <description>During the course of my work I find my self rubberbanding between two extremes - universal truth and exacting, excruciating detail at a specific moment in time. Those many not seem like they are on the same continuum, but that&amp;rsquo;s where todays suggesting reading comes into play: The Three Ways by Gene Kim 1.
I&amp;rsquo;m a sucker for bit of wisdom that is seemingly inscrutable, but reveals it self to be universal.</description>
    </item>
    
    <item>
      <title>Platforms Are All Around Us</title>
      <link>https://rumproarious.com/2019/12/05/platforms-are-all-around-us/</link>
      <pubDate>Thu, 05 Dec 2019 08:44:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/05/platforms-are-all-around-us/</guid>
      <description>But, how do they work? 1
Platforms are about leverage. When done well they increase value superlinear rate compared to the amount of resources available. They are also hard to define, hard to see, and hard to build.
Today, I&amp;rsquo;ve got a one two punch. First an article from Frank Chimero, &amp;ldquo;Platforms as Tables, Tables as Platforms&amp;rdquo; 2. In it Chimero finds that Design and Jazz are both platforms, but also:</description>
    </item>
    
    <item>
      <title>A Systems Approach</title>
      <link>https://rumproarious.com/2019/12/04/a-systems-approach/</link>
      <pubDate>Wed, 04 Dec 2019 09:00:24 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/04/a-systems-approach/</guid>
      <description>Whatever it is that you do, if you have wondered about increasing productivity, improving outcomes or creating more long lasting value, you owe it to your self to learn a little about the study of systems.
Okay, starting with the most banal definition of a system:
 A system is a group of interacting or interrelated entities that form a unified whole.[1] A system is delineated by its spatial and temporal boundaries, surrounded and influenced by its environment, described by its structure and purpose and expressed in its functioning.</description>
    </item>
    
    <item>
      <title>A Pile of Links</title>
      <link>https://rumproarious.com/2019/12/03/a-pile-of-links/</link>
      <pubDate>Tue, 03 Dec 2019 14:20:24 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/03/a-pile-of-links/</guid>
      <description>There must be a large and storied body of literature when it comes to curation, but I am unfortunately not familiar. I might have a chance someday, but for now, what I do have is this article from Frank Chimero &amp;ldquo;Sorting A Mass&amp;rdquo; 1.
Up till this point, I had bookmarked anything and everything that came close to piquing my interest. But after this article, I remember bringing more of a critical eye to my reading.</description>
    </item>
    
    <item>
      <title>The Stream as a Guiding Metaphor</title>
      <link>https://rumproarious.com/2019/12/02/the-stream-as-a-guiding-metaphor/</link>
      <pubDate>Mon, 02 Dec 2019 14:20:24 -0700</pubDate>
      
      <guid>https://rumproarious.com/2019/12/02/the-stream-as-a-guiding-metaphor/</guid>
      <description>Being a child of the 80s I can recall a time before the internet permeated my entire reading experience. It was a happy accident for me and my career when I was able to access the internet on a daily bases.
Before the internet, Wired came once a month. When I had enough money I&amp;rsquo;d buy 2600 (it&amp;rsquo;s hard to convince parents to subscribe to a &amp;ldquo;hackers&amp;rdquo; quarterly). Between publications, I&amp;rsquo;d dwell on the information.</description>
    </item>
    
    <item>
      <title>How To Download The Internet by Accident</title>
      <link>https://rumproarious.com/2019/12/01/how-to-download-the-internet-by-accident/</link>
      <pubDate>Sun, 01 Dec 2019 23:00:00 -0600</pubDate>
      
      <guid>https://rumproarious.com/2019/12/01/how-to-download-the-internet-by-accident/</guid>
      <description>Gonna start out the month with a fun and simple one.
MP3 Blogs and wget by Jeffrey Veen.
When I read this, I had a VPS, that I could barely keep running. I blindly ran the command in this post.
The next morning I found that I had downloaded almost 30 gigabytes of MP3s.
It forced me to learning about things about linux, and wget.
This was important, because I got one of my first tech jobs because I knew about wget.</description>
    </item>
    
    <item>
      <title>500 articles to read!</title>
      <link>https://rumproarious.com/2019/12/01/500-articles-to-read/</link>
      <pubDate>Sun, 01 Dec 2019 12:00:00 -0600</pubDate>
      
      <guid>https://rumproarious.com/2019/12/01/500-articles-to-read/</guid>
      <description>500+ articles to read. That backlog took years to build. Years of, &amp;ldquo;Yea, I&amp;rsquo;ll totally read that&amp;rdquo;. Then not reading anything. While I was able to trash part of the backlog. (No, I don&amp;rsquo;t need to read &amp;ldquo;4 spaces are better then 2 when formatting code&amp;rdquo;). I still had a healthy backlog.
To not keep anyone in suspense, I read it 1. Reading it reminded me of my favorite articles from years past.</description>
    </item>
    
    <item>
      <title>Advice for a software dev who is not a librarian but now finds themselves writing software for libraries</title>
      <link>https://rumproarious.com/2018/08/03/advice-for-a-software-dev-who-is-not-a-librarian-but-now-finds-themselves-writing-software-for-libraries/</link>
      <pubDate>Fri, 03 Aug 2018 12:00:00 -0600</pubDate>
      
      <guid>https://rumproarious.com/2018/08/03/advice-for-a-software-dev-who-is-not-a-librarian-but-now-finds-themselves-writing-software-for-libraries/</guid>
      <description>&lt;p&gt;Well, around 3ish years ago I stared working for a company that sells software to libraries and I didn&amp;rsquo;t know a thing. I have learned a lot since then, but I am now embarking on a new journey and I would like to leave some advice to other software devs who might find themselves in similar situations.&lt;/p&gt;
&lt;p&gt;The best advice I can give is to find a community who can remind you of how important libraries are.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Use Short-Lived AWS IAM Credentials For Everything</title>
      <link>https://rumproarious.com/2018/05/28/use-short-lived-aws-iam-credentials-for-everything/</link>
      <pubDate>Mon, 28 May 2018 15:48:24 -0600</pubDate>
      
      <guid>https://rumproarious.com/2018/05/28/use-short-lived-aws-iam-credentials-for-everything/</guid>
      <description>&lt;p&gt;Managing IAM credentials is a burden. Besides juggling N separate credentials, I don&amp;rsquo;t want more secretes to manage. There must be a better way and I&amp;rsquo;m experimenting with some tools to find a better way.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>JSON Feed For Hugo</title>
      <link>https://rumproarious.com/the-stream/2017-05-17-json-feed-for-hugo/</link>
      <pubDate>Wed, 17 May 2017 10:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2017-05-17-json-feed-for-hugo/</guid>
      <description>&lt;p&gt;After learning about JSON Feed I took some time to implment a template for Hugo. This relies upon version 0.20 of Hugo which has support for many alternative formats. You can see find this in the &lt;a href=&#34;https://github.com/voidfiles/rumproarious.com/blob/master/layouts/index.json&#34;&gt;github repo for this site&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>JSONfeed</title>
      <link>https://rumproarious.com/the-stream/2017-05-17-jsonfeed/</link>
      <pubDate>Wed, 17 May 2017 10:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2017-05-17-jsonfeed/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://jsonfeed.org/version/1&#34;&gt;JSON Feed&lt;/a&gt; is a new format for syndication that was developed by &lt;a href=&#34;http://inessential.com/&#34;&gt;Brent Simmons&lt;/a&gt; and &lt;a href=&#34;http://manton.org/&#34;&gt;Manton Reece&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is a great idea. Read the &lt;a href=&#34;https://jsonfeed.org/2017/05/17/announcing_json_feed&#34;&gt;announcment&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Blogging as the Long View</title>
      <link>https://rumproarious.com/the-stream/2017-04-10-blogging-is-the-longview/</link>
      <pubDate>Mon, 10 Apr 2017 21:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2017-04-10-blogging-is-the-longview/</guid>
      <description>I share Gabe Weatherheads sentiment about blogging.
 Is this it then? Is this the last gasp of independent blogging as everyone moves to micro transactions of half considered thoughts? Will Tweets eat Wordpress? It sure seems like the indie blogs are thinned down to a small collection of ideas and opinions.
 What I miss about blogging is the slow contemplation of a bloggers ideology. Indie bloggers like Kottke and Daring Fireball have been publishing for over a decade on a daily basis.</description>
    </item>
    
    <item>
      <title>Short Notes on Instant Articles</title>
      <link>https://rumproarious.com/the-stream/2015-05-13-short-notes-on-instant-articles/</link>
      <pubDate>Wed, 13 May 2015 15:11:11 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2015-05-13-short-notes-on-instant-articles/</guid>
      <description>Instant articles are cool. They look nice, at least the NatGeo one does.
This is a much better reading experience then the average article, especially on mobile.
It&amp;rsquo;s a little weird that Facebook effectively owns the &amp;ldquo;TV&amp;rdquo; of mobile content.
That being said, Facebook just defined the &amp;ldquo;Instant Articles&amp;rdquo; market. If people in general like that experience other apps can capitalize on this new market. Some app could unbundle that experience from Facebook.</description>
    </item>
    
    <item>
      <title>Programs are meant to be read by humans, and only incidentally for computers to execute.</title>
      <link>https://rumproarious.com/2015/01/20/programs-are-meant-to-be-read-by-humans-and-only-incidentally-for-computers-to-execute./</link>
      <pubDate>Tue, 20 Jan 2015 21:00:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/2015/01/20/programs-are-meant-to-be-read-by-humans-and-only-incidentally-for-computers-to-execute./</guid>
      <description>PPK is on a tear. He&amp;rsquo;s having a conversation in public that I&amp;rsquo;ve been having for a few years. You really should read these three blog posts for context.
I appreciate the discussion and I hope that it continues, but the scope is sufficiently broad enough that I won&amp;rsquo;t be able to go through it all point by point. Instead I would like to provide a framework for the disscussion, thats why I titled this blog post with a quote from Donald Knuth</description>
    </item>
    
    <item>
      <title>Full stack is more then a checkbox for your startup</title>
      <link>https://rumproarious.com/2014/10/19/full-stack-is-more-then-a-checkbox-for-your-startup/</link>
      <pubDate>Sun, 19 Oct 2014 12:37:06 -0700</pubDate>
      
      <guid>https://rumproarious.com/2014/10/19/full-stack-is-more-then-a-checkbox-for-your-startup/</guid>
      <description>The words full stack will quickly be overburdened, but for now they represents an ideal. The basic premise laid out by Chris Dixon.
 The new approach is to build a complete, end-to-end product or service that bypasses existing companies.
 Awesome, we now have this new word, and it&amp;rsquo;s a word that is getting used a lot from fund-raising, to job listings, to internal memos. Like any new label how the hell do you know if a company is actually full stack?</description>
    </item>
    
    <item>
      <title>On To My Next Adventure</title>
      <link>https://rumproarious.com/2014/05/06/on-to-my-next-adventure/</link>
      <pubDate>Tue, 06 May 2014 22:56:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/2014/05/06/on-to-my-next-adventure/</guid>
      <description>Taken by a co-worker when App.net was still picplz. App.net is shutting It&amp;rsquo;s clearly the context for this post, but it&amp;rsquo;s not the point. I am leaving App.net to be the VP of Engineering at new company that should have a name shortly.
Durring my time at App.net I constantly operated at the edge of my abilities, and past them sometimes. It was alternatingly painful and exhilirating. I will be processing my stay here for quite awhile, but the main thing I learned from App.</description>
    </item>
    
    <item>
      <title>How Vox Media Creates News Products</title>
      <link>https://rumproarious.com/2014/02/07/how-vox-media-creates-news-products/</link>
      <pubDate>Fri, 07 Feb 2014 10:56:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2014/02/07/how-vox-media-creates-news-products/</guid>
      <description>Yesterday we got a look into how new news organization are working in a technical sense1. To my mind its one of the few detailed posts about how places like Vox Media are working to actually innovate. It was written by Pablo Mercado, Vox Media’s VP of Technology. He detailed a little bit about how they pull together all the talent needed for a project and how they coordinate that talent.</description>
    </item>
    
    <item>
      <title>Introducing Lark a RESTy interface for Redis</title>
      <link>https://rumproarious.com/2013/12/22/introducing-lark-a-resty-interface-for-redis/</link>
      <pubDate>Sun, 22 Dec 2013 10:21:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2013/12/22/introducing-lark-a-resty-interface-for-redis/</guid>
      <description>Lark is a python library that provides a generic method for transforming a HTTP request into a redis command. If you know what webdis is then you&amp;rsquo;ll roughly know what this is. It does a couple of things right now:
 It users REST as a guideline without getting to pedantic. It has built in support for per user key prefixs. It automatically JSON encodes redis values (where appropriate). It has lots of tests (and TravisCI all setup).</description>
    </item>
    
    <item>
      <title>Feedbin.me Goes Open Source</title>
      <link>https://rumproarious.com/the-stream/2013-09-02-feedbin-dot-me-goes-open-source/</link>
      <pubDate>Mon, 02 Sep 2013 14:10:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-09-02-feedbin-dot-me-goes-open-source/</guid>
      <description>Feedbin.me has released the code that runs the service as open source, checkout out the Github. It joins Newsblur as being the second large for profit RSS reader to release its code in such a manner. I&amp;rsquo;m not aware of any other commercial services that open source all of their code.
This seems like a strong move that only a independent developer can take when faced with competition from well funded competitors.</description>
    </item>
    
    <item>
      <title>Open Question: What&#39;s the impact of Reader&#39;s shutdown on traffic?</title>
      <link>https://rumproarious.com/the-stream/2013-06-27-open-question-whats-the-impact-of-readers-shutdown-on-traffic/</link>
      <pubDate>Thu, 27 Jun 2013 23:35:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-27-open-question-whats-the-impact-of-readers-shutdown-on-traffic/</guid>
      <description>Let&amp;rsquo;s say that there are only 1 million Google Reader users. In three days, that&amp;rsquo;s a million people who won&amp;rsquo;t be clicking on American Apparel ads. Which could directly effect the bottom line of websites that are entirely funded by ads, like blogs.
Is there anyway to know by how much though? What do you think the leading indicators might be?
I have enabled comments for this post so let me know if you have any answers.</description>
    </item>
    
    <item>
      <title>The Rumproarious eBook</title>
      <link>https://rumproarious.com/the-stream/2013-06-24-the-rumproarious-ebook/</link>
      <pubDate>Mon, 24 Jun 2013 06:59:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-24-the-rumproarious-ebook/</guid>
      <description>I have been threatening to do this for a while, and now I have. I created a mini-ebook about the future of feed readers. I used many of the blog posts that I wrote over the last few weeks as the raw material for it, but I tried to craft a solid narrative for the ebook. Check it out:
Feeding Our Reading Habits
Also available in PDF and for the Kindle.</description>
    </item>
    
    <item>
      <title>Network Thinking In TV</title>
      <link>https://rumproarious.com/the-stream/2013-06-17-network-thinking-in-tv/</link>
      <pubDate>Mon, 17 Jun 2013 09:21:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-17-network-thinking-in-tv/</guid>
      <description>The Sopranos is a story about a man that happens to be set in the world of organized crime. The Wire is a story about a setting, Baltimore, that happens to include a story about some people. They just so happen to be there so we learn a little about their lives, but the the real story is that of the city. This distinction is what makes The Sopranos one of the biggest shows of the last 20 years, and it makes The Wire a show with a small but vocal crowd who think it may be the best TV show ever made.</description>
    </item>
    
    <item>
      <title>What Would a Facebook Reader Mean?</title>
      <link>https://rumproarious.com/the-stream/2013-06-16-what-would-a-facebook-reader-mean/</link>
      <pubDate>Sun, 16 Jun 2013 10:06:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-16-what-would-a-facebook-reader-mean/</guid>
      <description>Last week multiple signs started to appear that point to the fact that Facebook might be prepping a news reader. While there has been discussion of the possibility few, if any, have tried to figure out what it would mean in general. Admittedly, there are few details, but it&amp;rsquo;s not that hard to extrapolate from past actions. You need to look at this from a couple different perspectives though. Why does this make sense for Facebook, Publishers, or the consumer?</description>
    </item>
    
    <item>
      <title>Tastestalking</title>
      <link>https://rumproarious.com/the-stream/2013-06-14-tastestalking/</link>
      <pubDate>Fri, 14 Jun 2013 09:28:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-14-tastestalking/</guid>
      <description>Discovery is a pretty broad activity for one tool, but the idea is simple. Some cycles are inward, convergent paths, meaning you end up getting deeper and narrower into a topic over time. For certain topics, this isn&amp;rsquo;t always bad. Often you would go deeper on subjects that matter to you. In general though, you want to slowly move outwards. It&amp;rsquo;s a form of diversification. You don&amp;rsquo;t want your sources to stagnate, or you could end up missing out on a larger context.</description>
    </item>
    
    <item>
      <title>Juxtapositon In Feed Readers</title>
      <link>https://rumproarious.com/the-stream/2013-06-06-juxtapositon-in-feed-readers/</link>
      <pubDate>Thu, 06 Jun 2013 08:57:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-06-juxtapositon-in-feed-readers/</guid>
      <description>Juxtaposition is a technique that gets used quite often without anyone noticing. It gets used and misused daily by the media to great effect. To understand the power of juxtaposition I think it helps to talk about the Kuleshov Effect:
 &amp;ldquo;Kuleshov edited together a short film in which a shot of the expressionless face of Tsarist matinee idol Ivan Mosjoukine was alternated with various other shots (a plate of soup, a girl in a coffin, a woman on a divan).</description>
    </item>
    
    <item>
      <title>Reading Efficiently</title>
      <link>https://rumproarious.com/the-stream/2013-06-05-reading-efficiently/</link>
      <pubDate>Wed, 05 Jun 2013 07:23:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-06-05-reading-efficiently/</guid>
      <description>Now that we covered context, I think it&amp;rsquo;s important to talk about motivation. It frames the entire issue. What motivates you to read? The answer to this question puts you on entirely different paths.
For example, if you are motivated to read to pass time, thats fine, but much of what I am talking about is useless to you. Yes, you are reading, but you aren&amp;rsquo;t reading for comprehension, nor are you reading because you want to move on to something else.</description>
    </item>
    
    <item>
      <title>More On Sync and RSS</title>
      <link>https://rumproarious.com/the-stream/2013-05-23-more-on-sync-and-rss/</link>
      <pubDate>Thu, 23 May 2013 19:33:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-23-more-on-sync-and-rss/</guid>
      <description>Sync is key for feed readers got picked up by Dave Winer on Twitter here is what he had to say:
 &amp;ldquo;Sync Is Key For Feed Readers (If so, then make web apps, and you&amp;rsquo;re done). http://4fj.r2.ly/&amp;quot; — @davewiner
 And then Peter Rojas responded:
 &amp;ldquo;@davewiner I need an offline mode for my RSS reader since I often read on the subway, so mobile app is important to me.</description>
    </item>
    
    <item>
      <title>Two Quotes About Google Reader</title>
      <link>https://rumproarious.com/the-stream/2013-05-23-two-quotes-about-google-reader/</link>
      <pubDate>Thu, 23 May 2013 07:31:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-23-two-quotes-about-google-reader/</guid>
      <description>I understand that I am innately drawn to people talking about RSS readers. I shouldn&amp;rsquo;t be surprised when I find a good quote about Google Reader any day, but these are two good quotes.
The first come from a tubmlr blog, I thought it appropriate, called Britticisms. She seems to be an RSS reader after my own heart. In response to the question, could you list some of the blogs you subscribe to via google reader, she started with:</description>
    </item>
    
    <item>
      <title>Sync Is Key For Feed Readers</title>
      <link>https://rumproarious.com/the-stream/2013-05-22-sync-is-key-for-feed-readers/</link>
      <pubDate>Wed, 22 May 2013 08:56:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-22-sync-is-key-for-feed-readers/</guid>
      <description>Sync could simply be explained as the process of making everything the same in multiple places. In terms of an RSS reader, I think it&amp;rsquo;s the technical cornerstone of the tool. Information doesn&amp;rsquo;t care where you are or what device you are on. It is created at breakneck speeds, and you should be able to manage it from anywhere on any device. While this is a clear value proposition, not everyone would agree, but there are other reasons why sync is important.</description>
    </item>
    
    <item>
      <title>Super Human Reading Powers</title>
      <link>https://rumproarious.com/the-stream/2013-05-17-super-human-reading-powers/</link>
      <pubDate>Fri, 17 May 2013 14:53:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-17-super-human-reading-powers/</guid>
      <description>Growing up I was told that I had a learning disability. Some form of dyslexia, I think, I don&amp;rsquo;t remember exactly what it was. I don&amp;rsquo;t really think about it that much now days because I don&amp;rsquo;t think its holding me back any. But, I have started to think that the reason I enjoy using feed readers so much is because of whatever learning disability I had, or have is. Also, how I use a feed reader as a tool to stay afloat could probably be used by others to achieve spectacular results.</description>
    </item>
    
    <item>
      <title>The Pogue Piece on Reader</title>
      <link>https://rumproarious.com/the-stream/2013-05-11-the-pogue-piece-on-reader/</link>
      <pubDate>Sat, 11 May 2013 23:53:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-11-the-pogue-piece-on-reader/</guid>
      <description>David Pogue wrote a piece yesterday about Google reader. Explaining the Reader situation in plain english. In it I think he exemplifies the current market while completely missing the larger picture.
What he gets right is the broad picture, i.e., What a feed reader is, and what has happened. He had a good solid broad definition. Makes it sound simple, which could be one reason no one wants to pay, but sufficient.</description>
    </item>
    
    <item>
      <title>Context Is King</title>
      <link>https://rumproarious.com/the-stream/2013-05-10-context-is-king/</link>
      <pubDate>Fri, 10 May 2013 09:00:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-10-context-is-king/</guid>
      <description>Websites place content within a context of their choosing. They make certain decisions for the user that range from simple to subtle. The fact that using a feed reader gives more control to the user over context is the best and most basic reason to use a feed reader. While the case to be made is not that every website out there has nefarious reasons for its context. We simply don&amp;rsquo;t always need to let the website make those decisions.</description>
    </item>
    
    <item>
      <title>We Are In The RSS Cambrian Explosion</title>
      <link>https://rumproarious.com/the-stream/2013-05-09-we-are-in-the-rss-cambrian-explosion/</link>
      <pubDate>Thu, 09 May 2013 10:01:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-05-09-we-are-in-the-rss-cambrian-explosion/</guid>
      <description>I don&amp;rsquo;t think the revival of readers will happen because one person made it happen. This was hard for me to fathom, because I wrote an article about how there would only be room for one player, but we are in the middle of a Cambrian explosion. The people making the new readers are mostly going it alone, so far. But, on more than one occasion I thought to myself, what if they were all on the same team?</description>
    </item>
    
    <item>
      <title>Feeds on an Internet</title>
      <link>https://rumproarious.com/the-stream/2013-04-29-feeds-on-an-internet/</link>
      <pubDate>Mon, 29 Apr 2013 09:43:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-04-29-feeds-on-an-internet/</guid>
      <description>I recently wrote about how large the feed reading ecosystem could be. Specifically how large the pad market could be. In that post I wrote about how people say a Google Reader shut down is a good thing because there will be rapid innovation in the space, but few talked about what that innovation could be. I agree, but think that innovation is a matter of iteration and revision and not always a complete break from what came before.</description>
    </item>
    
    <item>
      <title>How Large Will the Paid Feed Reader Market Be?</title>
      <link>https://rumproarious.com/the-stream/how-large-will-the-payed-feed-reader-market-be/</link>
      <pubDate>Thu, 18 Apr 2013 06:34:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/how-large-will-the-payed-feed-reader-market-be/</guid>
      <description>Clearly, the market for feed readers is in transition. With only the mention of Google Reader closing, we&amp;rsquo;ve seen large user movement. Feedly alone gained more than 3 million new users recently1. In the midst of all this change, more than a few people have said, &amp;ldquo;This is going to mean good things.&amp;rdquo; But what does that really mean?
Any &amp;ldquo;good thing&amp;rdquo; will have to be driven by the makers of feed readers, so I am going to start there.</description>
    </item>
    
    <item>
      <title>How Big is the RSS Market?</title>
      <link>https://rumproarious.com/the-stream/2013-04-11-how-big-is-the-rss-market/</link>
      <pubDate>Thu, 11 Apr 2013 21:01:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-04-11-how-big-is-the-rss-market/</guid>
      <description>I am currently researching this question, but if you know the answer, or even if you think you know the answer. Let me know.
http://alpha.app.net/voidfiles
http://twitter.com/voidfiles
PS: Right now, I think the whole market is around 100 million active monthly users.</description>
    </item>
    
    <item>
      <title>Brent Simmons Creates RSS Sync Mailing List</title>
      <link>https://rumproarious.com/the-stream/2013-03-17-brent-simmons-creates-rss-sync-mailing-list/</link>
      <pubDate>Sun, 17 Mar 2013 17:06:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-03-17-brent-simmons-creates-rss-sync-mailing-list/</guid>
      <description>Brent Simmons created a mailing list to talk about any new potential RSS syncing services.
 &amp;ldquo;I created a new mailing list for people who want to talk about the technical side of RSS syncing.
  Ideally there would be a single standard for RSS syncing, and clients could choose among systems. But I don’t insist on that — at least not yet. I think it’s ambitious enough just to get some working sync systems up and running.</description>
    </item>
    
    <item>
      <title>Waiting for Chris Wetherell</title>
      <link>https://rumproarious.com/the-stream/2013-03-16-waiting-for-chris-wetherell/</link>
      <pubDate>Sat, 16 Mar 2013 11:21:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2013-03-16-waiting-for-chris-wetherell/</guid>
      <description>Whenever there are big changes to Google Reader Chris Wetherell usually has something insightful to say. In the latest cycle he has done an interview with Om Malik, but he hasn&amp;rsquo;t written a post yet.
It&amp;rsquo;s not surprising given that he is the creator of Google Reader that he might have something to say. I have always enjoyed his posts in the past.
Given that we are about to see a bunch of new feed readers, the reason I am waiting is that his old posts about the birth of Google Reader are always incredibly insightful, even upon re-reading.</description>
    </item>
    
    <item>
      <title>Edward Tufte quote of the day</title>
      <link>https://rumproarious.com/2013/02/13/edward-tufte-quote-of-the-day/</link>
      <pubDate>Wed, 13 Feb 2013 09:17:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2013/02/13/edward-tufte-quote-of-the-day/</guid>
      <description>At App.net we collect a metric ton of stats. When I build anything I try to collect some stats. We all must do that. Why not right, stats are fun. The hard part comes when you need to formulate those stats into information. It&amp;rsquo;s not easy. Slowly, I learned what to watch, what was important. It&amp;rsquo;s hard earned intuition, but intuition is no substitute for a well structured argument. Which is why I loved this short piece by Edward Tufte.</description>
    </item>
    
    <item>
      <title>Be Guilt Free</title>
      <link>https://rumproarious.com/2013/01/29/be-guilt-free/</link>
      <pubDate>Tue, 29 Jan 2013 23:57:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2013/01/29/be-guilt-free/</guid>
      <description>Do not feel guilty for not reading the tidal wave of information that piles up on your door everyday. Just don&amp;rsquo;t. Half the battle in this modern era of information overload is learning how to not care about all the information. We call them feeds, or streams for a reason — they never end. Your only goal should be to build a better net. It&amp;rsquo;s not to worry about unread counts or friend requests, or virtual corn fields.</description>
    </item>
    
    <item>
      <title>Going Long On Markdown</title>
      <link>https://rumproarious.com/2012/10/29/going-long-on-markdown/</link>
      <pubDate>Mon, 29 Oct 2012 00:04:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2012/10/29/going-long-on-markdown/</guid>
      <description>Markdown like RSS is one of those things that has fundamentally changed my relationship with the way that I work. Unlike RSS though I think Markdown is primed for mass adoption. Its ready because it fills a classic need for a lightweight-journaling-note-taking-style syntax, it has wide spread adoption ie network effects, and we are already seeing movements to standardize and proselytize Markdown to a larger community.
The other day on App.</description>
    </item>
    
    <item>
      <title>Optimistic Server Interactions</title>
      <link>https://rumproarious.com/2012/08/30/optimistic-server-interactions/</link>
      <pubDate>Thu, 30 Aug 2012 20:58:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2012/08/30/optimistic-server-interactions/</guid>
      <description>At PicPlz we built a hybrid mobile app. We had a native container written for iOS and Android that hosted a web version of our code. PicPlz was the first time I had worked on a fully mobile website. My operating paradigm was that I was building a website for a small screen.
One day, our iOS developer asked me why our follow button didn’t just react when a user touched it.</description>
    </item>
    
    <item>
      <title>Standards spelunking, App.net, and a change of heart</title>
      <link>https://rumproarious.com/2012/07/19/standards-spelunking-app.net-and-a-change-of-heart/</link>
      <pubDate>Thu, 19 Jul 2012 21:56:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2012/07/19/standards-spelunking-app.net-and-a-change-of-heart/</guid>
      <description>I have been standards spelunking recently. ATOM, OStatus, JSON XMPP (hint: that one is a joke), and Activity Steams. All this exploration led me to a conclusion - standards are not the panacea I once thought. There is a lot to like about standards; hard work, thourough thought, and sometimes a success, but we can&amp;rsquo;t blindly follow the standards off a cliff.
I have been presented with an amazing opportunity to spend some time looking through all this prior art.</description>
    </item>
    
    <item>
      <title>The New Aesthetic of Feeds</title>
      <link>https://rumproarious.com/2012/06/18/the-new-aesthetic-of-feeds/</link>
      <pubDate>Mon, 18 Jun 2012 17:17:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/2012/06/18/the-new-aesthetic-of-feeds/</guid>
      <description>The new aesthetic sat in my overflow folder for a while. I probably subscribed to it while working though a best new blog list. It was always curios. The pictures were nice, but like many blogs you figure it out by reading it. When I read the Atlantic piece It finally clicked.
If you don&amp;rsquo;t know, The new aesthetic is an art movement. It&amp;rsquo;s tag line would be an exploration of how our digital products effect us.</description>
    </item>
    
    <item>
      <title>RSS and New Media - comments so far</title>
      <link>https://rumproarious.com/the-stream/2012-02-03-rss-and-new-media-comments-so-far/</link>
      <pubDate>Fri, 03 Feb 2012 21:20:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2012-02-03-rss-and-new-media-comments-so-far/</guid>
      <description>I have had a fun few days processing the input I have recived about RSS needs better PR. I encourage everyone to keep the feedback coming. I would also like to announce that I am going to open this blog to other authors. If you would like to write a post just let me know. I am sure we can figure out something.
Some great comments so far.
 So what is this new medium?</description>
    </item>
    
    <item>
      <title>A twitter conversation with Dave Winer</title>
      <link>https://rumproarious.com/the-stream/2012-02-02-a-twitter-conversation-with-dave-winer/</link>
      <pubDate>Thu, 02 Feb 2012 21:20:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2012-02-02-a-twitter-conversation-with-dave-winer/</guid>
      <description>I had a short twitter conversation with Dave Winer yesterday about my blog post, RSS needs better PR.
RSS needs better PR sia.tw/wzJZVk
&amp;mdash; alex kessinger (@voidfiles) February 1, 2012If what RSS needs is better PR then give it better PR.:-).blork.ly/zLuoQz
&amp;mdash; Dave Winer ☮ (@davewiner) February 1, 2012@davewiner I&#39;m tryin man.
&amp;mdash; alex kessinger (@voidfiles) February 2, 2012@voidfiles -- really? you&#39;re all doom and gloom -- so negative. honestly, that&#39;s not really good PR.</description>
    </item>
    
    <item>
      <title>RSS needs better PR</title>
      <link>https://rumproarious.com/the-stream/2012-01-31-rss-needs-a-new-pr-team/</link>
      <pubDate>Tue, 31 Jan 2012 21:20:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2012-01-31-rss-needs-a-new-pr-team/</guid>
      <description>RSS is in a bad state and it&amp;#8217;s possibly in danger. The rate of adoption seems to be slowing down. There are blogs, but new forms of information are being created, and they aren&amp;#8217;t using RSS. Even the people who love it are resigned to its demise. It&amp;#8217;s really hard to even make a business case for why your service should have RSS. Best argument we have right now is that its a greater good argument.</description>
    </item>
    
    <item>
      <title>Google Reader Has Transitioned</title>
      <link>https://rumproarious.com/the-stream/2011-11-01-google-reader-has-transitioned/</link>
      <pubDate>Tue, 01 Nov 2011 21:20:22 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/2011-11-01-google-reader-has-transitioned/</guid>
      <description>So, it happened. Google Reader has forever changed. I am the one that always makes fun of normies when they complain about Facebook changing. I am sure that I can learn to use it even now. So, while I am totally butt hurt about this whole process. I think there are two standout problems that could be fixed quickly.
  The design of the story area is sad. I can&amp;#8217;t tell where it begins, and ends.</description>
    </item>
    
    <item>
      <title>Reader Roundup Iranians, R$$, and More Funny Please.</title>
      <link>https://rumproarious.com/the-stream/google-reader-even-more-roundup/</link>
      <pubDate>Tue, 25 Oct 2011 18:51:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/google-reader-even-more-roundup/</guid>
      <description>There have been some bigger names weighing in on the coming Reader changes. What I am liking is that client authors are starting ask some serious questions about what this means for google reader syncing.
Today I saw Marco, and Gruber posting about Reader. They both chose to reference an article written by Brent Simmons.
Marco said:
 &amp;ldquo;The bad news is that there really isn’t an alternative RSS sync platform that I know of.</description>
    </item>
    
    <item>
      <title>With google reader changing is there a competitor looming?</title>
      <link>https://rumproarious.com/the-stream/google-reader-changing-competitor-looming/</link>
      <pubDate>Thu, 20 Oct 2011 18:51:56 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/google-reader-changing-competitor-looming/</guid>
      <description>Google Reader is changing, and that leaves a door open for a competitor. Google Reader is among my most used tools. It&amp;rsquo;s up there with the browser, text editor, and command line. I am pretty sure people have snickered at my interest in RSS more then once, and even then it&amp;rsquo;s only when I am in the company of people who know what the hell RSS is, an every shrinking pool of people.</description>
    </item>
    
    <item>
      <title>My first attempt at figuring out why The Awl is so good.</title>
      <link>https://rumproarious.com/the-stream/my-first-attempt-at-figuring-out-why-the-awl-is-so-good/</link>
      <pubDate>Mon, 27 Jun 2011 17:10:39 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/my-first-attempt-at-figuring-out-why-the-awl-is-so-good/</guid>
      <description>I am going to leave the breakdown of weighty subjects to other people, and hopefully I am biting off a small chunk of this pie, but I want to try my hand at figuring out why something is so good. I am going to start with blogs as a whole. I have become entranced by blogs in the last few years, they have seriously started to become important voices in their own right.</description>
    </item>
    
    <item>
      <title>A quickie about how I use rss</title>
      <link>https://rumproarious.com/the-stream/a-quickie-about-how-i-use-rss/</link>
      <pubDate>Mon, 16 May 2011 06:09:59 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/a-quickie-about-how-i-use-rss/</guid>
      <description>I saw Alexis Madrigal talking about using RSS on twitter today. He mentioned that he felt twitter was better at surfacing things that he wanted to write about then a RSS reader. I know nothing about how he uses a reader, or what he has in it, but I wondered how he was using his reader.
In my opinion, if you setup your reader correctly, it will always be better then twitter.</description>
    </item>
    
    <item>
      <title>My #jqcon talk </title>
      <link>https://rumproarious.com/2011/04/17/my-jqcon-talk/</link>
      <pubDate>Sun, 17 Apr 2011 18:15:54 -0700</pubDate>
      
      <guid>https://rumproarious.com/2011/04/17/my-jqcon-talk/</guid>
      <description>I gave a talk at the jQuery conference on sunday. I wanted to create one page were all the information about the talk could live. This is that page. Sources:
 Phonegap Backbone.js HTML5 rocks offline gMail Mobile application cache Six Revisions - web development blog Building iPhone Apps with HTML, CSS, and JavaScript book Lawnchair jquery-offline  Details:
 outline  gist of the talk   Slides - full slides with speaker notes  </description>
    </item>
    
    <item>
      <title>Reading Code</title>
      <link>https://rumproarious.com/2011/03/30/reading-code/</link>
      <pubDate>Wed, 30 Mar 2011 05:48:12 -0700</pubDate>
      
      <guid>https://rumproarious.com/2011/03/30/reading-code/</guid>
      <description>I recently spent some time getting to know backbone.js. I wanted to apply it to a mobile app I have been working on. While the code is great, I stumbled on an idea while using it. When I fist start using a framework of any kind, django for example, I almost always use there getting started tutorial.
You copy, and paste the code from this tutorial, and then poke and prod it until you get some kind of understand of the code.</description>
    </item>
    
    <item>
      <title>RSS, I can&#39;t quit you. </title>
      <link>https://rumproarious.com/the-stream/rss-i-cant-quit-you/</link>
      <pubDate>Tue, 29 Mar 2011 05:42:03 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/rss-i-cant-quit-you/</guid>
      <description>On occasion my blog posts receive outside attention, like when a piece get&amp;rsquo;s featured on a more popular website. For instance I was quoted in an article over at the register last week, and that catapulted my stats for a day. Regardless of what drives traffic to my blog, most readers of my blog seem interested in RSS. That is fine with me, because I like talking about the finer points of RSS just like everyone else.</description>
    </item>
    
    <item>
      <title>I have to say it, RSS is not dead.</title>
      <link>https://rumproarious.com/the-stream/something-i-wanted-to-say-about-rss-for-a-long-time/</link>
      <pubDate>Mon, 14 Mar 2011 23:51:30 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/something-i-wanted-to-say-about-rss-for-a-long-time/</guid>
      <description>When I read about the death of RSS, I laugh, but I think the point is we need a new platform to consume RSS. It needs to cater to curators, and hubs of influential people.
To some degree Facebook has become a kind of RSS reader, but the king of RSS readers is Google Reader, and we need a new version. It&amp;rsquo;s hard to think of a way to make Google Reader better.</description>
    </item>
    
    <item>
      <title>Goodbye PHP</title>
      <link>https://rumproarious.com/2011/02/09/goodbye-php/</link>
      <pubDate>Wed, 09 Feb 2011 23:42:16 -0700</pubDate>
      
      <guid>https://rumproarious.com/2011/02/09/goodbye-php/</guid>
      <description>Last night it occurred to me, I might never use PHP in a serious manner ever again. It’s bittersweet. No one is a bigger advocate for leaving PHP behind then me, but it was where it all started for me. I had played around with VB in grade school, but desktop programming never got to me like web programming. PHP was ready for me, meaning the metaphorical person who doesn’t know how to program but wants to learn.</description>
    </item>
    
    <item>
      <title>Hacker from both Flickr, and Stamen Design writes about curation.</title>
      <link>https://rumproarious.com/2010/10/06/hacker-from-both-flickr-and-stamen-design-writes-about-curation/</link>
      <pubDate>Wed, 06 Oct 2010 03:45:41 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/10/06/hacker-from-both-flickr-and-stamen-design-writes-about-curation/</guid>
      <description>If you are interested at all in what is happing to curation you should read this well-researched article by Aaron Cope. The article stems from Cope&amp;rsquo;s time at Stamen Design Group, and Flickr, but it doesn&amp;rsquo;t stop there. This is a deep article with a lot of links, and references.
 What the Internet has done to the field of journalism, it will do to the practice of curation. This is not a claim based on empirical study, but rather, a prediction based on the evolution of “social software”, communities of interest that form and exist principally in on-line networks and a need to find stable ground in a digital world where the means and cost of production and distribution has approached zero.</description>
    </item>
    
    <item>
      <title>I am leaving Yahoo!</title>
      <link>https://rumproarious.com/2010/09/08/i-am-leaving-yahoo/</link>
      <pubDate>Wed, 08 Sep 2010 18:52:37 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/09/08/i-am-leaving-yahoo/</guid>
      <description>I have spent the last 3 years, or so, working at Yahoo!, you must raise your voice at the end of the hoo, and it has been awesome. The opportunities to learn, and grow were huge, but it&amp;rsquo;s time for me to move on. In any organization you can pick it apart, and I have, but my move isn&amp;rsquo;t about that. If anything, it&amp;rsquo;s about getting a variety of experience.</description>
    </item>
    
    <item>
      <title>I wrote a guest post for the DailyJS: The Future of Mobile Sync</title>
      <link>https://rumproarious.com/2010/09/03/i-wrote-a-guest-post-for-the-dailyjs-the-future-of-mobile-sync/</link>
      <pubDate>Fri, 03 Sep 2010 17:59:05 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/09/03/i-wrote-a-guest-post-for-the-dailyjs-the-future-of-mobile-sync/</guid>
      <description>I have been really impressed with the coverage of the javascript community over at DailyJS. So, when they were asking for guest bloggers I jumped at the chance. I chose to write about an idea that has started to surface which is mobile data sync. Sync can be tricky especially when you mix in the fact that mobile devices can be offline for long periods of time. I tried to find a solution, but couldn&amp;rsquo;t find anything.</description>
    </item>
    
    <item>
      <title>Medium, Curators, and Jason Santa Maria</title>
      <link>https://rumproarious.com/2010/08/12/medium-curators-and-jason-santa-maria/</link>
      <pubDate>Thu, 12 Aug 2010 06:13:32 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/08/12/medium-curators-and-jason-santa-maria/</guid>
      <description>If you haven&amp;rsquo;t checked out anything from Jason Santa Maria, go check his blog out. He has been around for a long time, I think. The fact that I don&amp;rsquo;t know much about him is what impresses me the most. I have read a few of his blog post, but each one has been incisive, and powerful so that they stand on their own. I don&amp;rsquo;t need to know who he is to understand the he gets it.</description>
    </item>
    
    <item>
      <title>HTML5 Brief: in a couple paragraphs</title>
      <link>https://rumproarious.com/2010/08/08/html5-brief-in-a-couple-paragraphs/</link>
      <pubDate>Sun, 08 Aug 2010 17:12:00 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/08/08/html5-brief-in-a-couple-paragraphs/</guid>
      <description>HTML5 is a loaded term that covers a range of ideas, but here is an attempt to explain it. Explicitly, all that HTML5 stands for is the next version of HTML. After this version there will be no more versions of HTML. Instead they will evolve the spec slowly over time instead of using major revisions. The next gold standard was going to be XHTML2, but it got dumped because it was built on an unrealistic view of the web.</description>
    </item>
    
    <item>
      <title>I just read the most wonderful short story: Mr. Penumbra’s Twenty-Four-Hour Book Store</title>
      <link>https://rumproarious.com/2010/07/26/i-just-read-the-most-wonderful-short-story-mr-penumbras-twenty-four-hour-book-store/</link>
      <pubDate>Mon, 26 Jul 2010 18:46:40 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/07/26/i-just-read-the-most-wonderful-short-story-mr-penumbras-twenty-four-hour-book-store/</guid>
      <description>here is the story
My favorite part besides the book was that I started to read it as if it was a dudes blog post about working in a 24 hour book shop. I thought the whole thing was real.
The story was based in San Francisco too, and I was going to go to the store and check it out. Near the end of the story though something happened that isn&amp;rsquo;t real, and I realized it was a short story, and not a blog post, although it was written in the style of a longish blog post.</description>
    </item>
    
    <item>
      <title>The mosh pit and cognative surplus.</title>
      <link>https://rumproarious.com/2010/07/12/the-mosh-pit-and-cognative-surplus/</link>
      <pubDate>Mon, 12 Jul 2010 06:52:45 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/07/12/the-mosh-pit-and-cognative-surplus/</guid>
      <description>I was caught off guard by an interesting compare/contrast over at snarkmarket. Two quotes from recent books, both disparaging looks at pre-internet life. The author, Tim Carmody, asks if these kinds of feelings are what are driving us to use our cognitive surplus towards creation.
Maybe slightly, orthogonal to his original idea, was a thought that pop&amp;rsquo;ed into my head. Not just why are people leaving TV, but how. I have tried to get my parents to use &amp;ldquo;newer&amp;rdquo; things, like linux, bad idea I know, but here they are using the internet in interesting ways, in creative ways all without &amp;ldquo;my help&amp;rdquo;.</description>
    </item>
    
    <item>
      <title>Published An Article On The YUI Blog</title>
      <link>https://rumproarious.com/2010/05/28/published-an-article-on-the-yui-blog/</link>
      <pubDate>Fri, 28 May 2010 00:24:53 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/05/28/published-an-article-on-the-yui-blog/</guid>
      <description>I just published an article on the YUI Blog. I have been working at a Yahoo! for almost 3 years now.
I have enjoyed more of my time at Yahoo, then not, and I think that Yahoo has a lot of really cool things going on. I have met some of the smartest developers I have ever worked with inside of Yahoo, and there is a lot of technical brilliance here.</description>
    </item>
    
    <item>
      <title>User Driven Design, Requires Talking To Users</title>
      <link>https://rumproarious.com/2010/05/28/user-driven-design-requires-talking-to-users/</link>
      <pubDate>Fri, 28 May 2010 00:04:53 -0700</pubDate>
      
      <guid>https://rumproarious.com/2010/05/28/user-driven-design-requires-talking-to-users/</guid>
      <description>I have made a number of websites, small and large. I would say that wacchen, is my fifth large project &amp;ldquo;launch&amp;rdquo;. I take that word &amp;ldquo;launch&amp;rdquo; with a grain of salt because this time I have done almost no fanfare. I just started by sharing things on my blog, and twitter.
People have started to show up, about 8 of them so far. That is fine by me, this is actually a great little rollout.</description>
    </item>
    
    <item>
      <title>Universal Feed Parser is awesome, except for embedded videos.</title>
      <link>https://rumproarious.com/the-stream/universal-feed-parser-is-awesome-except-for-embedded-videos/</link>
      <pubDate>Fri, 07 May 2010 22:39:43 -0700</pubDate>
      
      <guid>https://rumproarious.com/the-stream/universal-feed-parser-is-awesome-except-for-embedded-videos/</guid>
      <description>If you have never dealt with pythons awesome feedparser, Universal Feed Parser, you should check it out. This bad boy can take some of the crapiest, most mal-formed feeds atom, or rss, and give you back manicured, well formed python objects. I have used the project many times over, and am indebted.
There current security model is so tight that it removes all object, and embed tags. This is very secure, and for most people probably a good idea.</description>
    </item>
    
    <item>
      <title></title>
      <link>https://rumproarious.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://rumproarious.com/about/</guid>
      <description>For many years I was fascinated by RSS and Feed Readers. I wrote a number of blogposts about RSS and Feed Readers, but they no longer represent a burning passion for me that they once did. I don&amp;rsquo;t want to remove the posts, but I dont&#39; want them to be as front and center as they used to be. You can find them here.</description>
    </item>
    
  </channel>
</rss>
