So Matt walks into a bar....

 There already is a book on " Cracking the Coding Interview ", but not one for how to not totally flunk it. This blog post assumes an interview for a job involving coding. Many server admin jobs, UI jobs, testing jobs, might not call for you to ever write a line of code. If you don't know it say so. I have never written a line of rust or so much as read a book about it. I know it is a programming language. I will not try to leverage that into solving a live programming puzzle in rust on a whiteboard. If you don't know, say so, don't bullshit. Better to preface it with, "I'm not sure but...." than to confidently bullshit as if no one will notice. The HR person might not notice, but techies will. And don't waste your breath on technobabble with the HR folk anyhow, even if it is actually true and coherent. HR wants to hear about successful past projects and happy customers, not the finers points of fdisk. Go read up on the common questions. They...

 The cycle time from changing a line of code to seeing if it worked in terraform coding is LONG. Like maybe as much as half an hour. You really want to detect problems early. This was developed on windows, where bash is a 2nd class citizen. I use git-bash which plays poorly with docker, so I had to do a few tricks. The file docker.sh  contains !/bin/bash # This version works on windows, specifically git-bash # If you you gitbash, to use tflint, etc docker version, you need this. (export MSYS_NO_PATHCONV=1; "docker.exe" "$@") Every time you use a new custom module or 3rd party module you need to run init again. terraform init If you don't specify --recursive, this will fail to reformat any code in subfolders terraform fmt --recursive Validate catches syntax errors and not much else. It is not very strict. terraform validate Tflint is somewhat more strict. Watch out, tflint doesn't check subfolders. At the moment, you have to run tflint on each subfolder as a ...