DamonOehlman

Emoji guide:

• 👯 Supports co-op gameplay (my preference over PvP)
• 😵 Can get a bit addictive...
• 💵 Game has a payments system and they try and get money from you other than through the purchase price
• ⚙️ Can require a bit of a grind to be rewarding
• 🎫 Available on MS Xbox Game pass which I think is reasonable value...
• 💺 Best enjoyed in a couch co-op scenario

Shooters

DamonOehlman

Interesting articles

• https://www.reddit.com/r/linux_gaming/comments/2uvj4p/linuxgamingprotip_use_steamcmd_download_steam/

DamonOehlman

A collection of useful commands for dealing with various systems.

git

List all (local) branches and report date and sort in descending order:

git for-each-ref --sort=-committerdate refs/heads/ --format='%(committerdate:short) %(refname:short)'

DamonOehlman

The following is an "oh noes, where's my Internet" guide to surviving as a coder with no or limited Internet. Primarily the guide is focused on those who will be doing JS development (and using npm as a package manager) but some of the advice is useful for other environments also.

Step 1. Clone all things

Tooling in this steps require that you have git installed, and use github for your repositories.

One thing I really like to do when I get a bit of time offline, is clean up an old repository that I once thought was useful. I rarely know about what project this might be in advance. As a result, I like to clone all the things from my personal github account.

To do this I recommend using multirepo, which is best installed (at the moment) like so:

DamonOehlman

Useful information on the colours used in the Composited Layer Borders experiment (see chrome://flags/#composited-layer-borders) available at:

https://code.google.com/p/chromium/codesearch#chromium/src/cc/debug/debug_colors.cc&q=debug%20borders&sq=package:chromium&l=7

DamonOehlman

Death to Isomorphic JS

When exactly did we decide that we should substitute the term "code reuse" with isomorphism? I didn't get the memo...

All the Streams

So you've heard about streams huh? Yeah, the kind that makes producing, transforming and consuming data more portable. That's great. Did you know there are a few different kinds of streams, and it's not a one type will solve all your problems? No? Ah, well let me explain...

Don't control, react

DamonOehlman

This is an in-progress work that I should have started many moons ago.

Checking for Memory Leaks

• ssbc/ssb-server#82 (comment)

DamonOehlman

var COLORLIST = ['red', 'blue', 'yellow', 'green', 'pink'];
var h = require('hyperscript');

function toggler(value) {
  return function(evt) {
    var currentColor = evt.target.innerText;
    var currentIdx = COLORLIST.indexOf(currentColor);
    
    console.log(currentIdx + ' ^ ' + value + ' = ' + (currentIdx ^ value));
    evt.target.innerText = COLORLIST[currentIdx ^ value];

DamonOehlman

{
  "ignore": [
    "**/node_modules/**",
    "**/dist/**",
    "**/examples/**",
    "**/test/**",
    "**/Gruntfile.js",
    "**/gulpfile.js"
  ]
}

DamonOehlman

An nginx configuration that can be added to your /etc/nginx/sites-enabled directory to proxy from the local nginx server through to other servers running on other ports. Primarily this is useful when you want to view a site using HTTPS but don't want to associate the certificate with that local server.

The following proxys work:

http://localhost/ => http://localhost:9966/
https://localhost/ => http://localhost:9966/

https://localhost/<port>/ => http://localhost:<port>/
https://localhost// =&gt; http://localhost:/