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 skills mentioned below (just the most interesting tools are mentioned and some of their usages are explained).

• 🛠️ Developing CLI, TUI and GUI applications, automating tasks for developed tools:

  • Go (💬 ⭐)
  • Fish (💬 ⭐ 📦)

  🔥 Frequently used.

• 🛠️ Developing macros and libraries:

  • JavaScript (💬)
  • TinyScheme (💬 🖊️)
  • VBA (💬)

  ❌ Rarely used.

• 🛠️ Configuration languages for applications:

  • YAML
  • JSON (📦)

• 🛠️ Explaining developed tools:

  • Markdown

• 🛠️ Programming, writing tool explanations and configurations:

  • Visual Studio Code (💬)

• 🛠️ Drawing images for developed tools:

  • Inkscape (💬)
  • GIMP (💬)

• 🛠️ Creating presentations:

  • OnlyOffice (💬)
  • Google Slides (💬)
  • Microsoft PowerPoint (💬)

• 🛠️ Managing tool development:
  • Git
  • GitHub

• 💬: 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