Skip to content

Instantly share code, notes, and snippets.

Nick Volynkin NickVolynkin

Block or report user

Report or block NickVolynkin

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
lananovikova10 /
Last active Sep 18, 2019
Notes from Highload++ 2018

Управление знаниями по принципам DevOps

Управление знаниями

Управлять знаниями = Идентифицировать артефакты знания - логировать критические знания и навыки, фасилитировать обмен и находить узкие места

Зачем (с точки зрения проектных команд)?

  1. Risk-management
  2. Онбординг новичков и ротация
  3. Профессиональный рост внутри команды, компании
  4. Формирование культуры - прозрачность
lananovikova10 /
Last active May 14, 2020
additional materials from teamlead conf

Тут живут драконы. Матрица навыков как инструмент тимлида

Другие варианты матриц для команд разработки

mjang / imposterTW.txt
Last active Mar 20, 2018
Imposter Syndrome for Documentarians
View imposterTW.txt
Discussion from WtD Slack
Bear with me, documentarians. I’ve a big thought to share, and I want to use separate paragraphs/entries so that people can respond to points separately. (Vs. me just dumping five paragraphs into one Slack message.)
I’ve been troubled by several aspects of a seemingly prevalent _imposter syndrome_ among a lot of documentarians. Well, more among the technical writers among us documentarians. And although I considered posting to the #career-advice channel, (or the meetpus channel becasue this is the subject of an upcoming presentation), I chose the #watercooler for a bigger audience.
While I’m certainly not advocating that anyone exaggerate their knowledge or deliberately mislead others into thinking we’ve more abilities than we do, it seems that the catchy phrase _imposter syndrome_ contributes to too many people short-changing themselves in discussions with others. And, very importantly, it contributes to the lack of respect for tech writers that we all rightly complain about.
View blog.rst

Documentation Engine Demo

This is a demo of how our documentation engine to see the real Paw docs go to Paw Docs

.. bc::
    :noindex: true

    * Paw Docs Engine demo
cube-drone /
Last active Mar 8, 2020
Automation For The People

Automation for the People

Long ago, the first time I read "The Pragmatic Programmer", I read some advice that really stuck with me.

"Don't Use Manual Procedures".

This in the chapter on Ubiquitous Automation. To summarize, they want you to automate all the things.

The trouble was that I hadn't much of an idea how to actually go

jericson /
Last active Jul 26, 2016
Moderator Vacation feature requests


  • Add date/reason for absence to the mod page instead of being in the title attribute.
  • Network vacations for mods with more than one site.
  • Send notifications to community@ automatically.
  • Status on meta should inherit from main.


  • Begin and end dates for pre-planned absenses. [Unfortunately, because of the way moderator vacation was been implemented, this was not easy this time around.]
vidavidorra /
Last active Apr 18, 2020
Auto-deploying Doxygen documentation to gh-pages with Travis CI

Auto-deploying Doxygen documentation to gh-pages with Travis CI

This explains how to setup for GitHub projects which automatically generates Doxygen code documentation and publishes the documentation to the gh-pages branch using Travis CI. This way only the source files need to be pushed to GitHub and the gh-pages branch is automatically updated with the generated Doxygen documentation.

Sign up for Travis CI and add your project

Get an account at Travis CI. Turn on Travis for your repository in question, using the Travis control panel.

Create a clean gh-pages branch

To create a clean gh-pages branch, with no commit history, from the master branch enter the code below in the Git Shell. This will create a gh-pages branch with one file, the in it. It doesn't really matter what file is uploaded in it since it will be overwritten when the automatically generated documentation is published to th

cube-drone /
Created Jan 20, 2016
Leading the Transformation

Also the words "IT Revolution" are on the front of the book, so if you don't read carefully you might end up holed up with a bunch of guns in a remote wildlife sanctuary.


The advice in this book was very successful at HP and Macy’s, two lumbering tech giants who are still relevant in this day and age, dammit.

Chapter 1

View gist:ac95178fe5a0cd5d7206
###[Q] Форматирование
Чтобы отформатировать код, выделите его мышью и нажмите на кнопку {} редактора.
###[Q] Работа за автора
Согласно правилам форума, вопросы не должны сводиться к решению либо завершению учебных заданий за учащихся. Пожалуйста, уточните, что вы сделали сами и что не получилось.
###[Q] Примите ответ
Если вам дан исчерпывающий ответ, отметьте его как верный (нажмите на галку рядом с выбранным ответом).
###[Q] Всеобъемлющий вопрос

Note: this is a summary of different git workflows putting together to a small git bible. references are in between the text

How to Branch

try to keep your hacking out of the master and create feature branches. the [feature-branch workflow][4] is a good median between noobs (i have no idea how to branch) and git veterans (let's do some rocket sience with git branches!). everybody get the idea!

Basic usage examples

You can’t perform that action at this time.