Cleaning up the intro of chapter 05

diff --git a/chapter05.md b/chapter05.md
index 8cb6468006e62caed055e7c1fc52259e3cde92da..aad9d0dbcf3c917a0071a2009a27db85577c83f2 100644 (file)
--- a/chapter05.md
+++ b/chapter05.md
@@ -8,11 +8,13 @@ We've heard the stories of developers waking up at their computers to the strang
 
 There's a tendency to think that because we work with machines that are tireless and ready for more work that we need to behave in the same way; we need to constantly utilize these resources. We try become like the machine; tireless and always ready for more work. 
 
-### FIXME
+There's a problem with always being "on". When we feel like we always have to be "on" we never let ourselves feel like we can be "off" again. We don't allow ourselves the time to be off. This creates a pattern where we deny ourselves the moments to sit and reflect on what we're doing.  We force ourselves to keep moving; keep programming no matter the personal cost. Our brains don't get the ability to rest, relax, and recharge. Our minds are too busy and exhausted to process what we've learned and sweep that knowledge into long-term storage. When we get exhausted we start to worry that we're not doing enough. This doesn't motivate us; instead we create a vicious feedback loop of fear and panic. We spend our day worrying that we're not doing enough while our minds cry out "enough!" from exhaustion. This feedback loop of fear and exhaustion can spiral us into a vortex of burnout, depression, and a desire to leave programming for good.
 
-There's a problem with always being "on". When we feel like we need to be "on" all the time we don't allow ourselves any time to feel like we can be "off". We create a pattern where we deny ourselves the moments to sit and reflect on what it is we're doing. We force ourselves to keep moving; keep programming no matter the personal cost. We don't allow our brains to relax and recharge. We don't let our minds process what we've learned and sweep that knowledge into long-term storage. Instead we create a vicious feedback loop of fear and panic. We spend our day worrying that we're not doing enough while our minds cry out from exhaustion. This feedback loop of fear and exhaustion can lead to burnout, depression, and a desire to leave programming for good.
+There's a delicate balance that we need to strike between our desires of being on all the time and our needs for relaxation and reflection. Our desires for invincible and indefatigable development need to be tempered with the reality that our bodies and minds have finite resources per day and must be allocated appropriately. Think of this as power-management for a complex machine that the manufacturer (currently) won't let you swap the battery out for a new one. Being aware what processes are running, how much energy is being used, and how much energy is left would be vital to ensuring you could still be running that machine later on in the day. That's the level of awareness that we'll need to have about ourselves.
 
-So how do we balance these feelings of wanting to be on all the time while allowing ourselves to relax and reflect on what we're doing?
+How do we balance these feelings of wanting to be on all the time while allowing ourselves to relax and reflect on what we're doing? How do we pay attention to the needs of this programming machine?
+
+#### FIXME
 
 ## Lights out