- What problem do you solve and why would I give you money to solve it?
- When’s the last time someone went above and beyond the call of duty at the company/on the team? What did they do?
- What are the current goals that the company is focused on, and how does this team/role work to support hitting those goals?
- What are the projects in this company you think are really key to its future and how would a motivated person go about getting on them?
- What do you see as your largest technical challenge currently?
- Pain Points beyond headcount
- What is a project you wish a new member of the team could take on?
name: CI | |
# This workflow will purposely fail a check, then change that status to success. | |
# It will then approve and merge itself when a PR has been created. | |
# This is certainly not something you should usually do and I take no responsibility for how it's used. | |
# This is for informational purposes only. | |
on: | |
# Triggers the workflow on pull request events but only for the main branch | |
pull_request: |
# Copyright (C) 2018 Jameel Al-Aziz | |
# Modified for simplicification and use within CoreOS. | |
# | |
# Copyright (C) 2006-2016 Amazon.com, Inc. or its affiliates. | |
# All Rights Reserved. | |
# | |
# Licensed under the Apache License, Version 2.0 (the "License"). | |
# You may not use this file except in compliance with the License. | |
# A copy of the License is located at | |
# |
This gist will show how to setup Raspbian Stretch as a headless Bluetooth A2DP audio sink. This will allow your phone, laptop or other Bluetooth device to play audio wirelessly through a Rasperry Pi.
A quick search will turn up a plethora of tutorials on setting up A2DP on the Raspberry Pi. However, I felt this gist was necessary because this solution is:
- Automatic & Headless - Once setup, the system is entirely automatic. No user iteration is required to pair, connect or start playback. Therefore the Raspberry Pi can be run headless.
- Simple - This solution has few dependencies, readily available packages and minimal configuration.
- Up to date - As of December 2017. Written for Raspbian Stretch & Bluez 5.43
*update: TBC, but this new might affect how easy it is to use this technique past August 2024: Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August
This gist, based in part on a gist by Brian Hartvigsen, allows you to export from Authy your TOTP tokens you have stored there.
Those can be "standard" 6-digits / 30 secs tokens, or Authy's own version, the 7-digits / 10 secs tokens.
# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env | |
# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced | |
# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start | |
# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running. | |
# Add the following to your shell init to set up gpg-agent automatically for every shell | |
if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then | |
source ~/.gnupg/.gpg-agent-info | |
export GPG_AGENT_INFO | |
else |
Slack doesn't provide an easy way to extract custom emoji from a team. (Especially teams with thousands of custom emoji) This Gist walks you through a relatively simple approach to get your emoji out.
If you're an admin of your own team, you can get the list of emoji directly using this API: https://api.slack.com/methods/emoji.list. Once you have it, skip to Step 3
HOWEVER! This gist is intended for people who don't have admin access, nor access tokens for using that list.
Follow along...
input { | |
elasticsearch { | |
hosts => [ "HOSTNAME_HERE" ] | |
port => "9200" | |
index => "INDEXNAME_HERE" | |
size => 1000 | |
scroll => "5m" | |
docinfo => true | |
scan => true | |
} |
#A script to post back to Slack via the webhooks API
##why this exists?
Slack's own hubot adapter needs the hubot installation to be accessible via web. This can be problematic in some cases, as a security risk.
This hack let's you run your Hubot behind a firewall, and connect to Slack via the IRC gateway.
To respond, Hubot uses the incoming webhooks end-point of Slack.
#!/usr/bin/python | |
# Quick and dirty demonstration of CVE-2014-0160 by Jared Stafford (jspenguin@jspenguin.org) | |
# The author disclaims copyright to this source code. | |
import sys | |
import struct | |
import socket | |
import time | |
import select |