athaller

Let's say you're using Ubuntu 13.04 (Raring Ringtail, released in April 2013) and it just went End-of-Life on you, because it's supported for only 6 months, and the deprecated packages are taken down after 12 months.

You'll probably figure this out the hard way. When you run sudo apt-get update, it will eventually report these errors:

Ign http://archive.ubuntu.com raring-updates/universe Sources/DiffIndex
Err http://security.ubuntu.com raring-security/main Sources
  404  Not Found [IP: 91.189.91.15 80]
Err http://security.ubuntu.com raring-security/universe Sources
  404  Not Found [IP: 91.189.91.15 80]

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

#System Design Interview Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

##Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Guide to install PyQt5 on Mac OS X with python 3.4 virtualenv

Description

A simple guide to install PyQt5 on Mac OS X 10.9 (Maverick) and use python 3.4 on a virtualenv.

Requirements

xcode 5.1.1
python 3.4.0
Qt libraries 5.2.1

	#!/bin/bash

	SENDGRID_API_KEY=""
	EMAIL_TO=""
	FROM_EMAIL=""
	FROM_NAME=""
	SUBJECT=""

	bodyHTML="<p>Email body goes here</p>"

	#!/bin/bash

	usage() {
	cat << EOF
	Usage: $0 [OPTION]... COMMAND
	Execute the given command in a way that works safely with cron. This should
	typically be used inside of a cron job definition like so:
	* * * * * $(which "$0") [OPTION]... COMMAND

	Arguments:

-#!/usr/bin/python
-# -*- coding: utf-8 -*-
-import sublime_plugin
-import subprocess
-from time import sleep
-import sys
-cl = lambda line: subprocess.Popen(line, shell=True, stdout=subprocess.PIPE).communicate()[0].strip()
-log = lambda message: sys.stderr.write("Log: %s\n" % message)

	#
	# For sites which prefer IPv4 connections change the last line to
	#
	precedence ::ffff:0:0/96 100

	<?php
	echo '{"Fn::Base64": {"Fn::Join": ["\n", ' . json_encode(file($argv[1], FILE_IGNORE_NEW_LINES), JSON_PRETTY_PRINT) . ']}}';

	#
	drush pml --no-core --type=module --status=enabled --pipe > modules.txt

	cat modules.txt \| xargs drush -y dis
	cat modules.txt \| xargs drush -y en