Skip to content

Instantly share code, notes, and snippets.

# Your init script
#
# Atom will evaluate this file each time a new window is opened. It is run
# after packages are loaded/activated and after the previous editor state
# has been restored.
#
# An example hack to log to the console when each text editor is saved.
#
# atom.workspace.observeTextEditors (editor) ->
# editor.onDidSave ->

BaileyAI

Goal: More AI projects through to incubation

  • Intro to BaileyX
  • BaileyAI
  • Q&A

Intro to BaileyX

  • Hod shares screen and runs through deck

BaileyAI

@groeney
groeney / aws-missing-creds.txt
Created March 2, 2018 17:58
Terraform complains about missing AWS credentials
2018/03/02 09:57:14 [WARN] Invalid log level: "1". Defaulting to level: TRACE. Valid levels are: [TRACE DEBUG INFO WARN ERROR]
2018/03/02 09:57:14 [INFO] Terraform version: 0.11.2 a6008b8a48a749c7c167453b9cf55ffd572b9a5d
2018/03/02 09:57:14 [INFO] Go runtime version: go1.9.1
2018/03/02 09:57:14 [INFO] CLI args: []string{"/usr/local/bin/terraform", "plan"}
2018/03/02 09:57:14 [DEBUG] Attempting to open CLI config file: /Users/groeneveld_james/.terraformrc
2018/03/02 09:57:14 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2018/03/02 09:57:14 [INFO] CLI command args: []string{"plan"}
2018/03/02 09:57:14 [INFO] command: empty terraform config, returning nil
2018/03/02 09:57:14 [DEBUG] command: no data state file found for backend config
2018/03/02 09:57:14 [DEBUG] New state was assigned lineage "940c8c02-93ff-483a-8366-f9e732eb0822"
@groeney
groeney / aws-invalid-creds.txt
Created March 2, 2018 17:55
Terraform complaining about invalid AWS credentials
2018/03/02 09:53:33 [WARN] Invalid log level: "1". Defaulting to level: TRACE. Valid levels are: [TRACE DEBUG INFO WARN ERROR]
2018/03/02 09:53:33 [INFO] Terraform version: 0.11.2 a6008b8a48a749c7c167453b9cf55ffd572b9a5d
2018/03/02 09:53:33 [INFO] Go runtime version: go1.9.1
2018/03/02 09:53:33 [INFO] CLI args: []string{"/usr/local/bin/terraform", "plan"}
2018/03/02 09:53:33 [DEBUG] Attempting to open CLI config file: /Users/groeneveld_james/.terraformrc
2018/03/02 09:53:33 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.
2018/03/02 09:53:33 [INFO] CLI command args: []string{"plan"}
2018/03/02 09:53:33 [INFO] command: empty terraform config, returning nil
2018/03/02 09:53:33 [DEBUG] command: no data state file found for backend config
2018/03/02 09:53:33 [DEBUG] New state was assigned lineage "773854d1-beb5-4590-8016-0a6826ba4a87"
@groeney
groeney / keybase.md
Created September 30, 2017 00:15
Keybase github proof

Keybase proof

I hereby claim:

To claim this, I am signing this object:

@groeney
groeney / id-insights-non-technical.md
Last active December 7, 2018 05:24
iD Insights stack (non-technical)

iD Insights stack (non-technical)

Everyone derives "insights" on the iD team - PMs, Devs, QA, Design, DevOps and leaders alike. We have a two part system for insights; Google Analytics (GA) and a tailored ELK deployment -- Elasticsearch, Logstash and Kibana. Generally speaking Kibana is the interface you will become most familiar with in the ELK ecosystem and you should already be familiar with GA. GA and Kibana are broad stroke and fine stroke analytics tools respectively.

Telos: the fewest data to give us maximum insight into user and application behaviours.

Important note regarding this document: this document is maintained through a Google Drive <--> StackEdit sync/pairing. Please make edits at either one of these platforms. Do not edit the gist directly, by doing so you will effectively clone the document and you will lose those changes next time it is published from the source.

@groeney
groeney / id-insights-technical.md
Last active December 7, 2018 05:24
iD Insights stack (technical)

iD Insights stack (technical)

This will serve as a guide for making future technical enhancements to the iD insights stack (ELK and GA), covering general maintenance tasks and current stack architecture.

Important note regarding this document: this document is maintained through a Google Drive <--> StackEdit sync/pairing. Please make edits at either one of these platforms. Do not edit the gist directly. Doing so you will effectively fork the document from its source.

Source: https://drive.google.com/open?id=0B52VNRX_C7xPN0ZvZV9paHd1MmM