• Registered to vote in NY (LA county prior).
• Signaling Reminder: There are many problems on Earth. More than time allows an individual to solve. Every human can solve their own optimization problem. They alone understand their skills, passions, gifts, priorities, and schedules to choose which solutions to pursue. That can include voting as a small periphery responsibility. That can include voting as a primary personality trait. It can ignore voting overall. I’m not talking about what you vote for, I’m observing that it is ok to not vote. Use the time to study medicine if you want. Learn about physics. Adopt an animal. Research how to consume a healthier diet for your family. Build an iphone app that makes a commute easier for 10 strangers. We don’t elect our doctors. We don’t democratize engineering choices. And the malignancies are deterministically adversarial in those systems.

• Tons of private work.
• Coconut oil is good for new tattoos.
• Binance going to acquire FTX?? (#1 vs #3)
• Did a fireflies recording of a gmeet. It actually is a pretty cool tool Audio/video recording. AI transcription. Captures chat/notes (gmeet does not). Tries to pull out action items, prices, etc. Metrics on talktime by participant, sentiment (positive/negative/neutral). Would definitely use this if free, and will reconsider as scaling.

• Supercontest.
• Updated banner, redeployed.
• Made some progress on the CICD work. https://gitlab.com/bmahlstedt/supercontest/-/issues/165.
• Deleted the old SSH key variable from gitlab CICD settings. Added AWS access key / secret / default region.
• Created a Lifecycle Policy rule in ECR to only keep a count of 10 max (most recent). Will expire FIFO after that.
• Removed some venv and tox stuff. Just run in the built images (system env). Also removed the ctags reindexing stuff, no longer using vim.
• DEV: Builds the image locally, runs the image locally, does not tag the image, does not push the image, runs on any branch, tests in the locally running image.
• PROD: Builds the image in CI, runs the image in CI, tags the image with the git sha, pushes the image, runs on master only, tests in the running image.
• Branch tests are just build-prod then test. No tag or push. Then master branch will build-prod, test, tag, push. Then trigger the deploy target, which is just start-prod (pulls the latest, most recent master-cicd-blessed-prod image).
• You have to upload an explicit image tagged latest to pull latest, of course. This isn’t clientside (image registry, deploy infra, etc) logic that you get for free. Your push in CICD needs to accommodate what image tags you want to be available.
• The client utility for docker will default to latest, however (when no tag is specified and you build an image).
• Did some planning for later. Image size reduction, proper tagging, scanned img security vulnerabilities.
• Will also use CloudFormation to provision/configure the EC2 instance, rather than the manual one I manage right now. This will make spinup easier (like moving from DO to AWS) or updating the machine, or redeploying, or disaster recovery, etc.
• May try some of the developer tools too. I don’t have any gitlab features I’m married to. Using CodeCommit, CodeBuild, CodeDeploy, and CodePipeline would probably make it all easier to use in the AWS ecosystem. I’ll try the all-in approach for a bit.
• Might even try RDS for managed postgres.
• ELB for the nginx reverse-proxy and letsencrypt companion container infra I run right now.
• Will also move the banner to CloudFront (AWS CDN) so that I don’t have to rebuild/deploy every wednesday.