awalterschulze

all:
	make build
	make objdump

build:
	go build -gcflags -m main.go

objdump:
	go tool objdump -s "main.main" main | grep CALL

awalterschulze

.stack-work

awalterschulze

mybinary

awalterschulze

_build

awalterschulze

Table Name

❌ |	✅
File_name File_Name	FileName _File

awalterschulze

FROM cassandra:3.1.1

RUN mkdir -p /tmp/var/lib/cassandra /etc/cassandra \
	&& chown -R cassandra:cassandra /tmp/var/lib/cassandra /etc/cassandra \
	&& chmod 777 /tmp/var/lib/cassandra /etc/cassandra

RUN sed -i "s~/var/lib/cassandra~/tmp/var/lib/cassandra~g" /etc/cassandra/cassandra.yaml

COPY *.cql /tmp/

awalterschulze

FROM python:2.7.9-wheezy

RUN git clone https://github.com/shk3/edx-downloader
RUN (cd edx-downloader && pip install -r requirements.txt)
RUN pip install --upgrade youtube_dl

VOLUME /tmp/
WORKDIR /tmp/

ENTRYPOINT bash

awalterschulze

#!/bin/bash
# Delete all containers
docker rm $(docker ps -a -q)
# Delete all images
docker rmi $(docker images -q)

Reference: http://techoverflow.net/blog/2013/10/22/docker-remove-all-images-and-containers/

awalterschulze

package main

import (
	"encoding/base64"
	gojson "encoding/json"
	"fmt"
	"io"

	"github.com/katydid/katydid/parser"
	"github.com/katydid/katydid/parser/json"

awalterschulze

For Sum Types: Multiple return parameters are overrated

In this Go Experience Report I am going to make a case for sum types over multiple return parameters.

Analysis of multiple return parameters

I wrote a little tool which does some analysis of Go source code:

https://github.com/awalterschulze/goanalysis