<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to Engineer Yourself for Peak Performance</title>
	<atom:link href="http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/feed/" rel="self" type="application/rss+xml" />
	<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/</link>
	<description>For People Pursuing Freedom</description>
	<lastBuildDate>Mon, 15 Feb 2010 04:43:33 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Making The Best Better Team</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4077</link>
		<dc:creator>Making The Best Better Team</dc:creator>
		<pubDate>Fri, 27 Feb 2009 07:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4077</guid>
		<description>Hmmmm,very interesting...

I&#039;ve always believed that peak performance is determined by you choice. Success is not by chance, it’s by CHOICE! And you choose your life&#039;s design for success.

Cheers!
Making The Best Better Team</description>
		<content:encoded><![CDATA[<p>Hmmmm,very interesting&#8230;</p>
<p>I&#8217;ve always believed that peak performance is determined by you choice. Success is not by chance, it’s by CHOICE! And you choose your life&#8217;s design for success.</p>
<p>Cheers!<br />
Making The Best Better Team</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Recipe For Intentional Life &#8212; Practice This</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4076</link>
		<dc:creator>The Recipe For Intentional Life &#8212; Practice This</dc:creator>
		<pubDate>Tue, 14 Oct 2008 13:12:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4076</guid>
		<description>[...] My answer was simple - Engineer Yourself for Peak Performance [...]</description>
		<content:encoded><![CDATA[<p>[...] My answer was simple &#8211; Engineer Yourself for Peak Performance [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Microsoft vs. Google - Competing For GTD &#8212; Practice This</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4075</link>
		<dc:creator>Microsoft vs. Google - Competing For GTD &#8212; Practice This</dc:creator>
		<pubDate>Mon, 07 Apr 2008 02:54:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4075</guid>
		<description>[...] or Google ;), or even beat them both! If you are midlevel manager - you can make your team perform with peak results without burning out and hopefully get promoted to executive level. If you are individual [...]</description>
		<content:encoded><![CDATA[<p>[...] or Google <img src='http://steve-olson.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> , or even beat them both! If you are midlevel manager &#8211; you can make your team perform with peak results without burning out and hopefully get promoted to executive level. If you are individual [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alik</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4073</link>
		<dc:creator>Alik</dc:creator>
		<pubDate>Wed, 26 Mar 2008 22:52:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4073</guid>
		<description>Tola, great to hear you like it. Please meet JD - he responded first to the post.

It amazes me again and again how software engineering techniques can be easily reverse engineered and applied in our own lives. I am both performance and security engineer. I use security engineering techniques in my life too. Take threat modeling, for example. I try to model the threats and their impacts on my life, just like with software. If the threat has low risk I leave it alone and move my energy to something more productive, If the threat has high risk I invest my best to mitigate it completely. This is part of my prioritization technique. It helps me prioritize my energy for high impact results over just completing another task.

Makes sense?</description>
		<content:encoded><![CDATA[<p>Tola, great to hear you like it. Please meet JD &#8211; he responded first to the post.</p>
<p>It amazes me again and again how software engineering techniques can be easily reverse engineered and applied in our own lives. I am both performance and security engineer. I use security engineering techniques in my life too. Take threat modeling, for example. I try to model the threats and their impacts on my life, just like with software. If the threat has low risk I leave it alone and move my energy to something more productive, If the threat has high risk I invest my best to mitigate it completely. This is part of my prioritization technique. It helps me prioritize my energy for high impact results over just completing another task.</p>
<p>Makes sense?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tola</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4074</link>
		<dc:creator>Tola</dc:creator>
		<pubDate>Wed, 26 Mar 2008 01:45:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4074</guid>
		<description>Alik,

Very interesting stuff...I&#039;m not familiar with J.D. Meir, but I love how you&#039;ve incorporated his ideas and translated it into personal development!

state management - sometimes tough for me to isolate one state from another.  i.e. my finances spill over and affect my relationships, etc.

resource management - i believe this.  One&#039;s attention can only be focused on one item at a time.

exception management - goes with my thoughts on adversity:  http://www.rx4life.info/what-is-adversity

algorithms - working on setting schedules and plans - and following them.

coupling/cohesion - i like this one.  It reminds me of the paradox of life.  The more tightly you hold onto something, the more likely you are to lose it.

caching - i&#039;ve always had a problem with this.  no matter what system i use - the trick is to be consistent with any system.

Good stuff,

Tola</description>
		<content:encoded><![CDATA[<p>Alik,</p>
<p>Very interesting stuff&#8230;I&#8217;m not familiar with J.D. Meir, but I love how you&#8217;ve incorporated his ideas and translated it into personal development!</p>
<p>state management &#8211; sometimes tough for me to isolate one state from another.  i.e. my finances spill over and affect my relationships, etc.</p>
<p>resource management &#8211; i believe this.  One&#8217;s attention can only be focused on one item at a time.</p>
<p>exception management &#8211; goes with my thoughts on adversity:  <a href="http://www.rx4life.info/what-is-adversity" rel="nofollow">http://www.rx4life.info/what-is-adversity</a></p>
<p>algorithms &#8211; working on setting schedules and plans &#8211; and following them.</p>
<p>coupling/cohesion &#8211; i like this one.  It reminds me of the paradox of life.  The more tightly you hold onto something, the more likely you are to lose it.</p>
<p>caching &#8211; i&#8217;ve always had a problem with this.  no matter what system i use &#8211; the trick is to be consistent with any system.</p>
<p>Good stuff,</p>
<p>Tola</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alik</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4072</link>
		<dc:creator>Alik</dc:creator>
		<pubDate>Wed, 13 Feb 2008 13:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4072</guid>
		<description>Rob, WOW, what a comment!
I love &quot;friction&quot; notation too. It falls into my life architecture bucket under “pipeline management” category - http://practicethis.com/2008/02/05/life-architecture-for-personal-achievement/
With regards to this post, friction I think can reduced by applying proper caching, algorithms, and data access techniques. Here example how I implement caching to reduce friction when coping with avalanches of daily tasks http://practicethis.com/2008/02/11/the-fast-and-the-peaceful/

BTW, Rob, I liked your music samples very much!</description>
		<content:encoded><![CDATA[<p>Rob, WOW, what a comment!<br />
I love &#8220;friction&#8221; notation too. It falls into my life architecture bucket under “pipeline management” category &#8211; <a href="http://practicethis.com/2008/02/05/life-architecture-for-personal-achievement/" rel="nofollow">http://practicethis.com/2008/02/05/life-architecture-for-personal-achievement/</a><br />
With regards to this post, friction I think can reduced by applying proper caching, algorithms, and data access techniques. Here example how I implement caching to reduce friction when coping with avalanches of daily tasks <a href="http://practicethis.com/2008/02/11/the-fast-and-the-peaceful/" rel="nofollow">http://practicethis.com/2008/02/11/the-fast-and-the-peaceful/</a></p>
<p>BTW, Rob, I liked your music samples very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RobB</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4071</link>
		<dc:creator>RobB</dc:creator>
		<pubDate>Wed, 13 Feb 2008 00:39:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4071</guid>
		<description>Good post Alik. I&#039;ve also been adopting J.D. s methods, though I&#039;m in my infancy. It&#039;s clarified some of these methods further.

I&#039;m the artist type who&#039;s been looking for a method that helps me be flexbile while still making more effective. I&#039;ve used a number of different types of planners from other people and those that I&#039;ve made up myself.

The irony is that I&#039;m anal-retentive in many ways. I&#039;ve worked at organizing content for the last 10 years. Personally, I&#039;ve moved all my bills and things online and have over 10,000 pages scanned into the computer to get rid of my information clutter.

During this time I&#039;ve found two things that are relevant to this post.
1) that it&#039;s easy to get lost in the inflexibility of a system. The simpler you can keep it, the more portable it is to other tools.  The benefits of a simple system like J.Ds is that it&#039;s highly portable to other mail products (not just outlook).

2) J.D. concept of friction. The more friction you have in any area, the harder it is to overcome it, just like in physics.  Friction is equal to
   perceived difficulty of the task
        x
   the number of times you need to perform it in a given time period

Note the &quot;perceived&quot; part.
a) This may be high at the start, but it gets easier as patterns become automatic.
b) The perception is partially controlled by how easy it is to try a different method. For example, on the web, everything is a click away. If you have to travel someplace to start something, there may be as much friction to leave and try something else as there is to just complete the task where you are. The task in front of you can seem &quot;easier&quot; simply because you&#039;ve decided to do it.
c) Depending on your skills, some things are easier than others. For example, I&#039;d rather fix a computer than cook something. My girlfriend is the other way around.

Also note that something that has just a little bit of friction will seem very painful if you have to repeat it 20 times a day.

How this relates to the post - Low friction methods can be learned and implemented at a lightening pace, overcoming perceived time savings from more complex systems.</description>
		<content:encoded><![CDATA[<p>Good post Alik. I&#8217;ve also been adopting J.D. s methods, though I&#8217;m in my infancy. It&#8217;s clarified some of these methods further.</p>
<p>I&#8217;m the artist type who&#8217;s been looking for a method that helps me be flexbile while still making more effective. I&#8217;ve used a number of different types of planners from other people and those that I&#8217;ve made up myself.</p>
<p>The irony is that I&#8217;m anal-retentive in many ways. I&#8217;ve worked at organizing content for the last 10 years. Personally, I&#8217;ve moved all my bills and things online and have over 10,000 pages scanned into the computer to get rid of my information clutter.</p>
<p>During this time I&#8217;ve found two things that are relevant to this post.<br />
1) that it&#8217;s easy to get lost in the inflexibility of a system. The simpler you can keep it, the more portable it is to other tools.  The benefits of a simple system like J.Ds is that it&#8217;s highly portable to other mail products (not just outlook).</p>
<p>2) J.D. concept of friction. The more friction you have in any area, the harder it is to overcome it, just like in physics.  Friction is equal to<br />
   perceived difficulty of the task<br />
        x<br />
   the number of times you need to perform it in a given time period</p>
<p>Note the &#8220;perceived&#8221; part.<br />
a) This may be high at the start, but it gets easier as patterns become automatic.<br />
b) The perception is partially controlled by how easy it is to try a different method. For example, on the web, everything is a click away. If you have to travel someplace to start something, there may be as much friction to leave and try something else as there is to just complete the task where you are. The task in front of you can seem &#8220;easier&#8221; simply because you&#8217;ve decided to do it.<br />
c) Depending on your skills, some things are easier than others. For example, I&#8217;d rather fix a computer than cook something. My girlfriend is the other way around.</p>
<p>Also note that something that has just a little bit of friction will seem very painful if you have to repeat it 20 times a day.</p>
<p>How this relates to the post &#8211; Low friction methods can be learned and implemented at a lightening pace, overcoming perceived time savings from more complex systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alik</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4070</link>
		<dc:creator>Alik</dc:creator>
		<pubDate>Thu, 31 Jan 2008 20:31:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4070</guid>
		<description>@JD – Yeah! Life by test-driven design. Model, test, fail, fix, succeed. Iteratively. :)!!
@Kelvin – There is such technique in software too. It has proven to be not very scalable, meaning when there are too many flags raised the system  gets choked locking resources without releasing it. Imagine, you work on something – you are locked on it. Suddenly the flag raised, you need to complete another task – what do you do? Drop what you are doing and switch to the incoming task? That is bad algorithm. You get burned out on context switches – one of performance killers in software too. You may lose the state of the former task, and find yourself doing the same task once more.  Are you unlimited on resources like time or energy for doing same thing twice? Better technique is job scheduling – you know or anticipate what should come into your pipeline and you allocate resources, time and energy, proactively. If you do not know what’s to come in – you model, allocating time buffers for such cases.
@Ryan! Great to hear you liked it. Fantastic distillation of the key points!! You should read JD’s latest post - The Zen of Results - he uses quote from Bruce Lee that sounds very similar to what you’ve said &quot;Absorb what is useful, reject what is useless, add what is specifically your own.”. It is here http://blogs.msdn.com/jmeier/archive/2008/01/30/the-zen-of-results.aspx

Thanks for the feedback!!</description>
		<content:encoded><![CDATA[<p>@JD – Yeah! Life by test-driven design. Model, test, fail, fix, succeed. Iteratively. <img src='http://steve-olson.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> !!<br />
@Kelvin – There is such technique in software too. It has proven to be not very scalable, meaning when there are too many flags raised the system  gets choked locking resources without releasing it. Imagine, you work on something – you are locked on it. Suddenly the flag raised, you need to complete another task – what do you do? Drop what you are doing and switch to the incoming task? That is bad algorithm. You get burned out on context switches – one of performance killers in software too. You may lose the state of the former task, and find yourself doing the same task once more.  Are you unlimited on resources like time or energy for doing same thing twice? Better technique is job scheduling – you know or anticipate what should come into your pipeline and you allocate resources, time and energy, proactively. If you do not know what’s to come in – you model, allocating time buffers for such cases.<br />
@Ryan! Great to hear you liked it. Fantastic distillation of the key points!! You should read JD’s latest post &#8211; The Zen of Results &#8211; he uses quote from Bruce Lee that sounds very similar to what you’ve said &#8220;Absorb what is useful, reject what is useless, add what is specifically your own.”. It is here <a href="http://blogs.msdn.com/jmeier/archive/2008/01/30/the-zen-of-results.aspx" rel="nofollow">http://blogs.msdn.com/jmeier/archive/2008/01/30/the-zen-of-results.aspx</a></p>
<p>Thanks for the feedback!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan@ProspectingLIFE</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4069</link>
		<dc:creator>Ryan@ProspectingLIFE</dc:creator>
		<pubDate>Thu, 31 Jan 2008 10:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4069</guid>
		<description>Great perspective from an engineer&#039;s point of view! Key points I learn from this article is to streamline processes and the removal of whatever that is unneccesary from your life!</description>
		<content:encoded><![CDATA[<p>Great perspective from an engineer&#8217;s point of view! Key points I learn from this article is to streamline processes and the removal of whatever that is unneccesary from your life!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelvin</title>
		<link>http://steve-olson.com/how-to-engineer-yourself-for-peak-performance/comment-page-1/#comment-4068</link>
		<dc:creator>Kelvin</dc:creator>
		<pubDate>Thu, 31 Jan 2008 01:20:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.steve-olson.com/how-to-engineer-yourself-for-peak-performance/#comment-4068</guid>
		<description>Interesting!

I&#039;ve thought about a system that has the notions of interrupts. These are the most high priority things that you just jump to whenever a flag is raised. They are so important that you always handle them before you go back to what you were originally doing.</description>
		<content:encoded><![CDATA[<p>Interesting!</p>
<p>I&#8217;ve thought about a system that has the notions of interrupts. These are the most high priority things that you just jump to whenever a flag is raised. They are so important that you always handle them before you go back to what you were originally doing.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
