I am a native russian speaker, open source contributor and I am keen on administrating, scripting, creating sites and presentations. It’s my life. I like to automate routine tasks and not to do them manually. Currently I have the following skills (just the most interesting tools are mentioned and some of their usages are explained):

• 💻 programming, markup and configuration languages:
  • Fish: automating tasks for developed tools
  • TinyScheme: extending GIMP
  • Go: developing CLI, TUI and GUI applications
  • JavaScript: developing VS Code extensions and Web Apps
  • YAML & JSON: configuration languages for Go applications
  • Markdown: explaining developed tools
• 📝 ides and editors:
  • Visual Studio Code: programming, writing tool explanations and configurations
  • GIMP & Inkscape: drawing images for developed tools
  • OnlyOffice: creating presentations about English and German
• 🕜 vcs-tools:
  • Git & GitHub: managing tool development

I support several projects and organizations such as (just the most interesting ones are mentioned):

But now I mainly focused on [C]ommand [L]ine [I]nterface [P]ages project:

which provides neat command help pages.

Starting from 21 August 2024 I use the following placeholder syntax in all my tools (Go-inspired):

• {{placeholder}}: some arbitrary text with no constraints implied which should be exactly one CLI argument.
• {{placeholder ...}}: almost the same thing as the previous one, but here zero or more arguments are expected.
• | can be used inside double curly braces to provide more than one alternative for what can be placed instead of placeholder.

, where instead of placeholder any text can be written which explains what should be put instead of CLI argument(s), but without spaces unless it's explicitly permitted. This syntax is used just when no other default syntax is mandated.

Examples:

command {{number}} # 1 number expected
command {{number..}} # 0 or more numbers expected
command {{number|strings...}} # one number or 0 or more string expected