Here’s what I learned at Rustbelt Refresh 2019: “Next Steps with CSS Layout” with Rachel Andrew~!
You should have the following completed on your computer before the workshop:
- Have Node.js installed on your system. (Recommended: Use nvm.)
- Unfortunately, you'll need to be on Node 9.x or earlier. Dependencies are hard and one of the dependencies of one of our dependencies is set to not allow Node 10.x.
- Install
yarn
withbrew install yarn
.
- Create an AWS account. (This will require a valid credit card.)
- Install multi-factor authentication app (e.g. Authy, Google Authenticator, Duo).
- Install the AWS CLI. (
brew install awscli
should do the trick. Otherwise, you'll need Python and PIP, which you can install usingbrew install python
.)
import datetime as dt | |
from collections import OrderedDict | |
from glob import glob | |
from sys import argv | |
from PIL import Image | |
from PIL.ExifTags import TAGS, GPSTAGS | |
def get_exif_data(image): |
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.
Running a local server for testing purposes:
import sys | |
from PIL import Image | |
from PIL.ExifTags import TAGS, GPSTAGS | |
def get_exif_data(image): | |
"""Returns a dictionary from the exif data of an PIL Image item. Also converts the GPS Tags""" | |
exif_data = {} | |
info = image._getexif() | |
if info: |
The following books are ordered in descending order of Matthew's preference.
by Avinash K. Dixit
Recommended by Ted Neward. A different perspective and writing style from the other volumes listed.
“I am hard pressed to think of another book that can match the combination of practical insights and reading enjoyment.”—Steven Levitt
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real