navicore

#
# BEGIN all purpose associative array via temp fs
#
prefix=$(basename -- "$0")
mapdir=$(mktemp -dt ${prefix})
trap 'rm -r ${mapdir}' EXIT
put() {
  [ "$#" != 3 ] && exit 1
  mapname=$1; key=$2; value=$3
  [ -d "${mapdir}/${mapname}" ] || mkdir "${mapdir}/${mapname}"

navicore

#!/usr/bin/env bash

curl --request GET \
--url "https://api.github.com/repos/dtlaboratory/dtlab-scala-alligator/pulls?state=all" \
--header "Accept: application/vnd.github.v3+json" \
--header "Authorization: Bearer $GITHUB_PAT"

navicore

public class Quine { public static void main(String[] args) { char c=34; System.out.println(s+c+s+c+';'+'}'); } static String s="public class Quine { public static void main(String[] args) { char c=34; System.out.println(s+c+s+c+';'+'}'); } static String s=";}

navicore

===> Initial Screen <===
What is maven used for?
Spring provider? Change out DB impl in JPA?
What can you tell me about Dockerfile?
What is Java casting? Syntax?
What is dependency injection in Spring?
What are Java generics?
grpc vs REST

===> Programming <===

navicore

If you can keep your head when all about you   
    Are losing theirs and blaming it on you,   
If you can trust yourself when all men doubt you,
    But make allowance for their doubting too;   
If you can wait and not be tired by waiting,
    Or being lied about, don’t deal in lies,
Or being hated, don’t give way to hating,
    And yet don’t look too good, nor talk too wise:

If you can dream—and not make dreams your master;   

navicore

The Twelve Factors
-----------------

I. Codebase
One codebase tracked in revision control, many deploys

II. Dependencies
Explicitly declare and isolate dependencies

navicore

Keybase proof

I hereby claim:

• I am navicore on github.
• I am navicore (https://keybase.io/navicore) on keybase.
• I have a public key ASB_uoJJbQKL02G5uSnWSSBEX0VXA9AYVYvzclBRDm-T9go

To claim this, I am signing this object:

navicore

Navicore Modular Manifesto

1. Analog biased
2. Prefer big modules that don't do much - Modular is nothing without ergonomics
3. Effects are pedals
4. No dedicated battleship sequencer
5. No dedicated master clock
6. No menus or button combinations
7. Quantizers, Shift Registers, Comparators, and Precision Adders rule

navicore

nyc-scale simulation via DTs

assumptions and guiding principles

Some notes about the challenge of performing large scale simulations with DTs.

HIGH UTILIZATION

The guiding principle is that you best solve compute problems by running resources just below their saturation level, saving both money and time. Money and time are both sucked up by under utilized resources and I/O processing.

navicore

Ed's Cosmology