From: Craig Maloney Date: Tue, 13 Nov 2018 13:12:12 +0000 (-0500) Subject: Added a section on renegotiating agreements X-Git-Tag: 0.5.0^2~14 X-Git-Url: https://jxself.org/git/?a=commitdiff_plain;h=654e36dce78c3d9e7033ca3894dc6078b9963266;p=themediocreprogrammer.git Added a section on renegotiating agreements --- diff --git a/chapter07.md b/chapter07.md index 7d9cffc..a5c6832 100644 --- a/chapter07.md +++ b/chapter07.md @@ -106,9 +106,13 @@ There are some things we can do to understand and help alleviate burnout: By understanding that we're headed toward burnout (or are burned-out already) we can take measures to course-correct so we can approach our programming practice with joy and enthusiasm. Sometimes taking a step back and re-evaluating what we're doing can help us not sit in the constant loops of frustration, anger, and guilt. Changing our story to better fit reality can keep us from trying to match an impossible dream. -### FIXME (Talk a bit about how to re-negotiate commitments) +I mentioned above about re-negotiating commitments. Often we'll get ourselves into situations where we have way more to do than is physically possible, even under the best of circumstances. This may be in part because we've said "yes" to too many things, or may be because we're being swamped with outside work commitments (a large high priority project, or several smaller projects that need urgent attention). The best way to renegotiate your work load is to review your work load and notice which ones feel more urgent and which ones feel important. Note which ones fall into those two categories. Next mark the due date (as best you can) of each of these tasks. If you have more than three urgent and important items and they're due later this week then it's likely you're being overworked and will want to renegotiate those commitments. You may think that you should be able to do all of these things but if you're already feeling stressed, tired, and burned out then you'll only compound those feeling by trying to meet these deadlines. If you can see if you can move some of these deadlines to next week, or check with your customers if these are really as urgent and important as you think they are. If they are then see if your management can assist you with other resources, or intervene to renegotiate these deadlines and priorities. If you're truly stuck (management won't budge and the customers are firm with this commitment) then you have some decisions to make about how important their priorities are versus your own capabilities. There's the temptation to say that your management and your customer's priorities are more important but your own health and well-being should have more weight in your decision than their priorities and deadlines. Perhaps you can negotiate some down-time after this period so you can rest, relax, and regain your strength and mental acuity before being plunged into a similar situation. -You will experience burnout in your programming career. Things will come at you that will overwhelm your ability to cope with them. You will find yourself stuck in loops wondering if this is really what you should be doing. Understanding what you're feeling and acknowledging your feelings as valid is the first step to changing the course from one of burnout and stress. Programming shouldn't be drudgery (no work should be drudgery). There should be something in your programming day that keeps you motivated, and helps you grow your skills. Adding bits of learning, joy and wonder (along with periods of downtime) will help sustain you through the emotional turbulence that awaits. +It's also cliche to say "learn to say no", but this is an important skill as a programmer. Too often we think of ourselves as super-beings that can do anything because the computer can do anything. But we have finite physical and emotional resources, so learning to pick and choose the projects that are most important to us (depending on our own internal criteria) will help sustain us as we progress in our programming career. If we say "yes" to everything that is pitched to us then we'll have less time to work on the things that really matter to us. We'll be at the whims of external folks whose priorities and desires may not match our own. The most effective way to burn-out on programming is to spend all of your energy working on projects that don't match your own desires and priorities. + +You will experience periods of burnout in your programming career. Things will come at you that will overwhelm your ability to cope with them. You will find yourself stuck in loops wondering if this is really what you should be doing. Understanding what you're feeling and acknowledging your feelings as valid is the first step to changing the course from one of burnout and stress. Programming shouldn't be drudgery (no work should be drudgery). There should be something in your programming day that keeps you motivated, and helps you grow your skills. Adding bits of learning, joy, and wonder (along with periods of downtime) will help sustain you through the emotional turbulence that awaits. And recognizing when you're burning out and renegotiating your agreements with yourself and others can help reinvigorate your desires to keep programming. + +### FIXME ## Giving up