(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
These are the Kickstarter Engineering and Data role definitions for both teams.
Following this guide will set up a local Elasticsearch with Kibana and Marvel using Homebrew and Homebrew Cask
If you already have Java installed on your system, skip steps Install Cask and Install Java
If you already have Java and Homebrew installed on your system, skip steps Prerequisites, start at Install Elasticsearch and Kibana after running $ brew update
$ ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"| # Monkey Patch Knapsack to merge reports instead of overwrite | |
| begin | |
| class Knapsack::Report | |
| alias_method :save_without_leading_existing_report, :save | |
| def save | |
| Knapsack::Presenter.existing_report = open | |
| save_without_leading_existing_report | |
| end | |
| end |
I recently had several days of extremely frustrating experiences with service workers. Here are a few things I've since learned which would have made my life much easier but which isn't particularly obvious from most of the blog posts and videos I've seen.
I'll add to this list over time – suggested additions welcome in the comments or via twitter.com/rich_harris.
Chrome 51 has some pretty wild behaviour related to console.log in service workers. Canary doesn't, and it has a load of really good service worker related stuff in devtools.
init.vim and settings.vim go under ~/.config/nvim Follow the installation instructions for https://github.com/junegunn/vim-plug and place plug.vim in ~/.config/nvim/autoload
| # Written by Dane Fetterman on 12/1/2016 | |
| # https://aws.amazon.com/blogs/compute/monitor-cluster-state-with-amazon-ecs-event-stream/ | |
| # Where they use a cloud watch event from ECS to notify a SNS topic. We're | |
| # sending a notification directly to slack instead | |
| import requests | |
| import json | |
| from boto3 import session, client |
| http://stackoverflow.com/questions/22667401/postgres-json-data-type-rails-query | |
| http://stackoverflow.com/questions/40702813/query-on-postgres-json-array-field-in-rails | |
| #payload: [{"kind"=>"person"}] | |
| Segment.where("payload @> ?", [{kind: "person"}].to_json) | |
| #data: {"interest"=>["music", "movies", "programming"]} | |
| Segment.where("data @> ?", {"interest": ["music", "movies", "programming"]}.to_json) | |
| Segment.where("data #>> '{interest, 1}' = 'movies' ") | |
| Segment.where("jsonb_array_length(data->'interest') > 1") |
| # .ebextensions/cache.config | |
| files: | |
| "/opt/elasticbeanstalk/hooks/appdeploy/pre/02a_set_cache.sh": | |
| mode: "000755" | |
| owner: root | |
| group: root | |
| content: | | |
| #!/bin/bash | |
| set -xe |