Lukasz Strzalkowski lukaszx0

Obviously, the simplest solution would be for the client to share their account details or add us as ‘team admin’, but that is not what this is about.

On https://developer.apple.com

[Add us to your iOS Developer Program as ‘team member’.][1]
[Create a ‘Distribution Certificate’, if you haven’t got one already.][2]
[Create a ‘App Store Distribution Provisioning Profile’.][3]
[Export the ‘Distribution Certificate’ assets and send the export and password to us.][4] (For security sake, it’s a good idea to send us the password via other means than the exported certificate. E.g. by phone/SMS.)

On https://itunesconnect.apple.com

A slightly updated version of this doc is here on my website.

Why I Like Go

I visited with PagerDuty yesterday for a little Friday beer and pizza. While there I got started talking about Go. I was asked by Alex, their CEO, why I liked it. Several other people have asked me the same question recently, so I figured it was worth posting.

Goroutines

The first 1/2 of Go's concurrency story. Lightweight, concurrent function execution. You can spawn tons of these if needed and the Go runtime multiplexes them onto the configured number of CPUs/Threads as needed. They start with a super small stack that can grow (and shrink) via dynamic allocation (and freeing). They are as simple as go f(x), where f() is a function.

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

Declared ETags, together with Russian Doll caching, can be used to automatically mix your template and asset versions into the ETags set in your controllers. This avoids the need to blow all browser caches on each deploy and neatly contains the scope of "freshness fallout" when you tweak a view.

To include the template's version in the ETag:

  # Incorporate the cache version for this action into our ETag.
  # This allows template changes to bubble up into HTTP cache
  # freshness and bust browser caches when we make changes.
  etag do
    begin

Since this is on Hacker News and reddit...

No, I don't distribute my résumé like this. A friend of mine made a joke about me being the kind of person who would do this, so I did (the link on that page was added later). My actual résumé is a good bit crazier.
I apologize for the use of _t in my types. I spend a lot of time at a level where I can do that; "reserved for system libraries? I am the system libraries".
Since people kept complaining, I've fixed the assignments of string literals to non-const char *s.
My use of type * name, however, is entirely intentional.
If you're using an older compiler, you might have trouble with the anonymous unions and the designated initializers - I think gcc 4.4 requires some extra braces to get them working together. Anything reasonably recent should work fine. Clang and gcc (newer than 4.4, at le

Original: http://www.shadowandy.net/2012/03/asus-rt-n66u-tomatousb-firmware-flashing-guide.htm

Download Asus RT-N66U Flash utility

http://support.asus.com/ServiceHome.aspx?SLanguage=en

Download Shibby RT-N66U firmware

http://tomato.groov.pl/download/K26RT-N/

	require 'connection_pool'
	require 'redis'
	require 'metriks'

	class RedisClientWrapper
	def initialize(options)
	@options = options.delete(:pool)
	@pool = ConnectionPool.new(@options) do
	::Redis.new(options)
	end

	#!/usr/bin/env bash
	#
	# Wraps curl with a custom-drawn progress bar. Use it just like curl:
	#
	# $ curl-progress -O http://example.com/file.tar.gz
	# $ curl-progress http://example.com/file.tar.gz > file.tar.gz
	#
	# All arguments to the program are passed directly to curl. Define your
	# custom progress bar in the `print_progress` function.
	#

	#! /usr/bin/env python
	from boto.ses.connection import SESConnection
	import os
	import sys
	import subprocess
	import socket

	TMPFILE = '/var/run/postgresql/last-wal-archive-error-file.tmp'

	if __name__ == '__main__':

	#!/bin/sh
	#
	# Usage: git semver-tags [-p\|--pre]
	#
	# Lists semver tags in the repository in order from newest to oldest.
	#
	# Useful for e.g. programmatically finding the latest release tag:
	# `git semver-tags \| head -n 1`.
	#
	# Tag names must be valid according to the SemVer 1.0.0 specification