Blake Niemyjski niemyjski

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

Basic Steps

Clarify and agree on the scope of the system

User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?

Exceptionless Contributor License Agreement

The document below clarifies the terms under which You (the copyright owner or legal entity authorized by the copyright owner), may make “The Contributions” (software, bug fixes, configuration changes, documentation, or any other materials) to “The Work” (Exceptionless/Exceptionless). This license protects You, “The Company” (Exceptionless) and licensees; it does not change your rights to use your own contributions for any other purpose.

Please complete the following information about You and The Contributions. If you have questions about these terms, please contact us at [email protected].

You and “The Company” (Exceptionless) agree:

You grant to “The Company” (Exceptionless) a non-exclusive, irrevocable, worldwide, royalty-free, sublicenseable, relicenseable, transferable license under all of Your relevant intellectual property rights, to use, copy, prepare derivative works of, distribute and publicly perform and display “The Contributions”

Python3 Virtualenv Setup

Requirements

Python 3
Pip 3

$ brew install python3

Diagnosing Redis errors on the client side

Customers periodically ask "Why am I getting errors when talking to Redis". The answer is complicated - it could be a client or server side problem. In this article, I am going to talk about client side issues. For server side issues, see here

Clients can see connectivity issues or timeouts for several reason, here are some of the common ones I see:

###Memory pressure

	# first:
	lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom \| while read f; do sudo rm /usr/local/${f}; done
	sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.*

	# To recap, the best way (I've found) to completely uninstall node + npm is to do the following:

	# go to /usr/local/lib and delete any node and node_modules
	cd /usr/local/lib
	sudo rm -rf node*

	// There are two ways to create an plugin:

	public class UniqueUserIdentifierPlugin : IEventPlugin {
	public void Run(EventPluginContext context) {
	if (!ctx.Client.Configuration.IncludePrivateInformation)
	return;

	// Only update it if it's not currently set.
	var user = context.Event.GetUserIdentity();
	if (user != null)

	// only semi-golfed, mostly because i was in the headspace; only used for debugging
	var w, h, x, y, m=maze(w=16,h=16), g=[];

	// generate fully walled grid
	for(y = 0; y < h * 2 + 1; y ++) {
	g[y]=[]
	for(x = 0; x < w * 2 + 1; x ++)
	g[y].push(!(y&1)?"#":!(x&1)?"#":" ");
	}

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else