Skip to content

Instantly share code, notes, and snippets.

Keybase proof

I hereby claim:

  • I am howinator on github.
  • I am howinator (https://keybase.io/howinator) on keybase.
  • I have a public key ASDqMM2eShQfk0erX_oz_QE8WBHx2HbTlCH5yTXM1xOPVwo

To claim this, I am signing this object:

@howinator
howinator / post-flood-shopping-list.md
Created August 29, 2017 18:17
Post-Flood Shopping List

If you can find these things

  1. Commercial demuhidifiers (if you're contractor doesn't have these things or if they do but they can't make it out immediately)
  2. Industrial blowers

Absolute needs

  1. Gloves
  2. Particulate masks
  3. Good heavy shoes
  4. Wheel barrow/moving equipment
  5. More trash bags than you think you need
@howinator
howinator / kush-flood-advice.md
Last active August 29, 2017 18:00
Flood advice for Kush

Administrative

So, there’s some administrative stuff that needs to happen while the water is still up. First administrative concern is get in touch with your parent's homeowner's insurance agency and either: a) file a flood claim if they have flood insurance or b) get a written denial of claim form from them. The denial of claim form will enable them to apply for FEMA aid. The next piece of admin work is going to be finding a contractor. I would contact these categories of people in the following order (pretty much ordered by likelihood of being screwed over): 1) a disaster clean up company, like ServPro. 2) contractors local to your community (ask friends, look in flyers, google for them). 3) contractors not local to your community and possible not local to Houston. Getting a contractor is probably going to be the hardest part, so y'all should double or triple thread this effort. If you find a contractor, but they can't start until next week, reserve them but keep on looking. Don't stop until you can find

@howinator
howinator / gist:83d8a0e7ba15eeb0a23a1600a7c3bf16
Last active February 4, 2017 14:53
sparkabowl-api-reference.md

Infrastructure/Data Flow

The process starts with a user making a request to the Echo. The Echo records the input and sends it to the Amazon Alexa service. The Alexa service process the recording and decomposes it to text. That text is then cross-referenced against a JSON document, found here to determine what the "intent" of the user is. The found intent is then sent with other metadata to an AWS service called Lambda. AWS Lambda can be black boxed to be thought of as just a piece of code, without any physical infrastructure, which takes input values and returns values.