Skip to content

Instantly share code, notes, and snippets.

I may be slow to respond.

Eunsoo Park (Evan) esevan

I may be slow to respond.
View GitHub Profile
AruniRC / ms_coco_classnames.txt
Created Mar 5, 2018
Class Names of MS-COCO classes in order of Detectron dict
View ms_coco_classnames.txt
{0: u'__background__',
1: u'person',
2: u'bicycle',
3: u'car',
4: u'motorcycle',
5: u'airplane',
6: u'bus',
7: u'train',
8: u'truck',
9: u'boat',
itaysk / prepull.yaml
Last active Sep 21, 2022
Kubernetes: Pre-pull images into node (moved to: )
View prepull.yaml
# There's a newer version available here:
# All future updates will be made there.
# Please also post you questions as issues on that repo instead of commenting here
apiVersion: apps/v1beta2
kind: DaemonSet
jashmenn /
Last active Sep 6, 2022
Javascript var self = this; vs. .bind

The Problem

In Javascript this is bound in unexpected ways. Functions, in particular, create a new 'this' and so when you want to keep a reference to an "outer" object you sometimes see the pattern:

var self = this;

as in:

var self = this;
mikepea /
Last active Dec 5, 2022
Pull Request Etiquette

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.