adragomir

; supermacros.asm
;   High-level constructs for NASM
;   v0.5.0 - 01.05.2014

; Take note that these macros are written in CamelCase. This is to distinguish
;then from assembly instructions, which are typically written all in one case.

; Functions ===================================================================

; Begin a function, or rather, the variable declaration part. Functions are

adragomir

# IN AMAZON EC2 SERVER #
########################
sudo su
apt-get -y update && apt-get -y upgrade
apt-get install vim git-core curl openssh-server openssh-client python-software-properties build-essential zlib1g-dev libssl-dev libreadline-gplv2-dev libcurl4-openssl-dev aptitude

/usr/sbin/groupadd wheel
/usr/sbin/visudo
    (paste bottom)
    %wheel  ALL=(ALL)       ALL

adragomir

# OSX for Hackers (Mavericks/Yosemite)
#
# Source: https://gist.github.com/brandonb927/3195465

#!/bin/sh

# Some things taken from here
# https://github.com/mathiasbynens/dotfiles/blob/master/.osx

# Ask for the administrator password upfront

adragomir

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns                     on recent CPU
L2 cache reference ........................... 7 ns                     14x L1 cache
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns                     20x L2 cache, 200x L1 cache
Compress 1K bytes with Zippy ............. 3,000 ns  =   3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns  =  20 µs
SSD random read ........................ 150,000 ns  = 150 µs

Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs 4X memory

adragomir

{
  "AWSTemplateFormatVersion" : "2010-09-09",

  "Description" : "Creates networking infrastructure.",

  "Parameters" : {

    "BastionKeyName" : {
      "Description" : "Name of an existing EC2 KeyPair to enable SSH access to the bastion host",
      "Type" : "String",

adragomir

#!/bin/bash

# get the absolute path of the executable
SELF_PATH=$(cd -P -- "$(dirname -- "$0")" && pwd -P) && SELF_PATH=$SELF_PATH/$(basename -- "$0")

# resolve symlinks
while [ -h $SELF_PATH ]; do
	# 1) cd to directory of the symlink
	# 2) cd to the directory of where the symlink points
	# 3) get the pwd

adragomir

//Projection Matrix
        mat4x4 mP = perspective_matrix(45.0, 1, 0.1, 100);
        //Translation
        mat4x4 mT = mat4x4::translation(float3(0, 0, -14));
        //Rotation
        mat4x4 mR = rotation_matrix_degrees(Rotation, float3(0, 1, 0));
        //View matrix
        mat4x4 mV = lookat_matrix(float3(0.0, 0.0, -3.0), float3(0, 0, -3), float3(0, 1, 0));
        mV = transpose(mV);
        //WorldViewProjection

adragomir

// My investigations on the C standard compliance of Gob and related techniques:
// https://gist.github.com/pervognsen/5249a405fe7d76ded1cf08ed50fa9176

#pragma once

#include <stdint.h>

#pragma pack(push, 8)

#if __cplusplus >= 201103L || (__cplusplus && _MSC_VER >= 1900)

adragomir

#include <stdlib.h>
#include <stdio.h>
#include <assert.h>
#include <string.h>
#include <windows.h>

typedef struct {
    char *start;
    char *current;
    char *end;

adragomir

A lot of these are outright stolen from Edward O'Campo-Gooding's list of questions. I really like his list.

I'm having some trouble paring this down to a manageable list of questions -- I realistically want to know all of these things before starting to work at a company, but it's a lot to ask all at once. My current game plan is to pick 6 before an interview and ask those.

I'd love comments and suggestions about any of these.

I've found questions like "do you have smart people? Can I learn a lot at your company?" to be basically totally useless -- everybody will say "yeah, definitely!" and it's hard to learn anything from them. So I'm trying to make all of these questions pretty concrete -- if a team doesn't have an issue tracker, they don't have an issue tracker.

I'm also mostly not asking about principles, but the way things are -- not "do you think code review is important?", but "Does all code get reviewed?".