Alexei Zaviruha AZaviruha

LINGVA LATINA PER SE ILLVSTRATA

Что есть LLPSI?

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

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

Rōma in Italiā est. Italia in Eurōpā est. Graecia in Eurōpā est. Italia et Graecia in Eurōpa sunt. Hispānia quoque in Eurōpā est.

You can use the tuple() function in tuple.ts to infer tuple types in TypeScript and cut down on the need to repeat yourself. Without tuple(), declaring a constant of a tuple type looks like this:

const daysOfTheWeek: ["sunday", "monday", "tuesday", "wednesday", "thursday", "friday", "saturday"] = 
  ["sunday", "monday", "tuesday", "wednesday", "thursday", "friday", "saturday"];

You can't do this:

const daysOfTheWeek = ["sunday", "monday", "tuesday", "wednesday", "thursday", "friday", "saturday"];

Async IO Programming

Design Pattern

Proactor
Proactor vs Reactor
The Reactor patterns involve synchronous I/O, whereas the Proactor pattern involves asynchronous I/O. In Reactor, the event demultiplexor waits for events that indicate when a file descriptor or socket is ready for a read or write operation. The demultiplexor passes this event to the appropriate handler, which is responsible for performing the actual read or write.
In the Proactor pattern, by contrast, the handler—or the event demultiplexor on behalf of the handler—initiates asynchronous read and write operations. The I/O operation itself is performed by the operating system (OS). The parameters passed to the OS include the addresses of user-defined data buffers from which the OS gets data to write, or to which the OS puts data read. The event demultiplexor waits for events t

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"];

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.

Recently CSS has got a lot of negativity. But I would like to defend it and show, that with good naming convention CSS works pretty well.

My 3 developers team has just developed React.js application with 7668 lines of CSS (and just 2 !important). During one year of development we had 0 issues with CSS. No refactoring typos, no style leaks, no performance problems, possibly, it is the most stable part of our application.

Here are main principles we use to write CSS for modern (IE11+) browsers:

SUIT CSS naming conventions + SUIT CSS design principles;
PostCSS + CSSNext. Future CSS syntax like variables, nesting, and autoprefixer are good enough;
Flexbox is awesome. No need for grid framework;
Normalize.css, base styles and variables are solid foundation for all components;

Reddit discussion.

Disclaimer 1: Type classes are great but they are not the right tool for every job. Enjoy some balance and balance to your balance.

Disclaimer 2: I should tidy this up but probably won’t.

Disclaimer 3: Yeah called it, better to be realistic.

Type classes are a language of their own, this is an attempt to document features and give a name to them.

	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"

	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)

	# Build image with Node.js, Elm and Nginx
	FROM debian:latest

	# prepare
	RUN apt-get -y update
	RUN apt-get -y install apt-utils

	# install curl, http://stackoverflow.com/questions/27273412/cannot-install-packages-inside-docker-ubuntu-image
	RUN apt-get -y install curl