Opinions are like assholes, every one has got one.
This one is mine.
Punctuation is a bikeshed. Put your semicolons, whitespace, and commas where you like them.
# 0 is too far from ` ;) | |
set -g base-index 1 | |
# Automatically set window title | |
set-window-option -g automatic-rename on | |
set-option -g set-titles on | |
#set -g default-terminal screen-256color | |
set -g status-keys vi | |
set -g history-limit 10000 |
I have moved this over to the Tech Interview Cheat Sheet Repo and has been expanded and even has code challenges you can run and practice against!
\
When times get tough and people get nasty, you’ll need more than a killer smile. You’ll need a killer contract.
Used by 1000s of designers and developers Clarify what’s expected on both sides Helps build great relationships between you and your clients Plain and simple, no legal jargon Customisable to suit your business Used on countless web projects since 2008
…………………………
Go to the egghead website, i.e. Building a React.js App
run
$.each($('h4 a'), function(index, video){
console.log(video.href);
});
This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays
In React's terminology, there are five core types that are important to distinguish:
React Elements
#!/usr/bin/env bash | |
set -u | |
set -e | |
export GIT_WORK_TREE="/var/www/example.com" | |
export NODE_VERSION="0.10" | |
echo "--> Checking out..." | |
git checkout -f |
### MARKHAM'S NOTES: | |
# This Makefile includes the Arduino core sources. (Set ARDDIR here:) | |
ARDDIR = /d/arduino | |
# You should build a tiny Makefile for each of your projects and just declare a few | |
# things in it, then include this Makefile in it. Your Makefile should be in the same | |
# directory as your TARGET file (see below). | |
# | |
# Exemplia gratia: |