Alexei Zaviruha AZaviruha

From: http://stackoverflow.com/questions/1676632/whats-a-quick-way-to-comment-uncomment-lines-in-vim

For those tasks I use most of the time block selection.

Put your cursor on the first # character, press Ctrl``V (or Ctrl``Q for gVim), and go down until the last commented line and press x, that will delete all the # characters vertically.

For commenting a block of text is almost the same: First, go to the first line you want to comment, press Ctrl``V, and select until the last line. Second, press Shift``I``#``Esc (then give it a second), and it will insert a # character on all selected lines. For the stripped-down version of vim shipped with debian/ubuntu by default, type : s/^/# in the second step instead.

LINGVA LATINA PER SE ILLVSTRATA

Что есть LLPSI?

Lingua Latina per se Illustrata (сокращенно LLPSI или иллюстрата) — это серия книг за авторством Ханса Эрберга (Hans Ørberg) — датского лингвиста-латиниста, посвятившего большую часть своей жизни обучению английскому, французскому и латинскому языкам.

Курс LLPSI состоит из нескольких книг, ядром которых являются Pars I: Familia Romana и Pars II: Roma Aeterna. В отличии от традиционного, т.н. грамматического подхода к изучению языка, Ханс использует натуральный метод — метод погружения. Обе книги написаны полностью на латинском языке. Повествование начинается с простых предложений, понятных любому носителю языка индоевропейской семьи:

type StringBool = "true"|"false";


interface AnyNumber { prev?: any, isZero: StringBool };
interface PositiveNumber { prev: any, isZero: "false" };

type IsZero<TNumber extends AnyNumber> = TNumber["isZero"];
type Next<TNumber extends AnyNumber> = { prev: TNumber, isZero: "false" };
type Prev<TNumber extends PositiveNumber> = TNumber["prev"];

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

Rich Hickey on becoming a better developer

Rich Hickey • 3 years ago

Sorry, I have to disagree with the entire premise here.

A wide variety of experiences might lead to well-roundedness, but not to greatness, nor even goodness. By constantly switching from one thing to another you are always reaching above your comfort zone, yes, but doing so by resetting your skill and knowledge level to zero.

Mastery comes from a combination of at least several of the following:

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

An introduction to curl using GitHub's API.

Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

Includes HTTP-Header information in the output

	pipeline {
	agent { node { label 'swarm-ci' } }

	environment {
	TEST_PREFIX = "test-IMAGE"
	TEST_IMAGE = "${env.TEST_PREFIX}:${env.BUILD_NUMBER}"
	TEST_CONTAINER = "${env.TEST_PREFIX}-${env.BUILD_NUMBER}"
	REGISTRY_ADDRESS = "my.registry.address.com"

	SLACK_CHANNEL = "#deployment-notifications"

	#%RAML 0.8

	title: World Music API
	baseUri: http://example.api.com/{version}
	version: v1
	schemas:
	- halLink: \|
	{ "$schema": "http://json-schema.org/schema",
	"type": "object",
	"description": "a Hypertext Application Language link",

	module Main exposing (..)

	import RemoteData exposing (WebData, RemoteData(..), asCmd, fromTask)
	import Html exposing (Html, text, div, input, br)
	import Html.Events exposing (onClick)
	import Html.Attributes exposing (type_, value)
	import Http exposing (get, toTask)
	import Json.Decode exposing (Decoder, string)
	import Json.Decode.Pipeline exposing (decode, required)
	import Random exposing (int, generate)