mflower

I was thinking about something pretty similar -- rather than just try to overload the server, make it more difficult for phisherpeople to figure out which data is legitimate.

Realistically, I don't think I'd do it though -- who knows what 0 days you are putting on your box when you connect to those sites.

Large drive on one machine in my house, every computer in my house backs up to there using Restic. I keep hourlies for 2 days, weeklies for 2 months, monthlies for a year, and one extra year.

I also back up to Backblaze B2 using Restic and do the same thing except no hourlies.

This threatens to be a pretty nice replacement for mosh/tmux/neovim. I’ve been using the insiders build and the only thing missing is better handling of flaky connections.

These are probably the 3 I find most useful:

Copies the directory of the current git dir into the clipboard.

    which pbcopy &> /dev/null
    if [[ $? -eq 0 ]]; then
        CLIPBOARD_COMMAND="pbcopy"
    fi
    which clip &> /dev/null
    if [[ $? -eq 0 ]]; then
        CLIPBOARD_COMMAND="clip"
    fi

    cpgitdir() {
        GIT_DIR=`git remote show -n origin | grep "Fetch URL" | sed -e "s/  Fetch URL: //"  | tr -d '\n'`
        echo "Copying git dir to clipboard: $GIT_DIR"
        echo $GIT_DIR | tr -d '\n' | $CLIPBOARD_COMMAND
    }

Allows you to split your .bash_profile into multiple .bash_profile files for clarity

    if [[ -d ~/.bash_profile.d ]]; then
        for file in `find ~/.bash_profile.d -type f`; do
            source $file
        done
    fi

Simple calculator

    calc () {
        bc -l <<< "$@"
    }

1. Tell me how you help to develop the careers of your direct reports. Have you helped someone get promoted? What was their level before they got promoted and how you helped them to succeed?

2. Tell me about the pipeline of an idea from inception to delivery. (Give them opportunities to talk about points where people interact. Your looking to see if they think the ideas of the people at or below your level in the org are important and heard.)

3. Ask them to explain something in their org that is similar to your companies in as much tech detail as possible. Try to gauge if they have taken the time to understand what the different components in their system are.