Andrei L unrevised6419

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.

Directory structure

~/oss/redux-form – master branch of redux-form/redux-form
~/oss/rfdocs – master branch of redux-form/redux-form-docs
- This is auto deployed via Netlify to redux-form.com (or it was before I transfered ownership to the redux-form org)
- Contains publish.js, a horrible pre-Gatsby static site generator
~/oss/redux-form-website-template – website-template branch of redux-form/redux-form
- This is where styling tweaks sometimes need to be made
- It needs to be npm publish'd and the version updated in all the examples package.jsons and redux-form-docs repos to get the new changes.

Error Tracking https://sentry.io
Error Tracking https://logrocket.com
Localisation https://crowdin.com
Localisation https://poeditor.com
Auth https://auth0.com
Continuous Integration https://travis-ci.org/
E2E Testing https://www.cypress.io
Cross Browser Testing https://www.browserstack.com
Code Coverage https://codecov.io
Serverless https://zeit.co/

Setup multiple git identities & git user informations

/!\ Be very carrefull in your setup : any misconfiguration make all the git config to fail silently ! Go trought this guide step by step and it should be fine 😉

Setup multiple git ssh identities for git

Generate your SSH keys as per your git provider documentation.
Add each public SSH keys to your git providers acounts.
In your ~/.ssh/config, set each ssh key for each repository as in this exemple:

	import Analytics from 'analytics'
	import onRouteChange from '@analytics/router-utils'

	const persistPageViewsPlugin = {
	name: 'persist-page-data-plugin',
	page: ({ payload }) => {
	const { properties } = payload
	const pageView = {
	path: properties.path,
	title: properties.title,

	":" //#;exec /usr/bin/env node --input-type=module - $@<$0

	import process from 'process'

	const { argv } = process

	console.log(argv)

	(function bookmarksExportToCsv() {
	/**
	* 1. Export bookmarks from browser (supported any Chromium based browsers and Safari) (chrome://bookmarks)
	* 2. Open exported html file again in the browser
	* 3. Copy paste this entire file in console, and execute it (hit enter)
	* 4. You will be prompted to save a CSV file. Save it.
	* 5. Open Notion. Click Import -> CSV
	* 6. Select saved CSV file. Wait for import
	* 7. You have a new database with all your bookmarks
	*/

	details summary {
	cursor: pointer;
	outline: none !important;
	display: inline-block;
	padding: 8px 12px;
	padding-top: 10px;
	border-radius: 4px;
	overflow: hidden;
	background: #F09825;
	color: white;

	// Adapted code from https://github.com/flepretre/use-redux

	import { useContext, useState, useEffect, useCallback } from 'react';
	import { ReactReduxContext } from 'react-redux';
	import { bindActionCreators, ActionCreator } from 'redux';

	export function useRedux() {
	const { store } = useContext(ReactReduxContext);
	const { getState, dispatch, subscribe } = store;
	const reduxState = getState();

	import {
	formatDistance,
	isAfter,
	isBefore,
	endOfDay,
	startOfDay,
	isSameDay,
	isSameSecond,
	isSameMinute,
	isSameHour,