olebedev

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

###Array ####Definition:

• Stores data elements based on an sequential, most commonly 0 based, index.
• Based on tuples from set theory.

olebedev

#!/usr/bin/env bash

# fresh-chrome
#
# Use this script on OS X to launch a new instance of Google Chrome
# with its own empty cache, cookies, and user configuration.
#
# The first time you run this script, it will launch a new Google
# Chrome instance with a permanent user-data directory, which you can
# customize below. Perform any initial setup you want to keep on every

olebedev

First, check your current config (example output in homebrew.mxcl.postgresql.plist.xml lower down in this gist):

cat ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

Most importantly, note the -D /usr/local/var/postgres argument.

Second, shut down your current PostgreSQL.

launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.postgresql.plist

olebedev

$ ffmpeg -i input.mp4 -vcodec h264 -acodec mp2 output.mp4

olebedev

Go, multiple packages and coveralls.io

Single profile for single Go package

For Go projects that consist of only one package, the following Travis configuration is enough to get started with coveralls.io. You may want to encrypt your $COVERALLS_TOKEN via Travis encryption keys though.

language: go
go:
 - 1.3.1

olebedev

### My publicly-auditable identity:

https://keybase.io/olebedev

### From the command line:

Consider the [keybase command line program](https://keybase.io/download).

```bash
# look me up

olebedev

Tools for building microservices architecture (May 7, 2016)

We are obviously in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages, GitHub and Docker uprise. In this world, Open Source usage dominates, and the speed of change is intense. Knowing the direction of DevOps tools and picking the right one for the project is crucial.

Terms

Continuous Integration is the practice of running your tests on a non-developer machine automatically everytime someone pushes new code into the source repository.

This has the tremendous advantage of always knowing if all tests work and getting fast feedback. The fast feedback is important so you always know right after you broke the build (introduced changes that made either the compile/build cycle or the tests fail) what you did that failed and how to revert it.

olebedev

//usr/bin/env go run $0 $@; exit

olebedev

XGETTEXT_FLAGS = --no-wrap --language=c --from-code=UTF-8 --output=- -
$(POT_FILE): $(TEMPLATES) $(filter-out $(BINDATA), $(GO_FILES))
	@cat $? \
		| grep -i gettext \
		| sed -e "s/ngettext \"\([^\"]*\)\".\"\([^\"]*\)\".\(.*\) }}/ngettext(\"\1\", \"\2\", \3) }}/g" \
		| sed -e "s/[^n]gettext \"\(.*\)\"/ gettext(\"\1\")/g" \
		| sed -e "s/NGetText(\([^\)]*\))/ ngettext(\1)  /g" \
		| sed -e "s/GetText(\([^\)]*\))/ gettext(\1)  /g" \
		| xgettext $(XGETTEXT_FLAGS) \
		| sed -e '1,20d' \

olebedev

deploy:
  steps:
    - add-to-known_hosts:
        hostname: $HOSTNAME
    - add-ssh-key:
        keyname: KEY
    - script:
        name: Push to dokku
        code: |
          git remote add dokku dokku@$HOSTNAME:$APP