Sean Colsen seancolsen

Crowd-funding large extensions

This is a chronological description so you can see my plans for bootstrapping the model. The plan so far includes just me, and I'm not totally committed to going forward with it.

Brand: I would build a new brand for a dev shop. Here's what I've come up with so far (still a working name)
- Name: Left Join Labs
- Domain: leftjoinlabs.com (already registered)
- Logo:
- Website: haven't started on this

Useful snippets

A scratch pad of things that are hard to remember

vim

save with sudo

Checklist

(Move each criterion that you evaluate into "Passing" or "Failing". Add comments describing any failures.)

Not evaluated
- A JIRA ticket is mentioned (or not needed) (r-jira)
- The automated tests pass (r-test)
- The code looks good (r-code)
- It works as advertised (r-run)
- Users will be able to transition to this change easily (r-users)

Analytics Proposal

Overall

The analytics system is its own app with its own repo and its own database.
Eventually it could even have its own server, especially if disk space becomes an issue. But we'd start by deploying it on the prod server. A separate server would also be nice if we end up wanting to perform any analytics that turn out to be computationally intensive. A cheap VPS that's slow but has a big disk would be ideal.
It has a REST interface to receive data
No authentication at first, just don't expose it outside of localhost
We could use whatever stack for this tiny thing, really. It might be a cool opportunity to try something new. Maybe you want to build it in Haskell or Rust? Personally, I'd consider trying Deno and Oak because I think Deno is eventually going to supplant Node, and Oak is the Deno equivalent of Express. But we could always just build it in Flask. I'm fine with anything here.

Context

Users need to be able to quickly browse the data model so that they can complete tasks that involve performing actions in various tables or navigating to related tables. Besides indicating the location, these navigation elements should also be used to show the hierarchical structure and the relationships between the various data model parts.

Hierarchical Structure

The navigation design will be based on the following hierarchical structure:

Removing Tabs

Tabs will be phased out as part of the new navigation improvements. The new navigation considers the problems that tabs addressed and incorporates them into the design.

	[32mCreate test application[39m
	[32mCreate data directory: /home/sean/.amp/canary/data/kMPtKRrAp5ugpMRqFeSRQ0OP46UJfD9p[39m
	AMP_URL='http://localhost:7979'
	AMP_ROOT='/home/sean/.amp/canary'
	AMP_DB_DSN='mysql://canary_9e1ct:[email protected]:3306/canary_9e1ct?new_link=true'
	AMP_DB_USER='canary_9e1ct'
	AMP_DB_PASS='daNfLSMv1DRlh8Rx'
	AMP_DB_HOST='127.0.0.1'
	AMP_DB_PORT='3306'
	AMP_DB_NAME='canary_9e1ct'

	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="utf-8">
	<meta name="viewport"
	content="width=device-width, height=device-height, initial-scale=1, user-scalable=no, viewport-fit=cover">
	</head>
	<body>

	<div id='layout'>

	DROP TABLE IF EXISTS "star";
	CREATE TABLE "star" (
	"id" serial NOT NULL,
	"name" VARCHAR(255) NOT NULL,
	CONSTRAINT "star_pkey" PRIMARY KEY ("id")
	);
	INSERT INTO "star" ("id", "name") VALUES
	(1, 'Sun');

	DROP TABLE IF EXISTS "planet";