| #! /usr/bin/env python | |
| import redis | |
| import random | |
| import pylibmc | |
| import sys | |
| r = redis.Redis(host = 'localhost', port = 6389) | |
| mc = pylibmc.Client(['localhost:11222']) |
| // This is from my comment here: http://wolfram.kriesing.de/blog/index.php/2008/javascript-remove-element-from-array/comment-page-2#comment-466561 | |
| /* | |
| * How to delete items from an Array in JavaScript, an exhaustive guide | |
| */ | |
| // DON'T use the delete operator, it leaves a hole in the array: | |
| var arr = [4, 5, 6]; | |
| delete arr[1]; // arr now: [4, undefined, 6] |
| var os = require("os"); | |
| //Create function to get CPU information | |
| function cpuAverage() { | |
| //Initialise sum of idle and time of cores and fetch CPU info | |
| var totalIdle = 0, totalTick = 0; | |
| var cpus = os.cpus(); | |
| //Loop through CPU cores |
| /* | |
| Check SSE/AVX support. | |
| This application can detect the instruction support of | |
| SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4a, SSE5, and AVX. | |
| */ | |
| #include <iostream> | |
| #ifdef _MSC_VER | |
| #include <intrin.h> | |
| #endif |
| // Async/Await requirements: Latest Chrome/FF browser or Babel: https://babeljs.io/docs/plugins/transform-async-to-generator/ | |
| // Fetch requirements: Latest Chrome/FF browser or Github fetch polyfill: https://github.com/github/fetch | |
| // async function | |
| async function fetchAsync () { | |
| // await response of fetch call | |
| let response = await fetch('https://api.github.com'); | |
| // only proceed once promise is resolved | |
| let data = await response.json(); | |
| // only proceed once second promise is resolved |
Disclaimer: This piece is written anonymously. The names of a few particular companies are mentioned, but as common examples only.
This is a short write-up on things that I wish I'd known and considered before joining a private company (aka startup, aka unicorn in some cases). I'm not trying to make the case that you should never join a private company, but the power imbalance between founder and employee is extreme, and that potential candidates would
| // Instructions: | |
| // npm install --save d3 jsdom | |
| const fs = require('fs'); | |
| const d3 = require('d3'); | |
| const jsdom = require('jsdom'); | |
| const { JSDOM } = jsdom; | |
| const fakeDom = new JSDOM('<!DOCTYPE html><html><body></body></html>'); |
| var Redis = require('ioredis'); | |
| var redis = new Redis({ | |
| host: "nodesydney.wiftycloud.com", | |
| password: "7884b8baaa49fbcb48f17ad2a146" | |
| }); | |
| async function main() { | |
| // write an event to stream 'events', setting 'key1' to 'value1' | |
| await redis.sendCommand( |
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
| 'use strict'; | |
| const puppeteer = require('puppeteer'); | |
| (async () => { | |
| /* PRECONDITION: | |
| 0. download ublock, I used https://github.com/gorhill/uBlock/releases/download/1.14.19b5/uBlock0.chromium.zip | |
| 1. run $PATH_TO_CHROME --user-data-dir=/some/empty/directory --load-extension=/location/of/ublock | |
| 2. enable block lists you want to use | |
| */ |
