Valeriy Manenkov char16t

So you’d like to contribute to Clojure, great! Let’s talk about what that involves.

The first thing you’ll want to make sure is that your idea is valid, and that you won’t spend a ton of time working on something that won’t make into master. To do this, you should create a JIRA ticket. For example, let’s say we want to improve how core.async handles channel closing propagation. It’s not a super complex problem, but there are some design questions about which of the various semantics currently in place should be the default, and if some semantics should be configurable.

So start by making a JIRA ticket and stating what the problem is you’re trying to solve, what the possible options for solving the problem. Now hit save and wait for the ticket to be triaged. Alex Miller will take a look when he can, and that can take a few days to a few weeks, depending on the time of the year (he has other responsibilities). Alex may out-right reject the idea if he knows Rich would never approve the ticket, but otherwise h

Nginx production configuration sample

This config assumes that nginx is run from docker image _/nginx.

docker commands

docker network create nginx

mkdir -p /etc/myproject/nginx

cd /etc/myproject/nginx

These links no longer work. Springer have pulled the free plug.

Graduate texts in mathematics

duplicates = multiple editions

A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen

Я когда делаю Code Review критерии следующие:

Безопасность:
- Каждый аргумент метода простого типа должен проверяться на тип в случае его проксирования и на граничные значения в случае обработки. Чуть что не так - бросается исключение. Если метод с кучкой аргументов на 80% состоит из поверки из аргументов - это вполне норм))
- Никаких trigger_error, только исключения.
- Исключения ДОЛЖНЫ быть человеко-понятны, всякие "Something went wrong" можно отдавать пользователю, но в лог должно попасть исключение со стектрейсом и человеко-понятным описанием, что же там пошло не так.
- Каждый аргумент (объект) метода должен быть с тайпхинтингом на этот его класс, или интерфейс.
- За eval как правило шлю на **й.
- @ допускается только в безвыходных ситуациях, например проверка json_last_error.

Перед работой с БД - обязательная проверка данных.

	---
	- name: Install docker
	gather_facts: No
	hosts: default

	tasks:
	- name: Install yum utils
	yum:
	name: yum-utils
	state: latest

	<ol class="breadcrumb">
	{% set crumbs = [] %}
	{% set current = {'crumb': this} %}
	{% for i in this._path.split("/") %}
	{% if current.crumb is not none %}
	{% if crumbs.insert(0, current.crumb) %}{% endif %}
	{% if current.update({"crumb": current.crumb.parent}) %}{% endif %}
	{% endif %}
	{% endfor %}
	{% for crumb in crumbs %}

	(require '[instaparse.core :as insta])

	(def org-parse
	(insta/parser
	"<DOC> = <EOL>* heading*
	heading = level <SPC> [status <SPC>] text tag* [<EOL> content]
	sub-heading = sub-level <SPC> [status <SPC>] text tag* [<EOL> content]
	EOL = '\n' \| '\r\n' \| #'$'
	SPC = ' '
	level = #'\\*+'

	# Add the following 'help' target to your Makefile
	# And add help text after each target name starting with '\#\#'

	help: ## Show this help.
	@fgrep -h "##" $(MAKEFILE_LIST) \| fgrep -v fgrep \| sed -e 's/\\$$//' \| sed -e 's/##//'

	# Everything below is an example

	target00: ## This message will show up when typing 'make help'
	@echo does nothing

	/*
	Simple WINDOWS keylogger by jkrix 2013.
	User may distribute and modify source code but MUST keep this top commented section in the source code!

	Very important note:

	To be used for educational use and not for malicious tasks!
	I will NOT be held responsible for anything silly you may do with this!
	*/
	#include <stdio.h>

	git branch -m old_branch new_branch # Rename branch locally
	git push origin :old_branch # Delete the old branch
	git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote