diff options
Diffstat (limited to 'gemfeed')
| -rw-r--r-- | gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi | 12 | ||||
| -rw-r--r-- | gemfeed/atom.xml | 10 |
2 files changed, 11 insertions, 11 deletions
diff --git a/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi b/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi index ed0c2d66..daa86720 100644 --- a/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi +++ b/gemfeed/2021-12-23-how-to-stay-sane-in-the-world-of-devops.draft.gmi @@ -41,7 +41,7 @@ Due to politeness, many people are afraid to set clear expectations. I personall There are many temptations to get side-tracked by other projects and/or issues. It is important to set boundaries here. However, always answer to all requests as nothing is more frustrating than asking a person and never to get any answer back. This is especially frustrating when everyone is working form home and people are using tools such as Slack and E-Mail for 90% of their communications. Here, set clear expectations again. -If the request is urgent and you have the capacity, help. If it's not urgent, maybe ask to create a ticket. If it is urgent but you don't have the knowledge or the capacity to help, try to deffer the request to one of your teammates. You could also pride some quick tips and hints, so that the requester can resolve the issue by himself. Depending on the urgency, you may also ask the person to come back a few hours later. Also, make it transparent to the requester why you might not have the time now as this can help the person to review his own priorities or to escalate. +If the request is urgent and you have the capacity, help. If it's not urgent, maybe ask to create a ticket. If it is urgent but you don't have the knowledge or the capacity to help, try to deffer the request to one of your teammates. You could also provide some quick tips and hints, so that the requester can resolve the issue by himself. Depending on the urgency, you may also ask the person to come back a few hours later. Also, make it transparent to the requester why you might not have the time now as this can help the person to review his own priorities or to escalate. Sidenote on escalation: Never make it personally. The only forms of escalation should be due to technical issues or lack of work resources. An escalation then becomes like a math equation and does not need human resources involved. So per-se, an escalation is nothing negative but just a process people can follow to help decision making. @@ -69,16 +69,16 @@ If you are a super hero, try to give away some of your super powers, so that you So you are not a super hero. Or, if you are a super hero, then all colleagues are super heroes too. -## Force breaks; - - -## Shutdown routine - +## Force breaks; and shutdown now ## Time for personal advance Time blocking +* Work on an interesting project +* Learn a new technology your company plans to use +* Work on your personal goals you set with your manager + ## Think positively If times are very stressful, think that it could be worse: diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml index 9591828e..215144a3 100644 --- a/gemfeed/atom.xml +++ b/gemfeed/atom.xml @@ -1,6 +1,6 @@ <?xml version="1.0" encoding="utf-8"?> <feed xmlns="http://www.w3.org/2005/Atom"> - <updated>2021-12-01T09:12:31+00:00</updated> + <updated>2021-12-18T12:42:24+00:00</updated> <title>buetow.org feed</title> <subtitle>Having fun with computers!</subtitle> <link href="gemini://buetow.org/gemfeed/atom.xml" rel="self" /> @@ -330,10 +330,10 @@ bash: 1: command not found... <p>For these kinds of expressions it's always better to use "let" though. And you should also use $((...expression...)) instead of the old (deprecated) way $[ ...expression... ] like this example demonstrates:</p> <pre> ❯ declare j=0 -❯ let i=$((j + 1)) -❯ let i=$((j + 1)) -❯ let i=$((j + 1)) -❯ let i=$((j + 1)) +❯ let j=$((j + 1)) +❯ let j=$((j + 1)) +❯ let j=$((j + 1)) +❯ let j=$((j + 1)) ❯ echo $j 4 </pre> |