<?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>t+1 &#187; spreadsheets</title>
	<atom:link href="http://blog.tplus1.com/index.php/category/spreadsheets/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tplus1.com</link>
	<description>Programming, gardening, economics, life in Cleveland Heights</description>
	<lastBuildDate>Sat, 07 Jan 2012 21:12:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Spreadsheets are the devil, but here is how to avoid getting burned.</title>
		<link>http://blog.tplus1.com/index.php/2007/10/27/spreadsheets-are-the-devil-but-here-is-how-to-avoid-getting-burned/</link>
		<comments>http://blog.tplus1.com/index.php/2007/10/27/spreadsheets-are-the-devil-but-here-is-how-to-avoid-getting-burned/#comments</comments>
		<pubDate>Sat, 27 Oct 2007 21:27:53 +0000</pubDate>
		<dc:creator>matt</dc:creator>
				<category><![CDATA[spreadsheets]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://blog.tplus1.com/index.php/2007/10/27/spreadsheets-are-the-devil-but-here-is-how-to-avoid-getting-burned/</guid>
		<description><![CDATA[Spreadsheets seem like they are adequate tools for serious analysis.  And unfortunately, people are graduating from stats and OR programs without mastering any of the other alternatives.  But brother, I stand before you today to tell you that spreadsheets are the devil.
When you face a modeling problem, spreadsheets tempt you with the seemingly [...]]]></description>
			<content:encoded><![CDATA[<p>Spreadsheets seem like they are adequate tools for serious analysis.  And unfortunately, people are graduating from stats and OR programs without mastering any of the other alternatives.  But brother, I stand before you today to tell you that <b>spreadsheets are the devil</b>.</p>
<p>When you face a modeling problem, spreadsheets tempt you with the seemingly easy way out.  It all starts with how easy it is to import data.  Excel&#8217;s import wizard is fast and pretty smart about automatically assigning column types.  Meanwhile, your hapless colleagues are going to spend a day reading manuals just to load in that same tab-delimited text file.</p>
<p>Now that you&#8217;ve got the raw inputs loaded, you figure that within a few days you&#8217;ll be done building your trendlines and you&#8217;ll kill time choosing fonts for your pie charts.  But what happens &#8212; invariably &#8212; is that you think you are done and then you look at your number on your final worksheet and realize it can&#8217;t be right.  You must now find the error in any of the possibly hundreds of tiny formulas all chained together.  Welcome to cell HE11.</p>
<p>Meanwhile, while you&#8217;ve got numbers that are laughably wrong, your SAS friend after a few days at least has his PROC REPORT output to show the boss, even if he did have to print it on the basement mainframe dot-matrix printer.</p>
<p>So, despite all that, sometimes, I find that I just have to use a spreadsheet.  In that circumstance, I try to follow a set of rules.  Any time I deviate from these rules, I  always get burned.</p>
<ol>
<li style="list-style-type:lower-greek">Put at the top of each sheet a few paragraphs that describe the model.  Ideally, this text should be so clear and specific that I can rebuild the spreadsheet just based on this information.  (This also helps make sure that you implemented the logic correctly.)</li>
<li style="list-style-type:lower-greek">Indicate what are the cells that the user should play with, and what cells should not be tweaked.  Point out where the final answer pops out.  Establish a color scheme to distinguish between input data and formulas.</li>
<li style="list-style-type:lower-greek">Emulate the IRS 1040, where there is a column of text and just a few columns of numbers, and each row is as simple as possible.  There&#8217;s a main column that gets summed at the bottom, and a secondary column where complex totals are broke down further.</li>
<li style="list-style-type:lower-greek">Decompose those formulas and don&#8217;t store literal data inside of formulas!  For example, in a mortgage calculator, break out the interest rate, the mortgage size, and the number of years in the mortgage into separate cells, and then show the result in another cell:
<p><a href='http://blog.tplus1.com/wp-content/uploads/2007/10/s1.png' title='s1'><img src='http://blog.tplus1.com/wp-content/uploads/2007/10/s1.png' alt='s1' /></a></p>
<p>Don&#8217;t be tempted to cram all those numbers inside a single cell like this:</p>
<p><a href='http://blog.tplus1.com/wp-content/uploads/2007/10/s2.png' title='s2'><img src='http://blog.tplus1.com/wp-content/uploads/2007/10/s2.png' alt='s2' /></a></p>
<p>Sure, you save a few rows and it compresses the size of your sheet, but in the end, you make your sheet much less flexible, and it will be more difficult to separate data-entry errors from formula errors.</p>
<li style="list-style-type:lower-greek">Finally, Put everything in top-to-bottom order in each sheet and have a single flow.   Don&#8217;t have lots of parallel panels side-by-side.  It becomes too confusing.</li>
</ol>
<p>I am certain that there are even more rules that are better than these.  Enlighten me.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.tplus1.com/index.php/2007/10/27/spreadsheets-are-the-devil-but-here-is-how-to-avoid-getting-burned/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

