улик u-l-y

Customizing VS Code

I followed the instructions in this blog post Multiple Fonts: Alternative to Operator Mono in VSCode, but did not see any changes made to VS Code. After digging a bit, I discovered that all the CSS class names had changed. They’re now e.g. .mtk13, .mtk16 { … }.

Gotchas

Ensure it’s a file URL e.g. { "vscode_custom_css.imports": [ "file:///Users/Brian/Desktop/vscode-style.css" ] }
If you move the location of your file and update your user settings with the new location, you will need to disable and enable custom CSS cmd+shift+p.
Also, anytime you change the style in your custom CSS file, you need to disable, then re-enable the extension.

For reference

vscode-styles for operator mono, fira code ligatures, and oceanic next italic · GitHub

Amazon Rekognition - Python Code Samples

Labels Detection
Faces Detection
Faces Comparison
Faces Indexing
Faces Search

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;

1. Install PHP7 with brew

brew install php70

2. Install Memcache from source on PHP7 branch

git clone -b NON_BLOCKING_IO_php7 https://github.com/websupport-sk/pecl-memcache.git
cd pecl-memcache
phpize
./configure
make &amp;&amp; make install

	#
	# Github Actions for Serverless Framework
	#
	# Create AWS_KEY and AWS_SECRET secrets in Github repository settings
	# If you're using env.yml file, store its content as ENV Github secret
	#
	# Master branch will be deployed as DEV and every new tag starting with "v**" (e.g. v1.0, v1.2, v2.0, etc) will be deployed as PROD
	#
	# Learn more: https://maxkostinevich.com/blog/how-to-deploy-serverless-applications-using-github-actions/
	#

	# Prompts for beginning new projects

	start:
	- "#5ps#"
	- "#heart#"
	- "#disirability_feasibility_viability#"
	- "#practical_step#"
	- "#build#"
	- "#story#"
	- "#ooda#"

	(function (context, trackingId, options) {
	const history = context.history;
	const doc = document;
	const nav = navigator \|\| {};
	const storage = localStorage;
	const encode = encodeURIComponent;
	const pushState = history.pushState;
	const typeException = 'exception';
	const generateId = () => Math.random().toString(36);
	const getId = () => {

	mkdir ~/vim
	cd ~/vim

	# Staically linked vim version compiled from https://github.com/ericpruitt/static-vim
	# Compiled on Jul 20 2017
	curl 'https://s3.amazonaws.com/bengoa/vim-static.tar.gz' \| tar -xz

	export VIMRUNTIME="$HOME/vim/runtime"
	export PATH="$HOME/vim:$PATH"
	cd -


	require('./module.js') // { a: 1 }
	import module from './module.js' // undefined
	import { a } from './module.js' // 1

	require('./module2.js') // { default: { a: 1 }, b: 2 }
	import module2 from './module2.js' // { a: 1}
	import { b } from './module2.js' // 2

	require('./module3.js') // { default: { a: 1 }, b: 2 }