upstarter

Overview of Python Virtual Environments

This guide is targetted at intermediate or expert users who want low-level control over their Python environments.

When you're working on multiple coding projects, you might want a couple different version of Python and/or modules installed. This helps keep each workflow in its own sandbox instead of trying to juggle multiple projects (each with different dependencies) on your system's version of Python. The guide here covers one way to handle multiple Python versions and Python environments on your own (i.e., without a package manager like conda). See the Using the workflow section to view the end result.

h/t @sharkinsspatial for linking me to the perfect cartoon

upstarter

System Design Cheatsheet

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

Basic Steps

1. 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?

upstarter

$ ->
  active_tracker.track_links()
  active_tracker.track_forms()

# be sure to load Mixpanel's javascript before this, so window.mixpanel exists.

window.active_tracker = new Object

active_tracker.track_links = (selector = 'a[data-event-name]') ->
  $.each $(selector), (index, value) ->

upstarter

# Example of the Active Tracker API
# One javascript call at the top of your page can send any events you want to Mixpanel, Kissmetrics, etc
# Given a few links like this:
# <a href="http://google.com" data-event-name="google" data-event-properties="'target': 'google', 'username': 'nate'"></a>
# Then:
# active_tracker.track_links();
# ... sends an event called "google" 
# ... with JSON properties "'target': 'google', 'username': 'nate', 'environment': 'development'"
# ... to all of your registered event providers (in this case, mixpanel and kissmetrics)