Sam Clark samrocksc

## deeply-nested.html
<!DOCTYPE html>

<head>
  <title>I am a page</title>
  <style>
    .closed {
      display: none;
    }

    .hide_content>ul {

## index.html
‎‎

## fp-ts-fetch.ts
import fetch from 'isomorphic-unfetch';
import { pipe } from 'fp-ts/lib/function';
import * as TE from 'fp-ts/lib/TaskEither';
import * as E from 'fp-ts/lib/Either';
import * as O from 'fp-ts/lib/Option';

export const url = 'https://swapi.dev/api/planets/1/';

export const log = <A>(x: A) => {
  console.info(x);

## googlesecretmanager.ts
/* eslint-disable functional/functional-parameters */
/**
 * This code was written to be followed along with from top to bottom.  It is meant to show the value
 * of having a functional interface, with object arity of one and controlling what goes into functions interface
 * very strict fashion
 *
 * TODO: how do we make this chain easily? Commonality in needs and dependence inversion
 * TODO: What if we need to add an over arching dependency?
 *
 * Why do i like function declaraitons more than class in stantiations?

## docker-compose.yaml
  version: '3.1'
services:
  redis:
    image: "redis:alpine"
    ports:
      - '6379:6379'
    networks:
      - backend
  mongo:
    image: mongo

## gist:7d324d12c324f4db0ad518acff00237d
const fsx = require("fs-extra");
const glob = require("glob");
const fs = require("fs");
const path = require("path");
const mm = require("minimatch");

const getIgnoredFiles = (path) => {
  const str = fsx.readFileSync(path).toString();
  const lines = str
    .split(/\r?\n/)

## unpackLerna.js
const { readFileSync, readdirSync } = require('fs');
const fsx = require('fs-extra');
const { promisify } = require('util');
const lernaConfig = require('./lerna.json');

/**
 * grabs the lerna config, and then does a deep search of all packages and hard copies
 * the node_modules that need to be
 */
const main = async () => {

## dba.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                samrocksc
                / dba.md
            
            
              Last active
              January 30, 2020 15:35
            
              
                Thoughts on dba stuff
              
          
      View dba.md
  
      
    Notes on TypeORM and Lessons Learned DBA


TypeORM seems to have some opinionations that are pretty unfamiliar.  While it may seem advantageous to use them, it's not advantageous to from a 3 year view.  When you build a DB it should always be prepared for inevitable change.  It's not unforeseeable that we at some point get integrated into a bigger company.
PostgreSQL has some awesome new features(plugins, jsonb aggregators); however, it's always my best practice to right as I possibly can to ther SQL-92 spec(SQL - ANSI (American National Standards Institute) SQL (Standard|Reference|Specification) - SQL (92|99|2003|2011))
SQL-92 is primarily what most base database connectors connect to.  There are subtle differences to each kind of architecture for example:

mssql TOP:
SELECT TOP 10 * FROM users;


Postgres LIMIT


## debug w stack
const v = require('debug')('verbose');
const e = require('debug')('error');
const w = require('debug')('warning');

const buildStack = () => {
  const depth = 3;
  if (!this.stackIs) {
    Object.defineProperty(this, 'stackIs', {
      get: function() {
        const orig = Error.prepareStackTrace;

## docker-compose.yml
version: '3'
services:
  mysql:
    image: mysql:5.6
    restart: unless-stopped
    container_name: mysql
    ports:
      - '3306:3306'
    expose:
      - '3306'
	<!DOCTYPE html>

	<head>
	<title>I am a page</title>
	<style>
	.closed {
	display: none;
	}

	.hide_content>ul {
	import fetch from 'isomorphic-unfetch';
	import { pipe } from 'fp-ts/lib/function';
	import * as TE from 'fp-ts/lib/TaskEither';
	import * as E from 'fp-ts/lib/Either';
	import * as O from 'fp-ts/lib/Option';

	export const url = 'https://swapi.dev/api/planets/1/';

	export const log = <A>(x: A) => {
	console.info(x);
	/* eslint-disable functional/functional-parameters */
	/**
	* This code was written to be followed along with from top to bottom. It is meant to show the value
	* of having a functional interface, with object arity of one and controlling what goes into functions interface
	* very strict fashion
	*
	* TODO: how do we make this chain easily? Commonality in needs and dependence inversion
	* TODO: What if we need to add an over arching dependency?
	*
	* Why do i like function declaraitons more than class in stantiations?
	version: '3.1'
	services:
	redis:
	image: "redis:alpine"
	ports:
	- '6379:6379'
	networks:
	- backend
	mongo:
	image: mongo
	const fsx = require("fs-extra");
	const glob = require("glob");
	const fs = require("fs");
	const path = require("path");
	const mm = require("minimatch");

	const getIgnoredFiles = (path) => {
	const str = fsx.readFileSync(path).toString();
	const lines = str
	.split(/\r?\n/)
	const { readFileSync, readdirSync } = require('fs');
	const fsx = require('fs-extra');
	const { promisify } = require('util');
	const lernaConfig = require('./lerna.json');

	/**
	* grabs the lerna config, and then does a deep search of all packages and hard copies
	* the node_modules that need to be
	*/
	const main = async () => {
	const v = require('debug')('verbose');
	const e = require('debug')('error');
	const w = require('debug')('warning');

	const buildStack = () => {
	const depth = 3;
	if (!this.stackIs) {
	Object.defineProperty(this, 'stackIs', {
	get: function() {
	const orig = Error.prepareStackTrace;
	version: '3'
	services:
	mysql:
	image: mysql:5.6
	restart: unless-stopped
	container_name: mysql
	ports:
	- '3306:3306'
	expose:
	- '3306'