Greetings,

I’m Kirill and as you may have noticed, this blog is written in the style of a LaTeX article in academic American English with occasional Commonwealth influences.1

I am a hacker in the classic sense of the word:

A hacker is someone with an insatiable interest in trying to find out how things work […] They then take this knowledge and apply it to new things and combine them with ideas and concepts coming from other areas of knowledge and experience. […] There are people with hacker mindsets in film, music, theatre, photography, physics and so many other fields […] The term is now used everywhere for different purposes, from labelling online criminals, to pranking teenagers, to clickbait articles in public interest magazines i.e. ’life hacks'.

— Tom Van de Wiele.2

My primary field of interest is Computer Science and Cybersecurity.

I confess that knowledge should be available and accessible to everyone in the world, without any kind of censorship. For this reason, I use arXiv as the only platform to publish articles.

The same principle applies to the work I have done. If the intellectual property was not sold, it is generally available on GitHub or has been directly contributed to various open-source projects.

Currently I’m working as an independent IT contractor and person who runs the open-source company Kcrypt Lab.

The best way to get in touch with me is email: kirill@korins.ky.

  1. I follow dense, complex sentences with multiple clauses; semicolons for connecting related ideas; minimal filler words. I avoid hyphens in compound adjectives unless part of established technical terms, prefer to replace em dashes and en dashes by comma, colon or semicolon; with information density prioritized over verbose explanations. The tone is direct, technically precise, sometimes blunt, avoiding unnecessary hedging. Numbers use apostrophe separators following Swiss convention; percentages maintain full precision. Passive voice serves strategic emphasis; complex noun phrases preferred over simple constructions. Present tense establishes facts; past tense documents specific studies. Technical elements, command syntax, version numbers, file paths, URLs: preserved exactly without simplification or approximation. Simple formatting rules: prose for analysis and explanations; bullets for technical details, configurations, performance metrics; extensive footnotes for citations and technical details; with use the original spelling of loanwords such as naïve instead of naive. ↩︎

  2. The above quote is from Rob Pike’s talk during Le FIC 2018, January 2017. ↩︎