Google Chat messenger is the recommended way to contact me, while Bluesky to view my updates.
β Discord, Session and Signal are not actively used as they are blocked in Russia.
I am 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 toolsTinyScheme
(π¬
ποΈ
): extending GIMPGo
(π¬
β
): developing CLI, TUI and GUI applicationsJavaScript
(π¬
β
): developing VS Code extensions and Web AppsYAML
&JSON
(π¦
): configuration languages forGo
applicationsMarkdown
: explaining developed tools
- π ides and editors:
- π vcs-tools:
Git
&GitHub
: managing tool development
Legend:
π¬
: communityβ
: favorite toolsπ¦
: pull requestsποΈ
: personal scripts
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