sudo scientist | devoops | cloud naive
Unix/Linux/Infrastructure geek, author of Shell Scripting Tutorial (http://shellscript.sh) & Book (http://amzn.to/2s1kGN2).
he/him
| Personal | https://steve-parker.org |
| Shell Tutorial | https://shellscript.sh |
| joke_label_1 | sudo scientist |
| joke_label_2 | cloud naive |
There is a principle[1] that talking to a "rubber duck" can help in debugging a problem. It is a theory that I subscribe to, and many other IT people do too. The idea is that you talk to the rubber duck and in explaining the problem, it helps you to understand the problem and come to a solution, even if no other expertise is available to you.
But even a rubber duck is no use if you keep putting off the problem, so I have decided I need to up the ante: My rubber duck has been upgraded with a label so that it reminds me that it does need me to address the problem itself!
In this case, it's a Nagios issue for a project called "p4lm" but I am sharing this expansion to the Rubber Duck methodology to the world, in the hope that we can extend Rubber Duck debugging into Rubber Duck Nagging!
Kept the same username, moved to BlueSky, will still check in here as sporadically as I have before!
I've just realised why Microsoft called their operating system "Windows"
- because it's such a pane!
