Per Bering pbering

Don't use VPN services.

No, seriously, don't. You're probably reading this because you've asked what VPN service to use, and this is the answer.

Note: The content in this post does not apply to using VPN for their intended purpose; that is, as a virtual private (internal) network. It only applies to using it as a glorified proxy, which is what every third-party "VPN provider" does.

A Russian translation of this article can be found here, contributed by Timur Demin.
A Turkish translation can be found here, contributed by agyild.
There's also this article about VPN services, which is honestly better written (and has more cat pictures!) than my article.

Diagnosing Redis errors on the client side

Content moved

The content from this GIST has been moved to official Azure Cache for Redis Documentation. The new location is https://docs.microsoft.com/azure/azure-cache-for-redis/cache-troubleshoot-client

Please update your bookmarks.

Diagnosing Redis errors on the server side

The content from this GIST has been moved to official Azure Cache for Redis Documentation. The new location is https://docs.microsoft.com/azure/azure-cache-for-redis/cache-how-to-troubleshoot#server-side-troubleshooting

Please update your bookmarks.

Deploy the VM and setup endpoint

In portal.azure.com, go to New -> Compute -> Marketplace and search for Windows Server Container Preview.
Make sure the TCP 2375 endpoint is open in Azure (Settings -> Endpoint)

Enable Docker daemon networking

Access the VM via RDP
Edit C:\ProgramData\Docker\runDockerDaemon.cmd, and add -H 0.0.0.0:2375 on line 11, in the docker daemon invocation inside the run target
Enable docker.exe in the firewall: netsh advfirewall firewall add rule name="Allow Docker" dir=in action=allow program="C:\windows\system32\docker.exe"

a simple git branching model

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

The gist

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

Latency numbers every programmer should know

L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns             
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

	<?xml version="1.0" encoding="utf-8" ?>
	<!--

	Purpose: This include file simplifies the setup of Sitecore CD instances by removing any references to the Master database from Sitecore configuration files.

	This include file should be used only on CD servers.

	Important: Include files are applied in alphabetical order. Therefore this include file cannot remove any references to the Master database
	that are defined in include files that are applied later. In this situation, you must rename this include file so that it is applied after
	any other include files that contain references to "master" database.

	#REQUIRES -Version 3.0

	# This is a simple sample for access the MS UIAutomation in PowerShell.
	# In this sample:
	# 1. Load the MS UIA via System.Reflection.Assembly
	# 2. Launch the AUT ( calc.exe )
	# 3. Find the AutomationElement via the AUT Process Id
	# 4. Find buttons via 'ClassName' and 'Name' property
	# 5. Click the '1', '+', '1', '=' buttons.
	# At last, we will get '2' in the result of calc App.

	#!/bin/bash
	# cpustatus
	#
	# Prints the current state of the CPU like temperature, voltage and speed.
	# The temperature is reported in degrees Celsius (C) while
	# the CPU speed is calculated in megahertz (MHz).

	function convert_to_MHz {
	let value=$1/1000
	echo "$value"