Kyle Alwyn kylealwyn

Firebase Environments

Last updated: April 21st, 2017.

At the time of writing this gist (January 4th, 2017), I was unable to find true sandboxing to separate development and production environments for a Firebase project. The closest we can get is to create two separate Firebase projects -- one for development and one for production.

Pros

Complete separation and isolation of all Firebase features.
Freedom to experiment without risking the corruption of production data.

Cons

MySQL

Getting started:

What I Wish I'd Known About Equity Before Joining A Unicorn

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

become active record migration expert (Rails 4.0.2)

workflow:

create model

$ rails g model NameOfModel
    invoke  active_record
    create    db/migrate/YYYYMMDDHHMMSS_create_name_of_models.rb

	#!/bin/bash

	if [ "$1" == "-h" ]; then
	cat <<END
	AWS AutoScaling Termination Helper:
	terminate an instance in an auto scaling group

	Usage: $0 {group-name}

	END

	1. Highlight a recommended option,
	2. Allow users to switch currency (€/$/£)
	3. Allow users to switch pricing monthly/yearly
	4. Keep the entire pricing plan area clickable
	5. Use slider to calculate how much a user would save
	6. Provide free first month for good engagement
	7. Prominently highlight testimonials prominently
	8. Repeating call to action on top and bottom
	9. Sell benefits instead of features
	10. Indicate that users can cancel any time

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console