Piyush Chauhan piyushchauhan2011

What Hiring Should Look Like

This is definitely not the first time I've written about this topic, but I haven't written formally about it in quite awhile. So I want to revisit why I think technical-position interviewing is so poorly designed, and lay out what I think would be a better process.

I'm just one guy, with a bunch of strong opinions and a bunch of flaws. So take these suggestions with a grain of salt. I'm sure there's a lot of talented, passionate folks with other thoughts, and some are probably a lot more interesting and useful than my own.

But at the same time, I hope you'll set aside the assumptions and status quo of how interviewing is always done. Just because you were hired a certain way, and even if you liked it, doesn't mean that it's a good interview process to repeat.

If you're happy with the way technical interviewing currently works at your company, fine. Just stop, don't read any further. I'm not going to spend any effort trying to convince you otherwise.

Variables by Secrets

Sample script that allows you to define as environment variables the name of the docker secret that contains the secret value. It will be in charge of analyze all the environment variables searching for the placeholder to substitute the variable value by the secret.

Usage

You can define the next environment variables:

Migrations & Seeding

What are migrations??

Migrations are a way to make database changes or updates, like creating or dropping tables, as well as updating a table with new columns with constraints via generated scripts. We can build these scripts via the command line using knex command line tool.

To learn more about migrations, check out this article on the different types of database migrations!

	#!/usr/bin/env bash

	echo "Checking out master branch"
	git checkout master
	git pull origin master

	git log master..develop
	read -p "Review your changes..."

	echo "Merging develop branch"

	#!/usr/bin/env bash

	# Assuming you have a master and dev branch, and that you make new
	# release branches named as the version they correspond to, e.g. 1.0.3
	# Usage: ./release.sh 1.0.3

	# Get version argument and verify
	version=$1
	if [ -z "$version" ]; then
	echo "Please specify a version"

	#!/bin/bash

	# Merges the master branch into all other branches
	#
	# Process:
	#
	# - Save the name of the current branch
	# - If the current branch is not master then checkout master.
	# - Pull the latest changes for master from its upstream branch.
	# - Loop over each local branch.

	'use strict';
	const statusCodes = require('http').STATUS_CODES;

	function createError(code, name) {
	return function(message) {
	Error.captureStackTrace(this, this.constructor);
	this.name = name;
	this.message = message;
	this.statusCode = code;
	}

	// the main app file
	import express from "express";
	import loadDb from "./loadDb"; // dummy middleware to load db (sets request.db)
	import authenticate from "./authentication"; // middleware for doing authentication
	import permit from "./authorization"; // middleware for checking if user's role is permitted to make request

	const app = express(),
	api = express.Router();

	// first middleware will setup db connection

	# Note (November 2016):
	# This config is rather outdated and left here for historical reasons, please refer to prerender.io for the latest setup information
	# Serving static html to Googlebot is now considered bad practice as you should be using the escaped fragment crawling protocol

	server {
	listen 80;
	listen [::]:80;
	server_name yourserver.com;

	root /path/to/your/htdocs;

	{
	"presets": ["es2015"]
	}