Big dump

andy.org

@@ -0,0 +1,35 @@
+#+TITLE: Andy and Golang
+#+AUTHOR: Adam Mohammed
+
+* First and foremost I care about my te
+* I understand why you would be concerned with the choice to use elixir
+** This is not an official choice of the team
+** This is an experiment
+** We've hired engineers who are mainly experienced in golang
+** I acknowledge that some thing
+
+* Concerns around ruby and elixir
+- design goals as ruby
+- technical difficulties we had
+- static typing feels much more important
+- federated graphs MUST
+
+
+
+
+* Let's drop programming languages for a second
+- 12 people on the team
+  - 5? actual owners
+  - Lucasmpb
+  - Emiliano
+  - Hogle
+  - Myself
+
+
+- Here's what I'm looking at
+  - we have ideas on products that might improve metal
+  - it takes very long to produce those ideas
+  - how do we find ways to deliver value?
+  - write up documentation on the idea and get feedback from it
+  - try it and see what works
+  - some blend of the two?

devenvs/papi.devenv.nix

@@ -0,0 +1,48 @@
+{ pkgs, ... }:
+
+{
+  # https://devenv.sh/basics/
+
+  env.GREET = "devenv";
+
+  # https://devenv.sh/packages/
+  packages = [
+    pkgs.nats-server
+    pkgs.natscli
+    pkgs.libxml2
+    pkgs.icu
+    pkgs.postgresql_12
+    pkgs.memcached
+    pkgs.curl
+  ];
+
+  # https://devenv.sh/scripts/
+  scripts.hello.exec = "echo hello from $GREET";
+
+  # enterShell = ''
+  # '';
+
+  # https://devenv.sh/languages/
+  languages.ruby.enable = true;
+  languages.ruby.package = pkgs.ruby_3_0;
+
+  # https://devenv.sh/pre-commit-hooks/
+  # pre-commit.hooks.shellcheck.enable = true;
+
+  # https://devenv.sh/processes/
+  # processes.ping.exec = "ping example.com";
+  processes.nats.exec = "nats-server";
+
+
+  services.postgres.enable = true;
+  services.postgres.package = pkgs.postgresql_12;
+  services.postgres.initialScript = ''
+CREATE USER postgres SUPERUSER;
+'';
+  services.rabbitmq.enable = true;
+  services.memcached.enable = true;
+
+
+
+  # See full reference at https://devenv.sh/reference/options/
+}

eric-bachelor-party.org

@@ -0,0 +1,19 @@
+#+TITLE: Eric's Bachelor Party
+#+AUTHOR: Adam Mohammed
+#+DATE: July 23, 2023
+
+
+* Potential Dates
+
+9/21 - 9/24
+9/28 - 10/1
+10/5 - 10/8
+
+* Places to Stay
+https://www.airbnb.com/rooms/45465450?adults=8&check_in=2023-09-28&check_out=2023-10-01&source_impression_id=p3_1690159366_%2BgdjBYNvOoC8C4fv&previous_page_section_name=1000&federated_search_id=0a9d74d6-c981-4761-ba24-efec91115cac&modal=PHOTO_TOUR_SCROLLABLE - sick lodge if we're really scared of dirt
+https://www.airbnb.com/rooms/45516747?adults=8&check_in=2023-09-28&check_out=2023-10-01&source_impression_id=p3_1690162406_vj9v1YK%2BilH%2B3Sgj&previous_page_section_name=1000&federated_search_id=48c78479-928d-4445-ba6d-6c0a985bca56 - way more beds
+
+* Things to do
+
+Skyline trail
+Limestone Disc Golf

lucas.org

@@ -0,0 +1,22 @@
+#+TITLE: Lucas
+#+DATE: May 31, 2023
+
+* Talking points with Lucas
+
+can't say no
+
+
+grok the whole thinger
+
+
+Keeping tabs on things
+
+narwhal calls example of record calls
+
+
+osie
+
+entitlements - you have to duplicate them
+
+
+cleaning up roll bar

notes.org

@@ -4,3 +4,32 @@
 ** TODO Try to deploy
 ** TODO Put together POC for micro-caching RAILS
 ** TODO Create a ticket to deal with 403s for provisioning failures
+
+** TODO Express concern around engineering quality
+
+I raised concerns that this result is doesn't meet the bar to achieve success on the problem we set out to solve.
+I also do believe it doesn't help solve the problem
+
+When I express that the immediate response was defense. That's the wrong response itself.
+
+I can be clearer -- There are two points I want here,
+1. I don't think this solves the problem we were targeting.
+2. We have finite time, deciding if we want to iterate or redesign based on learning is a decision to make.
+3. Option 3 which I didn't think was possible is to completely ignore the point.
+
+
+Here's what's worse though. We're trying to transform the team to be enablers for other teams, so we need to set the bar.
+We have people on this team that are trying to raise / set the bar, and when they raise concerns they are dismissed without
+consideration.
+
+
+My main concern is our ability to field feedback on this team. I don't
+think I have many occurrences of differing opinions being given the required space.
+
+At best it leads to apathy, at worst it leads to mediocrity. Either way it leads to a dysfunctional team by design.
+
+
+Those people trying to raise the bar aren't doing so selfishly.
+We don't get immediate gain out of performing better or working harder, we still get paid the same.
+So why would we be striving to raise the bar? This is a fundamental question to see if a leader understands
+what high performers need to thrive.

scalable-api.org

@@ -0,0 +1,23 @@
+#+TITLE: Scalable API
+#+AUTHOR: Adam Mohammed
+
+* Overview
+
+In this document we take a look at the concept of breaking the
+monolith from the start. By that I mean, what do we hope to achieve
+with the breaking the monolith. From there we can identify the
+problems we're trying to solve.
+
+Part of the problem (I have) with the "breaking the monolith" phrase is the
+vision is too lofty. That phrase isn't a vision it's snake-oil. The
+promised land we hope to get to is a place where teams are able to
+focus on delivering business value and new features to customers that
+are meaningful, leverage our existing differentiators, and enable new
+differentiators.
+
+What do we believe is preventing us from delivering business value quickly
+currently? What we identify there is a hypothesis and based on some
+level of intuition, so it's a great start for an attempt to optimize
+the process. It's even better if we can quantify how much effort is
+spent doing these speed-inhibiting activities, so we know we're
+optimizing our bottlenecks.

shim.org

@@ -0,0 +1,19 @@
+#+TITLE: Org/Project SHIM
+#+AUTHOR: Adam Mohammed
+#+DATE: June 1, 2023
+
+* Problem
+
+Infratographer needs a way to hook into existing organizations and
+projects to associate load balancer and related objects to the
+entities which govern them.
+
+
+* Auxilliary Issues
+
+
+* Questions?
+- is there an endpoint to submit my policy documents?
+- Is it reentrant, or should I do it at most once?
+- What needs to happen for metal users -> resource owners?
+-

vlan-issues.org

@@ -0,0 +1,15 @@
+#+TITLE: Vlan Issues
+#+AUTHOR: Adam Mohammed
+
+
+* When a customer wants to provision an instance what does it do
+ - it's up to the caller to know what it needs
+
+   Narwhal just does the thing and reports back status
+
+
+* Narwhal queues tasks for workers to pick up later
+
+* Added a way for narhwal and API to coordinate batches
+
+* What about batch ordering?