<?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>Structures Workshop Blog</title>
	<atom:link href="http://structuresworkshop.com/blog/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://structuresworkshop.com/blog</link>
	<description>By Erik Anders Nelson, PE, SE</description>
	<lastBuildDate>Fri, 11 May 2012 12:31:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>25:  Don&#8217;t Not Do It</title>
		<link>http://structuresworkshop.com/blog/2012/05/09/25-dont-not-do-it/</link>
		<comments>http://structuresworkshop.com/blog/2012/05/09/25-dont-not-do-it/#comments</comments>
		<pubDate>Wed, 09 May 2012 01:02:33 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[A Structural Engineer's Manifesto for Individual Growth]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1057</guid>
		<description><![CDATA[“Just do it” from Nike is fine but it seems to be about finishing something you need to finish, not necessarily because you want to finish (say avoiding procrastination).  So that isn’t enough.  “Don’t not do it” is about doing &#8230; <a href="http://structuresworkshop.com/blog/2012/05/09/25-dont-not-do-it/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>“Just do it” from Nike is fine but it seems to be about finishing something you need to finish, not necessarily because you want to finish (say avoiding procrastination).  So that isn’t enough.  “Don’t not do it” is about doing something you want to do but are afraid (worried because it is different, or maybe slightly embarrassing, or risky, etc).  It may be already finished or easy to finish but you are scared.   These are the things you need to do.   If you purge these mental roadblocks, you will benefit yourself.   You will never be “better than the rest” if you don’t allow yourself to complete something because of worry or risk – you will be the rest.  Don’t be the rest.  Don’t not do it.</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/05/09/25-dont-not-do-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Truth of Structural Design</title>
		<link>http://structuresworkshop.com/blog/2012/05/09/the-truth-of-structural-design/</link>
		<comments>http://structuresworkshop.com/blog/2012/05/09/the-truth-of-structural-design/#comments</comments>
		<pubDate>Wed, 09 May 2012 00:43:25 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1049</guid>
		<description><![CDATA[There seems to be a progression of understanding as one designs structures. At first, as college students, we have well defined analytical techniques that appear objective and clear (there is truth). Later we learn this idea of structural design is &#8230; <a href="http://structuresworkshop.com/blog/2012/05/09/the-truth-of-structural-design/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>There seems to be a progression of understanding as one designs structures. At first, as college students, we have well defined analytical techniques that appear objective and clear (there is truth). Later we learn this idea of structural design is naïve. What we do is not clean. As the years go by, there is an improvement of the design of structures which combines the simple objective science with more complex subjective decision making requiring sound judgment (heuristics). There is not truth anymore, what is left is &#8220;good enough&#8221;. Problems encountered by the structural engineer are complex and nuanced and require experience and judgment to better sift through the multiple design ideas.</p>
<p>If there was a progression in the mind of a structural engineer, I think it is similar to the one that the philosopher Friedrich Nietzsche wrote about in “Twilight of the Idols” (see MSC article). While Nietzsche was generally referring to raising the human spirit to a higher level, it is similar to my experience, going from 1 to 6, as a structural engineer over the fifteen years:</p>
<p>1. The ”truth” of structural design – is attainable for the sage, the pious, the virtuous man.</p>
<p>2. The “truth” of structural design &#8211; unattainable for now, but promised for the sage, the pious, the virtuous man.</p>
<p>3. The “truth” of structural design &#8211; unattainable, indemonstrable; but the very thought of it &#8211; a consolation, an obligation, an imperative.</p>
<p>4. The “truth” of structural design &#8211; unattainable? At any rate, unattained. And being unattained, also unknown. Consequently, not consoling, redeeming, or obligating: how could something unknown obligate us?</p>
<p>5. The “truth” of structural design &#8211; an idea which is no longer good for anything, not even obligating &#8211; an idea which has become useless and superfluous &#8211; consequently, a refuted idea: let us abolish it!</p>
<p>6. The “truth” of structural design — we have abolished. What world has remained? The apparent one perhaps? But no! With the true world we have also abolished the apparent one.</p>
<p>Thus, we have abolished truth in practice even if we pretend it still exists in school. Good enough is enough in practice (i.e. a good enough design decision = a correct answer). That doesn&#8217;t make it easy, “good enough” is actually very hard. It is apparent in this progression the great extent to which the individual engineer can influence the design. I have found that the design of structures is less dispassionate and logical than I used to earlier in my career. There are no clear-cut answers to the complex and diverse problems we face. This is not to diminish the role of analytical tools to assimilate knowledge of phenomenon, it is just that it is simply not enough.</p>
<p>(E Nelson,  portion of MSC Twilight of the Idols)</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/05/09/the-truth-of-structural-design/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manifesto for Growth Part 2</title>
		<link>http://structuresworkshop.com/blog/2012/05/02/manifesto-for-growth-part-2/</link>
		<comments>http://structuresworkshop.com/blog/2012/05/02/manifesto-for-growth-part-2/#comments</comments>
		<pubDate>Wed, 02 May 2012 19:45:31 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Publications]]></category>
		<category><![CDATA[Structures Workshop News]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1041</guid>
		<description><![CDATA[05/2012 Published “Manifesto for Growth Part 2” in May 2012 STRUCTURE Magazine.   See this blog to comment on specific numbers. Structure Mag-May 2012 Note:   Part 8 should be &#8220;Kick Ass&#8221; (or &#8220;Kick Butt&#8221;), but the editors of STRUCTURE changed it to &#8220;Be &#8230; <a href="http://structuresworkshop.com/blog/2012/05/02/manifesto-for-growth-part-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>05/2012 Published “Manifesto for Growth Part 2” in May 2012 <em>STRUCTURE</em> Magazine.   See this blog to comment on specific numbers. <a href="http://structuresworkshop.com/blog/wp-content/uploads/2012/05/D-StrucForum-Nelson-May12-4-10.pdf">Structure Mag-May 2012</a></p>
<p>Note:   Part 8 should be &#8220;Kick Ass&#8221; (or &#8220;Kick Butt&#8221;), but the editors of <em>STRUCTURE</em> changed it to &#8220;Be Aggressive&#8221; unfortunately.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/05/02/manifesto-for-growth-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Recent Day, Smelly Braced Frames</title>
		<link>http://structuresworkshop.com/blog/2012/05/02/a-recent-day-smelly-braced-frames/</link>
		<comments>http://structuresworkshop.com/blog/2012/05/02/a-recent-day-smelly-braced-frames/#comments</comments>
		<pubDate>Wed, 02 May 2012 01:28:12 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1033</guid>
		<description><![CDATA[Engineers have to straddle many worlds.  We may find ourselves one day designing steel connections, then meeting on a new job to discuss appropriate structural systems, then doing some BIM modeling.   As we grow into project managers we may find &#8230; <a href="http://structuresworkshop.com/blog/2012/05/02/a-recent-day-smelly-braced-frames/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Engineers have to straddle many worlds.  We may find ourselves one day designing steel connections, then meeting on a new job to discuss appropriate structural systems, then doing some BIM modeling.   As we grow into project managers we may find ourselves writing emails and attending meetings possibly more than doing engineering calculations.   We use our judgement more and more to know where to start a problem and what to ignore.   There are no typical days.  I had a day recently where one morning I designed all the braced frame connections on a job and then in the afternoon attended a project review at an architectural college.  The student project consisted of spreading toothpaste on the wall and discussing how smell should be incorporated more into our built world.   That is right, smell &#8211; and objects should contain smell.   For some reason at that moment, it made sense.  I thought about what the brace frame connection smelled like that I designed that morning.   Not sure why, but I thought of that premade potato salad with that overly smelly mayo/mustard dressing.</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/05/02/a-recent-day-smelly-braced-frames/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Dreams, Mistakes and Uncomfortable Decisions</title>
		<link>http://structuresworkshop.com/blog/2012/05/02/dreams-mistakes-and-uncomfortable-decisions/</link>
		<comments>http://structuresworkshop.com/blog/2012/05/02/dreams-mistakes-and-uncomfortable-decisions/#comments</comments>
		<pubDate>Wed, 02 May 2012 01:11:56 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1026</guid>
		<description><![CDATA[I woke up at 3am today again.  It was the same dream, or similar dream to what I have been having over the last decade.   I forgot to check something.  I missed something in the code or I missed something &#8230; <a href="http://structuresworkshop.com/blog/2012/05/02/dreams-mistakes-and-uncomfortable-decisions/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I woke up at 3am today again.  It was the same dream, or similar dream to what I have been having over the last decade.   I forgot to check something.  I missed something in the code or I missed something more structurally egregious.    This latest dream was something that surprised me because I was actually wrong, I did check it!   I came to work early to discover that I did check this beam for additional load due to this or that, so no big deal.   Sometimes my dreams help me, I get a sort of eureka moment and I am better able to tackle such and such problem.   Other dreams are harmful, and they make me nervous and anxious and I can’t get back to bed.   There are two main themes to these dreams:  (1) Mistakes, whether real or imagined, and (2) Uncomfortable Decisions. </p>
<p>Uncomfortable decisions are by far the most common of my dreams.  These are engineering decisions that are made without the best understanding of how the part or system will perform (very common daily decisions when unique details or structures are developed).  This is why engineering is a profession.   We need to pull things out of a hat sometimes and live with them.  Part of the anxiety of a structural engineer is that we are solving problems that never existed before, we are inventing something new.    Yes, physics doesn’t change, but that is about the only thing that doesn’t.   Every building has traits that no other building in the world has, and have we verified everything?   Of course not.   But have we verified everything we know how to verify?  After all the calculations are applied, we still have to make a decision about whether it should be built a particular way or be changed.  Eventually we have to say yes, “no exceptions taken” and live with it the rest of our lives.   Crazy things get built and amazing engineers are the creative force behind all of them.  How many structures out there do we lose sleep on?  Maybe 2-3 per year on average?</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/05/02/dreams-mistakes-and-uncomfortable-decisions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manifesto for Growth Part 1</title>
		<link>http://structuresworkshop.com/blog/2012/04/07/manifesto-for-growth-part-1/</link>
		<comments>http://structuresworkshop.com/blog/2012/04/07/manifesto-for-growth-part-1/#comments</comments>
		<pubDate>Sat, 07 Apr 2012 20:33:04 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>
		<category><![CDATA[Publications]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1010</guid>
		<description><![CDATA[04/2012 Published “Manifesto for Growth Part 1” in April 2012 STRUCTURE Magazine.   See this blog to comment on specific numbers.   Manifesto Part 1]]></description>
			<content:encoded><![CDATA[<p>04/2012 Published “Manifesto for Growth Part 1” in April 2012 <em>STRUCTURE</em> Magazine.   See this blog to comment on specific numbers.   <a href="http://structuresworkshop.com/blog/wp-content/uploads/2012/04/D-StrucForum-Nelson-Apr12-3-131.pdf">Manifesto Part 1</a></p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/04/07/manifesto-for-growth-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What makes an Engineer, an Engineer?</title>
		<link>http://structuresworkshop.com/blog/2012/03/27/what-makes-an-engineer-an-engineer/</link>
		<comments>http://structuresworkshop.com/blog/2012/03/27/what-makes-an-engineer-an-engineer/#comments</comments>
		<pubDate>Tue, 27 Mar 2012 19:26:52 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Publications]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1005</guid>
		<description><![CDATA[03/2012 ASCE-SEI Structures Congress Procedings “What makes an Engineer, an Engineer”   Click here for What Makes An Engineer An Engineer ENelson.]]></description>
			<content:encoded><![CDATA[<p>03/2012 ASCE-SEI Structures Congress Procedings “What makes an Engineer, an Engineer”   Click here for <a href="http://structuresworkshop.com/blog/wp-content/uploads/2012/03/What-Makes-An-Engineer-An-Engineer-ENelson.pdf">What Makes An Engineer An Engineer ENelson</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/03/27/what-makes-an-engineer-an-engineer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Erik Nelson to present at Structures Congress in Chicago</title>
		<link>http://structuresworkshop.com/blog/2012/03/27/erik-nelson-to-present-at-structures-congress-in-chicago/</link>
		<comments>http://structuresworkshop.com/blog/2012/03/27/erik-nelson-to-present-at-structures-congress-in-chicago/#comments</comments>
		<pubDate>Tue, 27 Mar 2012 19:21:47 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>
		<category><![CDATA[Structures Workshop News]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=1003</guid>
		<description><![CDATA[Erik will be presenting &#8220;What makes an Engineer, an Engineer?&#8221; at the Structures Congress in Chicago, IL on Friday March 30, 2012.   PPT to come.]]></description>
			<content:encoded><![CDATA[<p>Erik will be presenting &#8220;What makes an Engineer, an Engineer?&#8221; at the Structures Congress in Chicago, IL on Friday March 30, 2012.   PPT to come.</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/03/27/erik-nelson-to-present-at-structures-congress-in-chicago/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Structures Workshop invests in New Software</title>
		<link>http://structuresworkshop.com/blog/2012/02/26/structures-workshop-invests-in-new-software/</link>
		<comments>http://structuresworkshop.com/blog/2012/02/26/structures-workshop-invests-in-new-software/#comments</comments>
		<pubDate>Sun, 26 Feb 2012 22:19:26 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Structures Workshop News]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=993</guid>
		<description><![CDATA[We bought 4 licences of Tedds to help us supplement our in-house calculation packages.  In addition, we bought 3 licenses of Bluebeam which help us easily mark-up PDF drawings and coordinate drawings in real time online with multiple users (it is Adobe &#8230; <a href="http://structuresworkshop.com/blog/2012/02/26/structures-workshop-invests-in-new-software/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We bought 4 licences of <a href="http://www.cscworld.com/Products/Tedds.aspx">Tedds</a> to help us supplement our in-house calculation packages.  In addition, we bought 3 licenses of <a href="http://www.bluebeam.com/">Bluebeam</a> which help us easily mark-up PDF drawings and coordinate drawings in real time online with multiple users (it is Adobe Pro on steriods).   We are also considering buying <a href="http://sds2connect.com/">SDS/2 Connect</a> after our 30 day trial to help us coordinate 3d steel connection design within Revit.     These new programs, along with out current licenses of <a href="http://www.csiberkeley.com/etabs">Etabs</a> and <a href="http://usa.autodesk.com/adsk/servlet/pc/index?id=16406616&amp;siteID=123112">Revit</a> allow us to be at the state of the art in the engineering community.</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/02/26/structures-workshop-invests-in-new-software/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Engineering predates Science</title>
		<link>http://structuresworkshop.com/blog/2012/02/13/engineering-predates-science/</link>
		<comments>http://structuresworkshop.com/blog/2012/02/13/engineering-predates-science/#comments</comments>
		<pubDate>Mon, 13 Feb 2012 11:45:39 +0000</pubDate>
		<dc:creator>enelson</dc:creator>
				<category><![CDATA[Philosophy of Engineering]]></category>

		<guid isPermaLink="false">http://structuresworkshop.com/blog/?p=145</guid>
		<description><![CDATA[We were designing and building things long before we had a “scientific” methods and mathematical solution techniques – and we still do today.  We can actually do engineering without science (Pantheon is an example), but science does indeed help and is &#8230; <a href="http://structuresworkshop.com/blog/2012/02/13/engineering-predates-science/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We were designing and building things long before we had a “scientific” methods and mathematical solution techniques – and we still do today.  We can actually do engineering without science (Pantheon is an example), but science does indeed help and is absolutely necessary today.  A calculator helps too.  Did we need to wait for mathematical understanding of a hanging chain before we could build catenaries?  Of course not.   We didn&#8217;t need to wait for Galileo and Bernoulli to create architecture.   We didn&#8217;t need Euler to design columns.  This “pre-science” type of engineering is design and it is still 90% of what we do today.  Have you witnessed the architect August Perret&#8217;s Church of Notre Dame du Raincy?   Were the methods of proportion used in the past flawed?   Sure.   Did they work?   Sure, sometimes.  Are current state-of-the- art methods that are good at mimicking nature still flawed?    Absolutely, less so, yes, but certainly flawed.  We as structural engineers should recognize that while science and math are critically important to what we do, they do not define us &#8211; and history tells us, they never did.  How can we be defined as applied scientists when engineering predates science?</p>
<p>I am particularly suspicious of the idea that our masterbuilders, craftmen, and masons of the past did not understand flexure and compression basics (top of beam is in compression for example or rules for column slenderness).    They may not have had the proper formulas but they certainly had a better intuition than we give them credit.  Yes, Leonardo Da Vinci and Galileo were the first to &#8220;discover&#8221; bending stress by writing it down, but it was used as rules of thumb by our builders well before that time.</p>
<p>In the book &#8220;Structural Engineering:  The Nature and Theory of Design&#8221; William Addis quotes the following statement from Karl Terzaghi challenging the idea that theorey leads to practice:</p>
<blockquote><p>History shows us that there is hardly a single concept of practical importance in the field of structural engineering that was not instinctively anticipated and used with success in design and construction by individuals or groups of engineers many centuries before applied mechanics came into existence.</p></blockquote>
<p>In Henry Petroski&#8217;s book <em>Remaking the World</em>, he states:</p>
<blockquote><p>Some of the first modern engineers did not apply science but rather led science.  The science of thermodynamics may be viewed as an application of steam engines, and rational structural analysis as an application of bridge building.   The view of scientific discovery as depending on the ingenious craftsmanship of instruments, and thus following technology, convincingly flies in the face of the conventional wisdom that technology is mere applied science.  [Petroski, 1997, 17]</p></blockquote>
<p>So according to this, Science is Applied Engineering</p>
]]></content:encoded>
			<wfw:commentRss>http://structuresworkshop.com/blog/2012/02/13/engineering-predates-science/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 1.838 seconds -->
<!-- Cached page served by WP-Cache -->

