home.social

Search

4 results for “edthedev”

  1. This also led to a maybe new kind of parenting moment: I (gently, they are quite young) explained to my youngest that their power button pressing was what had prevented their older sibling from adding pizza to our shopping list a few minutes later.

    I'm curious whether my youngest loves pizza or pushing interesting buttons more. I'm sure I will find out.

    Of course, their sibling's laughter upon realizing what happened was probably the strongest factor, toward future behavior.

    If it gets to be a habit, I might have to disable that power button, after all.

  2. A Linux microblog update:

    My youngest child casually hit the power button on the front of one of my main server's today, with the confidence of someone who has probably done so a few times before.

    This sheds some light on some mysterious service gaps I've noticed recently.

    I fixed the situation by doing nothing. I'm a lazy enough DevOps that I knew one of my scheduled processes would automatically restore my key services soon enough.

    This reveals a couple insights into my home lab devops:

    1. I'm lazy enough that I build in substantial resilience.

    2. I'm unattentive enough that I really should improve my logging and alerts to include "your kid pressed the power button".

    And yes, I'm aware I could disable the button, but then I wouldn't get stories like this.

  3. Any Cybersecurity peers have thoughts on
    getvouchsafe.org ?

    This seems promising, and potentially important for architecture consideration, if I'm not missing some important flaw?

Share on Mastodon

Enter the server where you have an account.