env command allows to find a script’s interpreter when its location is a non-standard one. In scripts it’s recommended to use env in shebang lines to find the executable and run it.

#!/usr/bin/env ruby

puts "Hello, world."

On GNU/Linux if it’s necessary to run a script’s interpreter with options, env has to be used with -S to pass options in shebang lines.

extends attribute in Docker Compose files allows to reuse existing service definitions for other services. That makes it possible to DRY Compose files.

Recently I had an interesting conversation with colleagues on the topic of writing tests for code. In particular, it was about tests for hotfixes that need to be deployed as soon as possible. In this post, I’ll leave the results of that conversation aside and focus on what it inspired me to think about. On the question “Why do I write tests for code?”

A week ago my friend Pablo and me released the very first episode of Code && Beyond. None of us had any experience in podcasting or ever worked with voice and audio. But we did that!