Kir Belevich deepsweet

Kinesis Freestyle (Terrible key switches. Mushy and un-lovable)
Kinesis Freestyle Edge (Traditional layout with too many keys, mech switches, proably too big to be tented easily/properly)
Matias Ergo Pro (Looks pretty great. Have not tried.)
ErgoDox Kit (Currently, my everyday keyboard. Can buy pre-assembled on eBay.)
ErgoDox EZ (Prolly the best option for most people.)

Use yarn with Greenkeeper

When using yarn, it will create a yarn.lock lockfile which holds data on your used dependencies. This file also includes hard-typed versions, so should you update your dependencies, the yarn.lock file is basically outdated and needs to be regenerated. While yarn does this automatically, Greenkeeper pull requests that update dependencies as of right now do not do this regeneration, which means you would have to do it manually.

This gist shows you a way how to automatise this step using a Travis CI script.

Prerequisites

You use Travis CI and have it build Pull Requests (default behaviour)
You have a yarn.lock file in your repository for Travis CI to automatically install yarn (yarn will be added to their default images soon)

Getting started

Edit — February 2019

This gist had a far larger impact than I imagined it would, and apparently people are still finding it, so a quick update:

TC39 is currently moving forward with a slightly different version of TLA, referred to as 'variant B', in which a module with TLA doesn't block sibling execution. This vastly reduces the danger of parallelizable work happening in serial and thereby delaying startup, which was the concern that motivated me to write this gist
In the wild, we're seeing (async main(){...}()) as a substitute for TLA. This completely eliminates the blocking problem (yay!) but it's less powerful, and harder to statically analyse (boo). In other words the lack of TLA is causing real problems
Therefore, a version of TLA that solves the original issue is a valuable addition to the language, and I'm in full support of the current proposal, which you can read here.

I'll leave the rest of this document unedited, for archaeological

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
Create or import a key -- see below for https://keybase.io
Run gpg --list-secret-keys and look for sec, use the key ID for the next step
Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

brew install gnupg, pinentry-mac (this includes gpg-agent and pinentry)
Generate a key: $ gpg --gen-key
Take the defaults. Whatevs
Tell gpg-agent to use pinentry-mac:
```
$ vim ~/.gnupg/gpg-agent.conf 
```

https://telegram.me/zavtracast Официальный канал Завтракаста - подкаста об играх, медиа, технологиях

https://telegram.me/webstandards_ru Ежедневные новости фронтенда от «Веб-стандартов»

https://telegram.me/addmeto филиал addmeto.сс на земле

https://telegram.me/techsparks Аннотированные ссылки на интересные, полезные и удивительные новости хайтека (ведет @asebrant)

https://telegram.me/globchan Новостной канал о мире, науке и технологиях

Atom Clojure Setup

This describes how I setup Atom for an ideal Clojure development workflow. This fixes indentation on newlines, handles parentheses, etc. The keybinding settings for enter (in keymap.cson) are important to get proper newlines with indentation at the right level. There are other helpers in init.coffee and keymap.cson that are useful for cutting, copying, pasting, deleting, and indenting Lisp expressions.

Install Atom

Download Atom

The Atom documentation is excellent. It's highly worth reading the flight manual.

	# Replace [YOUR_DOMAIN_NAME] by your real domain

	server.modules += ( "mod_setenv" ) # For HSTS

	$SERVER["socket"] == "0.0.0.0:443" {
	ssl.engine = "enable"

	ssl.pemfile = "/etc/letsencrypt/live/[YOUR_DOMAIN_NAME]/combined.pem"
	ssl.ca-file = "/etc/letsencrypt/live/[YOUR_DOMAIN_NAME]/fullchain.pem"
	ssl.dh-file = "/etc/ssl/certs/dhparam.pem"

	<div
	tabIndex="0"
	ref={onRef}
	onBlur={onWrapperBlur}
	>

	// ...

	withHandlers(() => {
	let element = null;

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else