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
+### FIXME
-The problem when we feel we always need to be "on" is that we don't allow ourselves the time to be "off". We create a pattern where we don't allow ourselves the moments to sit and reflect on what it is we're doing. We don't allow our brains to recharge. We don't allow for our minds to sit with what we've learned and sweep that into our long-term storage.
-
-Instead we create a feeling of constant panic where we spend most of our time worrying that we're not doing enough while at the same time pushing our minds to exhaustion. It's a vicious feedback loop, and one that can lead to 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.
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?
projects / themediocreprogrammer.git / commitdiff