<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Matt Hanley Storytelling &#187; Random / Consumerism</title>
	<atom:link href="http://matthanley.com/category/random-consumerism/feed/" rel="self" type="application/rss+xml" />
	<link>http://matthanley.com</link>
	<description></description>
	<lastBuildDate>Tue, 31 Jan 2012 04:08:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Preventing the Spread of Perishables</title>
		<link>http://matthanley.com/2011/05/preventing-the-spread-of-perishables/</link>
		<comments>http://matthanley.com/2011/05/preventing-the-spread-of-perishables/#comments</comments>
		<pubDate>Thu, 26 May 2011 18:44:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Random / Consumerism]]></category>
		<category><![CDATA[Software / Usability]]></category>
		<category><![CDATA[household tips]]></category>

		<guid isPermaLink="false">http://matthanley.com/?p=1699</guid>
		<description><![CDATA[Summary: it is not always wise to discard an expired food product. *** Sometimes you have to knowingly keep an expired item in the fridge for the very simple reason of avoiding further expiration. This would happen in cases where you cannot soon remove the item from the household. Take for example, an instance where [...]]]></description>
			<content:encoded><![CDATA[<p>Summary: it is not always wise to discard an expired food product.<br />
***<br />
Sometimes you have to knowingly keep an expired item in the fridge for the very simple reason of avoiding further expiration. This would happen in cases where you cannot soon remove the item from the household. Take for example, an instance where you discover that your mayo (or Miracle Whip!) has been &#8216;bad&#8217; since two months ago. You may feel upset, and wish to banish the item from the fridge, either as a punitive measure or so that you (or others in house) &#8220;won&#8217;t be fooled again.&#8221;  So, you toss it in the trash&#8230; then what? The item&#8217;s condition will worsen, and the family welfare will suffer for it. Imagine if you did the same with old meat. (Hello buzzards!)</p>
<p>So, unless you are planning to take the trash OUT, you should not simply put the old mayo in the kitchen&#8217;s trash bin. Instead, preserve it in the fridge, perhaps in a designated &#8216;Expired&#8217; zone.  Then you can schedule a time to evacuate expired items. Yep.. just like the end of Vietnam. Get yourself a chopper! </p>
]]></content:encoded>
			<wfw:commentRss>http://matthanley.com/2011/05/preventing-the-spread-of-perishables/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Accepting Data: I&#8217;ll see your ten and raise you&#8230;</title>
		<link>http://matthanley.com/2011/04/accepting-data-ill-see-your-ten-and-raise-you/</link>
		<comments>http://matthanley.com/2011/04/accepting-data-ill-see-your-ten-and-raise-you/#comments</comments>
		<pubDate>Tue, 26 Apr 2011 17:40:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Math & Science]]></category>
		<category><![CDATA[Random / Consumerism]]></category>
		<category><![CDATA[bus tracking]]></category>
		<category><![CDATA[city life]]></category>
		<category><![CDATA[transit]]></category>

		<guid isPermaLink="false">http://matthanley.com/?p=1692</guid>
		<description><![CDATA[Summary: Questions the idea of cancelling a data request when a seemingly more apparent answer becomes known. ** **** At Chicago bus stops, a sign gives a code for sending a text and receiving the predicted arrival time. Such trackers are becoming common in cities, for both bus and train ETA, and can be delivered [...]]]></description>
			<content:encoded><![CDATA[<p>Summary: Questions the idea of cancelling a data request when a seemingly more apparent answer becomes known. **<br />
****</p>
<p>At Chicago bus stops, a sign gives a code for sending a text and receiving  the predicted arrival time. Such trackers are becoming common in cities, for both bus and train ETA, and can be delivered via web, apps, and SMS.  This morning I arrived at a stop and entered the code but before I clicked send, the bus became visible about one-half of a mile away. My instinct was to put aside the phone, because the &#8216;answer&#8217; was right before me&#8230;  I thought about it, and decided this was short-sighted. I should have completed the data request and gotten the ETA from the authority. Why? </p>
<p>There are many variables that determine the speed of a bus, and a highly influential &#8211;and dynamic &#8212; component is the quantity of stops.  (Anything can happen at a stop.. or nothing at all). Even though the bus was visible, it was still more than 2 stops away, which made it susceptible to further delays. In an opposing situation, the distance (to a newcomer) might seem to include multiple stops, but might be an &#8216;express&#8217; or be entering a stretch of no stops. </p>
<p>The data provider (the &#8216;authority&#8217;) likely has a long history of each bus line to generate its algorithmic prediction. It is worthwhile to collect this wisdom while we wait as an ADDITIONAL source of data. We can of course still LOOK at the approaching bus. What about the COST of sending and receiving a text? It might be as much as $.20 for those who lack a high-quantity text plan. In that case, one would have to determine the value of receiving the authority&#8217;s prediction. It would likely be more valuable to keep the twenty cents, especially since the authority is often inaccurate&#8230; HA HA&#8230; but the inaccuracy is still of value! It is still data that YOU, as your own ultimate authority, can use, going forward. Example: </p>
<p>Authority predicts 2 minutes; Actual wait was 5 minutes&#8230; this provides guidance. It would take a lot of data to generate your own rule set, and you would likely be ruined by a dependence on a simple conclusion such as &#8220;authority always underestimates by 3 minutes.&#8221;  More preferable, would be for the authority itself to constantly be given corrections for each of its predictions. That&#8217;s the Google method, but the catch is the eventual Big Brother apparatus.</p>
<p>But for you to collect as much data as you can &#8211; by having as much knowledge and experience as possible&#8211; you would at least know that that is that and this is this&#8230; and isn&#8217;t that what life is about? </p>
<p>On the other hand, by busying yourself with texting, you may have missed a smile. </p>
]]></content:encoded>
			<wfw:commentRss>http://matthanley.com/2011/04/accepting-data-ill-see-your-ten-and-raise-you/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Traffic Jams: 2 lanes merge into one lane</title>
		<link>http://matthanley.com/2011/03/traffic-jams-2-lanes-merge-into-one-lane/</link>
		<comments>http://matthanley.com/2011/03/traffic-jams-2-lanes-merge-into-one-lane/#comments</comments>
		<pubDate>Mon, 21 Mar 2011 01:54:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Math & Science]]></category>
		<category><![CDATA[Random / Consumerism]]></category>
		<category><![CDATA[Software / Usability]]></category>
		<category><![CDATA[traffic]]></category>

		<guid isPermaLink="false">http://matthanley.com/?p=1577</guid>
		<description><![CDATA[Yesterday I was in the slowest-moving traffic of my life experience. A seven-mile trip to Folly Beach removed 75 minutes from my life. There were several factors contributing to the inefficiency, such as it being the first hot weekend beach day in the area; cars not at full capacity (several were with neither passengers nor [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday I was in the slowest-moving traffic of my life experience. A seven-mile trip to Folly Beach removed 75 minutes from my life. There were several factors contributing to the inefficiency, such as it being the first hot weekend beach day in the area; cars not at full capacity (several were with neither passengers nor drivers); hotel check-in period for visitors; two-lane road turning into a one-lane road. This last factor was most important, and the subject of our post. In yesterday&#8217;s case, it was the right lane that ends, requiring its cars to move over into the left lane. It is now my belief that the &#8216;ending&#8217; lane always moves faster than the &#8216;ceding&#8217; lane, so you should take the non-ceder if you are aware of the situation. This theory is based on human psychology and probability. Here are the issues that favor the &#8216;dead-end&#8217; lane:</p>
<ol>
<li>Fear. More people than not want to be safe and not risk depending on the mercy of others. It is also more common to fear angering other motorists, by pestering them for an opening. The fearful lane is more populated; the dead-end lane less populated, so it moves faster. At the point of the merger the driver who fears displeasing another motorist will let other car(s) merge ahead of her.</li>
<li>Reciprocity. Among the occupants of the ceding lane are former dead-enders who migrated to the single lane. Of these, a majority will be prone to let a cohort inside due to empathy and feelings of fair play.</li>
<li>Nature. The true nature of these respective lanes force an action in the drivers&#8217; favor. The dead-end would seem to require &#8216;yielding&#8217; but actually the ceding lane must yield. That is why it is the ceding lane. A dead-end driver cannot possibly yield to the other lane&#8211;there&#8217;s no place to go. The traffic <em><strong>must</strong></em> be merged. So given the weight of that necessary movement, it will happen (sooner rather than later). This third factor relates to the aggregate of the lanes and the cars, and is therefore a check on the individual hostilities or whims of people.  Even if many people in the ceding lane are vengeful and hostile, they will, as a whole, cede to the other lane out of necessity.</li>
</ol>
<p>Conclusion: Take the fast lane and ye shall be rewarded.</p>
]]></content:encoded>
			<wfw:commentRss>http://matthanley.com/2011/03/traffic-jams-2-lanes-merge-into-one-lane/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WWW is not Free for All</title>
		<link>http://matthanley.com/2011/03/www-is-not-free-for-all/</link>
		<comments>http://matthanley.com/2011/03/www-is-not-free-for-all/#comments</comments>
		<pubDate>Fri, 11 Mar 2011 03:05:26 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Random / Consumerism]]></category>
		<category><![CDATA[Facebook]]></category>
		<category><![CDATA[phones]]></category>

		<guid isPermaLink="false">http://matthanley.com/?p=1566</guid>
		<description><![CDATA[Facebook, Twitter and most web sites are free. All you need is a $500-800 device, and $100 per month to a phone company.]]></description>
			<content:encoded><![CDATA[<p>Facebook, Twitter and most web sites are free. All you need is a $500-800 device, and $100 per month to a phone company. </p>
]]></content:encoded>
			<wfw:commentRss>http://matthanley.com/2011/03/www-is-not-free-for-all/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>On-demand production</title>
		<link>http://matthanley.com/2011/03/on-demand-production/</link>
		<comments>http://matthanley.com/2011/03/on-demand-production/#comments</comments>
		<pubDate>Sat, 05 Mar 2011 22:49:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Matt News]]></category>
		<category><![CDATA[Random / Consumerism]]></category>
		<category><![CDATA[blogs]]></category>
		<category><![CDATA[TV]]></category>

		<guid isPermaLink="false">http://matthanley.com/2011/03/on-demand-production/</guid>
		<description><![CDATA[Since Hulu, and Neflix have become popular, people have discussed ‘on-demand’ consumption, wherein the consumer can choose when to consume a movie or TV show, just as she chooses when to listen to a song. Can there be a similar ‘on-demand’ production paradigm? I’m thinking of this because I’ve starting publishing a weekly magazine. Magazine’s [...]]]></description>
			<content:encoded><![CDATA[<p>Since Hulu, and Neflix have become popular, people have discussed ‘on-demand’ consumption, wherein the consumer can choose when to consume a movie or TV show, just as she chooses when to listen to a song. </p>
<p>Can there be a similar ‘on-demand’ production paradigm? </p>
<p>I’m thinking of this because I’ve starting publishing a weekly magazine. Magazine’s are usually weekly, and I wanted the challenge of meeting a deadline. But it causes much stress, and there is not a demand to warrant it. I do have to create demand. But do I still have to create an issue each week at the same time? </p>
<p>Welp, of course I do not HAVE to do anything. And of course, often times a brand new thing does not have fans, or demand. But as I try to interest people in the content, I am wary of promising a weekly output. </p>
<p>Output should be constantly POSSIBLE, but collected into something PERIODICALLY. I think that is the new model. So I will switch over to a Blog, and then inform ‘followers’ when a new ‘magazine’ is available. </p>
]]></content:encoded>
			<wfw:commentRss>http://matthanley.com/2011/03/on-demand-production/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

