thuongdinh-agilityio

# tested on AWS p2.xlarge August 29, 2018

# install CUDA
sudo apt-get update && sudo apt-get install wget -y --no-install-recommends
CUDA_URL="https://developer.nvidia.com/compute/cuda/9.2/Prod2/local_installers/cuda-repo-ubuntu1604-9-2-local_9.2.148-1_amd64"
wget -c ${CUDA_URL} -O cuda.deb
sudo dpkg --install cuda.deb
sudo apt-key add /var/cuda-repo-9-2-local/7fa2af80.pub
sudo apt-get update
sudo apt-get install -y cuda

thuongdinh-agilityio

The Best of the Best Practices (BOBP) Guide for Python

A "Best of the Best Practices" (BOBP) guide to developing in Python.

In General

Values

• "Build tools for others that you want to be built for you." - Kenneth Reitz
• "Simplicity is alway better than functionality." - Pieter Hintjens

thuongdinh-agilityio

#!/bin/bash

# install CUDA Toolkit v9.0
# instructions from https://developer.nvidia.com/cuda-downloads (linux -> x86_64 -> Ubuntu -> 16.04 -> deb)
CUDA_REPO_PKG="cuda-repo-ubuntu1604-9-0-local_9.0.176-1_amd64-deb"
wget https://developer.nvidia.com/compute/cuda/9.0/Prod/local_installers/${CUDA_REPO_PKG}
sudo dpkg -i ${CUDA_REPO_PKG}
sudo apt-key adv --fetch-keys http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1604/x86_64/7fa2af80.pub
sudo apt-get update
sudo apt-get -y install cuda-9-0

thuongdinh-agilityio

var Nightmare = require('nightmare'),
    vo = require('vo');

function *start() {
    var nightmare = new Nightmare({
        show: true,
        'download-preferences': {
            destination: require('path').resolve(__dirname, 'downloads')
        }
    });

thuongdinh-agilityio

# This shows the setup for two services, an accounts service which connects to a database and a pagerduty service which connects to the pagerduty api
# Directory structure
accounts/
  |_ Dockerfile
pagerduty/
  |_ Dockerfile
nginx/
  |_ conf/
    |_ sites.conf
  |_ .htpasswd

thuongdinh-agilityio

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

thuongdinh-agilityio

The Case For Go

• Iron.io: How We Went from 30 Servers to 2 with Go
• Go at Google: Language Design in the Service of Software Engineering
• Behind the Scenes: Big Data at Torbit
• pool.ntp.org DNS server in Go
• Juju at Canonical
• Go at bitly
• NSQ: realtime distributed message processing at scale