getify

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.

erikras

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.

calebporzio

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;

cmrigney

// 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();

kitze

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

iamandrewluca

• 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/

bgauduch

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:

srstsavage

# send logs for all traffic (including non-html) to google analytics
#
# in server block:
#  set $google_analytics_id "UA-THECORRECT-ID";
#  include            /srv/nginx/google_analytics;
#
# in location blocks:
#  post_action @ga;
#
# notes: post_action has been referred to by nginx devs as a "dirty hack" and this approach may stop working one day.

rauschma

This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays

helhum

{
    "require": {
        "typo3-console/composer-auto-setup": "^0.1",
        "georgringer/news": "^6.1",
        "helhum/typo3-secure-web": "^0.2.5",
        "typo3/cms-introduction": "^3.0"
    },
    "extra": {
        "typo3/cms": {
            "cms-package-dir": "{$vendor-dir}/typo3/cms",