Helping to hire designers with

Started a little (well, maybe not exactly that little, given that it wasn’t as quick as I’ve thought) project with my friends to aid the designer positions candidate pre-interview screening through several simple challenges, akin to what hackerrank, codility etc. do for software developers – for now serves only a landing page, but we will hopefully publish more functionality soon-ish.

Tech-wise it’s been (and it still is) a good exercise on Node.js + Express + Vue.js + Typescript stack, which I was only vaguely familiar with before, and also on using cloud providers like Heroku to deploy and host everything (well, not exactly everything, as images need to be hosted on S3 or some other storage provider). Quite a lot of knowledge gain, but quite a lot of fun too!

Copying shell commands from websites

There are quite a few websites – like Homebrew, for instance – that offer initial installation in a form of shell script that downloads installation binary and runs it (or does some other actions like saving specific values to a configuration file). I always had some vague concern about copying and running commands, but then again, you could read those commands and judge for yourself if they’re malicious or not, right? Yes, but…

I stumbled upon an article today that highlighted how the copied code could be not what it seems – or rather, it’d replace copied text with something else:

It’s quite ingenious, really – it hooks onto copy event and it replaces clipboard data with another command, that’d even have a newline at the end so it’d launch after you paste it automatically. Here’s the code from the article:

document.getElementById('copyme').addEventListener('copy', function(e) {
        'echo "this could have been [curl | sh]"\n'

Now, you need to land on a frankly malicious website that’d do such a trick to you, but there also might be an XSS on an honest website that could utilise that. One way to safeguard yourself would be check your clipboard content (I use Alfred for OSX, it has an amazing feature of clipboard history), or paste the copied data in text editor or any non-shell text field to validate it’s what you expect it to be.

Live and learn!

[tech] Leadership Growth

A great article on what to focus (and avoid focusing) on when pursuing your career growth as a tech lead – or any leadership role, really:

I guess it could be put simpler into something like “find the spot where you could help the most, and do it” – but there are several additional (and quite important) points there, like avoiding chasing simple tasks, don’t try to just look good, adjust your perspective to new challenges, plan ahead etc. Well worth reading!

Workout sketches for fun!

I won’t add much text here, as these are mostly for my own reference and describing each would take quite some time, while hopefully images are explanatory enough.

I’d just say these exercises were collected from the additional materials for the “Training For The New Alpinism” book, some other training materials and personal experiments.

Radial Charts


I wanted to plot the data that is tightly connected to a time of a day as a circular chart, resembling the clock face – for no particular reason other than checking out how it looks.

Another thing I wanted to do was to play with some relatively modern JS framework.

And then I also got a bit a of a spare time on my hands.


So as a result, here’s a code that fetches CSV data from Graphite metrics (or any other CSV file) and displays it on a radial chart (aka Radar chart). It’s crude and unoptimised and inefficient, but it serves the goal of visual representation (see examples section below):

It’s mostly an amCharts showcase – amCharts are amazing, I love them dearly. Check them out if you’re not familiar, there’s seemingly nothing you can’t do with them:

Additionally, it also uses Github Actions ( as a CI mechanism – so on every push a build is pushed to a branch and then deployed as Github pages using (there’s many action plugins, this one was just the first one that worked).


Surprisingly, there’s npt that many public datasets with high-granularity daily data available on the Internet, but here’s at least one:
Bike rentals in NYC, January 1st 2020 vs July 1st 2019 (from

Bike rentals


  • it’s not a working tool or a developing project – it’s a fun thing built for no reason
  • it loads a ton of unnecessary libraries, becasue how amCharts library for Vue.js is structured, and also because it’s not optimised for anything
  • <many other things>

Mandelbrot set

I was always fascinated by the Mandelbrot set pictures and always wanted to create a representation myself, but never really got to do it – till a few days ago when I stumbled over an article boiling the code down to a very simple sequence ( – so I just took it and made parameters adjustable. Also used it as an exercise in Vue.js, as it was another thing I wanted to try but never did.

It’s a very-very crude solution, but it was a good exercise:

Also the code is here (well, it’s also in the html file, but FTR):

Permanently adding SSH private key to OSX keychain

It’s been bugging me for quite a while, but never enough to go and find a solution – until now.

Shamelessly re-posting a perfect guidance from

On OSX, the native ssh-add client has a special argument to save the private key’s passphrase in the OSX keychain, which means that your normal login will unlock it for use with ssh. On OSX Sierra and later, you also need to configure SSH to always use the keychain (see Step 2 below).

Alternatively you can use a key without a passphrase, but if you prefer the security that’s certainly acceptable with this workflow.

Step 1 – Store the key in the keychain

Just do this once:

ssh-add -K ~/.ssh/[your-private-key]

Enter your key passphrase, and you won’t be asked for it again.

(If you’re on a pre-Sierra version of OSX, you’re done, Step 2 is not required.)

Step 2 – Configure SSH to always use the keychain

It seems that OSX Sierra removed the convenient behavior of persisting your keys between logins, and the update to ssh no longer uses the keychain by default. Because of this, you will get prompted to enter the passphrase for a key after you upgrade, and again after each restart.

The solution is fairly simple, and is outlined in this github thread comment. Here’s how you set it up:

  1. Ensure you’ve completed Step 1 above to store the key in the keychain.
  2. If you haven’t already, create an ~/.ssh/config file. In other words, in the .ssh directory in your home dir, make a file called config.
  3. In that .ssh/config file, add the following lines:Host * UseKeychain yes AddKeysToAgent yes IdentityFile ~/.ssh/id_rsa Change ~/.ssh/id_rsa to the actual filename of your private key. If you have other private keys in your ~.ssh directory, also add an IdentityFile line for each of them. For example, I have one additional line that reads IdentityFile ~/.ssh/id_ed25519 for a 2nd private key.The UseKeychain yes is the key part, which tells SSH to look in your OSX keychain for the key passphrase.
  4. That’s it! Next time you load any ssh connection, it will try the private keys you’ve specified, and it will look for their passphrase in the OSX keychain. No passphrase typing required.

Web server in OSX (Apache2, dammit!)

There’s an Apache2 in OSX!!!

Apache2! It’s been awhile since I touched httpd.conf… so many memories… ūüėČ

It’s all described in this tutorial:¬†

It’s dead simple – see/edit¬†/etc/apache2/httpd.conf to find or set DirectoryRoot (mind directory access rights) and run “sudo apachectl start” (stop, restart).

To enable user websites, add following to etc/apache2/users/USERNAME.conf :

<Directory "/Users/USERNAME/Sites/">
Options Indexes Multiviews
AllowOverride AuthConfig Limit
Order allow,deny
Allow from all

and then it’d be served as¬†

Also, generating self-signed certificates:

And adding them to OSX keychain:

And you’d need to put them into¬†/private/etc/apache2/ssl/ and (potentially) edit¬†/private/etc/apache2/extra/httpd-ssl.conf and enable (uncomment)

Include /private/etc/apache2/extra/httpd-ssl.conf


LoadModule ssl_module libexec/apache2/

in /etc/apache2/httpd.conf

and run “apachectl restart” as root.

Champagne for all!

/   \
||  |
||  |    .    ' .
|'--|  '     \~~~/
'-=-' \~~~/   \_/
       \_/     Y
        Y     _|_