Dmytro Borysovskyi dimabory

Each unit should have only limited knowledge about other units: only units "closely" related to the current unit.
Each unit should only talk to its friends; don't talk to strangers.
Only talk to your immediate friends.

https://www2.ccs.neu.edu/research/demeter/demeter-method/LawOfDemeter/paper-boy/demeter.pdf

More formally, the Law of Demeter for functions requires that a method m of an object O may only invoke the methods of the following kinds of objects:

O itself

Canary deployment

https://octopus.com/docs/deployment-patterns/canary-deployments
https://martinfowler.com/bliki/CanaryRelease.html

Canary deployments are a pattern for rolling out releases to a subset of users or servers. The idea is to first deploy the change to a small subset of servers, test it, and then roll the change out to the rest of the servers. The canary deployment serves as an early warning indicator with less impact on downtime: if the canary deployment fails, the rest of the servers aren't impacted.

The basic steps of a canary deployment are:

http://qualityisspeed.blogspot.com/2015/04/dependency-elimination-example-primitive-support.html

Primitive Support:

A primitive type (int, string, etc) representing a domain concept (megabytes, phone number, etc).
A helper class that does something meaningful with that primitive (e.g. MegabyteConverter or PhoneNumberParser or FooHelper).

A Simple Example: E-mail Address Validation

public class UserSignup

Architectural Styles and the Design of Network-based Software Architectures https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf

	http://wiki.c2.com/?AlanKaysDefinitionOfObjectOriented

	1. Everything Is An Object.
	2. Objects communicate by sending and receiving messages (in terms of objects).
	3. Objects have their own memory (in terms of objects).
	4. Every object is an instance of a class (which must be an object).
	5. The class holds the shared behavior for its instances (in the form of objects in a program list)
	6. To eval a program list, control is passed to the first object and the remainder is treated as its message.

	This definition is derived from early versions of Smalltalk (Smalltalk-72?), and rules 5 and 6 clearly show Smalltalk's Lisp heritage. Kay remarked as such, noting that rules 4-6 would mutate as Smalltalk developed.

	console.log('script start')

	const interval = setInterval(() => {
	console.log('setInterval')
	}, 0)

	setTimeout(() => {
	console.log('setTimeout 1')
	Promise.resolve().then(() => {
	console.log('promise 3')

	// 1. add props

	const user = { id: 100, name: 'Howard Moon'} // { id: 100, name: 'Howard Moon' }
	const userWithPass = { ...user, password: 'Password!' } // { id: 100, name: 'Howard Moon', password: 'Password!'

	// 2. merge obj

	const part1 = { id: 100, name: 'Howard Moon' }
	const part2 = { id: 100, password: 'Password!' }

	#!/usr/bin/env bash
	# Script Name: eslint-migration.sh
	#
	# Author: Dmytro Borysovskyi ([email protected])
	# Date : 25.08.2019
	#
	# Description: The following script tries to automatically (partially)
	# migrate TSLint to ESLint.
	#
	VERSION=1.2.0

	const palindrome = str =>
	(s = str.toLowerCase().replace(/[\W_]/g, '')) &&
	s === [...s].reverse().join('')