anselm anselm

## simplefirebasesetup
This is a quick outline of building an web service with these constraints:

  - some kind of cloud hosting; ie; visibile anywhere on the internet, no fretting over back end unix installs
  - presents a user editable fillable form on a web page
  - saves that user supplied form data to persistent state on the server
  - signs the user supplied information with a private key
  - does some secure server side transactionally bound database actions
  - returns a result to the user

I've been using firebase lately and I'd definitely do it this way if I was asked to do a quick one off.

## gist:2e9e45211b90abe30284f233386e5b62
### Keybase proof

I hereby claim:

  * I am anselm on github.
  * I am anselmhook (https://keybase.io/anselmhook) on keybase.
  * I have a public key whose fingerprint is 47D8 81E1 7770 619D F180  C796 238F A172 01DE BFE1

To claim this, I am signing this object:

## categories.txt
- categories

	- support
		- hardware
		- 3d trackers
		- rendering
		- animation
		- datastore
		- cloud service
		- account management

## gps_sound_game.html
<!-- see the writeup at https://medium.com/@anselm/playing-with-gps-spatialized-web-audio-f86e45d31d10 -->

<canvas id="mycanvas" width=512 height=512>
</canvas>


<script>

// a small database of all the objects
let artifacts = [

## import_some_data_to_parse.js
const http = require('http');

function pushme(mydata,mytable) {

  var postData = JSON.stringify( mydata );

  var options = {
    hostname: 'localhost',
    port: 1337,
    path: '/parse/classes/'+mytable,

## HalfCylinder.m
//
// a snippet for for iOS scenekit
// generate an open half cylinder in such a way that the texture stretches from 0->1 over the surface
// the idea is that this could be used for a 180' pano
//

- (SCNGeometry*) createCurve:(int)resolution width:(float)radius {

    if(resolution<1)return nil;

## early_out.mm
A small bit of kvetching...

Imagine in Shakespeare if a sonnet didn't hew towards the core message but instead had you hold all the loose blocks of marble in working memory.

My mistresses eyes are like the sun in no way, but in the way they are not like the sun so is her hair like wires, and in the way they are like the sun there is nothing further to remark upon.

By a similar quality it bugs me when early out conditions are deferred to the end of a code block. For me this is probaby a carry over from working in assembler. In early programming environments there was both a computational and cognitive cost to jumping around a block of other code prior to ceding control. Modern compilers optimize this away but there's still a cognitive burden to having to hold a larger model in mind. If you think of a piece of code as a tree of branching possibilities then it makes sense to whittle away those branches as quickly as possible so that you're left with the minimum functionality needed to close out the responsib

## migrate.rb
require 'date'
require 'net/http'
require 'uri'
require 'open-uri'
require 'rubypress'
require 'mime'
require 'mime/types'
require 'imgkit'

# goals

## Tubular.cs

using UnityEngine;
using System.Collections;
using System.Collections.Generic;
using System.Collections.Specialized;

/**
 * @author zz85 / http://www.lab4games.net/zz85/blog
 * Extensible curve object
 **/

## publish.php
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Web Notes</title>
<!-- Pull in Bootstrap to style things up a bit -->
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap-theme.min.css">
	This is a quick outline of building an web service with these constraints:

	- some kind of cloud hosting; ie; visibile anywhere on the internet, no fretting over back end unix installs
	- presents a user editable fillable form on a web page
	- saves that user supplied form data to persistent state on the server
	- signs the user supplied information with a private key
	- does some secure server side transactionally bound database actions
	- returns a result to the user

	I've been using firebase lately and I'd definitely do it this way if I was asked to do a quick one off.
	### Keybase proof

	I hereby claim:

	* I am anselm on github.
	* I am anselmhook (https://keybase.io/anselmhook) on keybase.
	* I have a public key whose fingerprint is 47D8 81E1 7770 619D F180 C796 238F A172 01DE BFE1

	To claim this, I am signing this object:
	- categories

	- support
	- hardware
	- 3d trackers
	- rendering
	- animation
	- datastore
	- cloud service
	- account management
	<!-- see the writeup at https://medium.com/@anselm/playing-with-gps-spatialized-web-audio-f86e45d31d10 -->

	<canvas id="mycanvas" width=512 height=512>
	</canvas>


	<script>

	// a small database of all the objects
	let artifacts = [
	const http = require('http');

	function pushme(mydata,mytable) {

	var postData = JSON.stringify( mydata );

	var options = {
	hostname: 'localhost',
	port: 1337,
	path: '/parse/classes/'+mytable,
	//
	// a snippet for for iOS scenekit
	// generate an open half cylinder in such a way that the texture stretches from 0->1 over the surface
	// the idea is that this could be used for a 180' pano
	//

	- (SCNGeometry*) createCurve:(int)resolution width:(float)radius {

	if(resolution<1)return nil;
	A small bit of kvetching...

	Imagine in Shakespeare if a sonnet didn't hew towards the core message but instead had you hold all the loose blocks of marble in working memory.

	My mistresses eyes are like the sun in no way, but in the way they are not like the sun so is her hair like wires, and in the way they are like the sun there is nothing further to remark upon.

	By a similar quality it bugs me when early out conditions are deferred to the end of a code block. For me this is probaby a carry over from working in assembler. In early programming environments there was both a computational and cognitive cost to jumping around a block of other code prior to ceding control. Modern compilers optimize this away but there's still a cognitive burden to having to hold a larger model in mind. If you think of a piece of code as a tree of branching possibilities then it makes sense to whittle away those branches as quickly as possible so that you're left with the minimum functionality needed to close out the responsib
	require 'date'
	require 'net/http'
	require 'uri'
	require 'open-uri'
	require 'rubypress'
	require 'mime'
	require 'mime/types'
	require 'imgkit'

	# goals

	using UnityEngine;
	using System.Collections;
	using System.Collections.Generic;
	using System.Collections.Specialized;

	/**
	* @author zz85 / http://www.lab4games.net/zz85/blog
	* Extensible curve object
	**/
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="utf-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Web Notes</title>
	<!-- Pull in Bootstrap to style things up a bit -->
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap.min.css">
	<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.4/css/bootstrap-theme.min.css">