Augustus Yuan augbog

Studying for a Tech Interview Sucks, so Here's a Cheat Sheet to Help

This list is meant to be a both a quick guide and reference for further research into these topics. It's basically a summary of that comp sci course you never took or forgot about, so there's no way it can cover everything in depth. It also will be available as a gist on Github for everyone to edit and add to.

Data Structure Basics

Array

Definition:

Stores data elements based on an sequential, most commonly 0 based, index.
Based on tuples from set theory.

First of all you need to be able to run MAMP in port 80. This is a "heat check" if you don't have any process jamming http ports. You can check it like this:

sudo lsof | grep LISTEN

If you do happen to have any process with something like this *:http (LISTEN), you are in trouble. Before with adventure check if it isn't MAMP itself (yeah, you should close that beforehand)

ps <pid of that process>

If you don't see MAMP, you are in good hands, I have just the thing for you:

Free O'Reilly books and convenient script to just download them.

Thanks /u/FallenAege/ and /u/ShPavel/ from this Reddit post

How to use:

Take the download.sh file and put it into a directory where you want the files to be saved.
cd into the directory and make sure that it has executable permissions (chmod +x download.sh should do it)
Run ./download.sh and wee there it goes. Also if you do not want all the files, just simply comment the ones you do not want.

Frontend Technical Interview Prep

EDIT: Well this has been linked now so just an FYI this is still TBD. Feel free to comment if you have suggestions for improvements. Also here is an unrolled Twitter thread of a lot of the tips I talk about on here.

I've been doing frontend for a while now and one thing that really gripes me is the interview. I think the breadth of knowledge of a "Frontend Engineer" has been so poorly defined that people really just expected you to know everything. Many companies have made this a hybrid role. The Web is massive and there are many MANY things to know. Some of these things are just facts that you learn and others are things you really have to understand.

Every time I interview, I go over the same stuff. I wanted to create a gist of the TL;DR things that would jog my memory and hopefully yours too.

Lots of these things are real things I've been asked that caught me off guard. It's nice to have something you ca

	# grunt-newer:
	# Check for newer @import .scss files example
	# See: https://github.com/tschaub/grunt-newer/issues/29

	newer: {
	options: {
	override: function(details, include) {
	if (details.task === 'sass') {
	checkForNewerImports(details.path, details.time, include);
	}

	#!/bin/bash
	cd ~/Pictures/wallpapers && curl https://www.reddit.com/r/wallpapers/ \| tr '"' '\n' \| grep imgur \| tee "$$.tmp" \| egrep 'http:\/\/i.imgur.com\/.*\.jpg' \| xargs wget -q -nc
	egrep '^http://imgur.com/a/' "$$.tmp" \| xargs -L1 ~/Pictures/wallpapers/imgur_album_download.sh
	rm "$$.tmp"

	# Credit /u/Molozonide
	# https://www.reddit.com/r/wallpapers/comments/138qi2

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
	Version 2, December 2004

	Copyright (C) 2011 YOUR_NAME_HERE <YOUR_URL_HERE>

	Everyone is permitted to copy and distribute verbatim or modified
	copies of this license document, and changing it is allowed as long
	as the name is changed.

	DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE

	#!/bin/bash

	echo 'Running Pax Tickets script...'
	while [ 1 ];
	do
	count=`curl -H 'Cache-Control: no-cache' -s "http://west.paxsite.com/registration?$[ (RANDOM % 18747214) + 1 ]" \| grep -c "showclix.com"`
	echo "http://west.paxsite.com/registration?$[ (RANDOM % 18747214) + 1 ]"
	if [ "$count" != "0" ]
	then
	echo "West PAX Site updated!"

	<div class="va">
	<div class="va__body">
	<div class="va__content">
	<h1>Hello, World!</h1>
	</div>
	</div>
	</div>

	<div id="hello1">Hello1</div>
	<div id="hello2">Hello2</div>
	<div id="hello3">Hello3</div>
	<div id="hello4">Hello4</div>
	<div id="hello5">Hello5</div>