Highly extensible software like Emacs, Vim, and Neovim tend to grow their own package managers. A software developer, for example, might want to install editor plugins that hook into a particular programming language's linter or language server. The programmer's text editor is therefore extended to support managing additional software to extend the text editor. If this loop continues for too long, the programmer's editor becomes more delicate and complex. The remedy for this problem is to manage software using dedicated tools apart
| - Intros + background overview | |
| - API service in a k8s clusters | |
| + Single region HA from starting with a single pod deployment? | |
| + API talks to MongoDB outside of the cluster | |
| + Describe KPIs for this application? | |
| + Describe how you would make this service multi region in AWS at a high level? | |
| - What are the three types of observability data? | |
| - How would you troubleshoot a k8s pod stuck in a crashloopbackoff state? | |
| - How can you expose a k8s application publicly using AWS and EKS? | |
| - How can you provide a file to a pod in k8s without building it into your application image? |
I found the watchman docs hard to follow / bereft of useful examples. Below is my attempt at a quickstart guide; see ryan-williams/watchman-helpers for some aliases and other scripts.
If you want to use Bitwarden CLI for ssh have a look at: How to use use Bitwarden CLI for SSH-Keys in macOS
Wirtten and tested on macOS Ventura
To allow Touch ID on your Mac to authenticate you for sudo access instead of a password you need to do the following.
If you want to use Touch ID have a look at: How to use use Bitwarden CLI with macOS Touch ID
Wirtten and tested on macOS Ventura
Before you can use Bitwarden CLI for your SSH private keys you have to add them to your Bitwarden account. Just create a normal login. The name, username and URI fields doesn't matter for my functions.
I get asked pretty regularly what my opinion is on merge commits vs rebasing vs squashing. I've typed up this response so many times that I've decided to just put it in a gist so I can reference it whenever it comes up again.
I use merge, squash, rebase all situationally. I believe they all have their merits but their usage depends on the context. I think anyone who says any particular strategy is the right answer 100% of the time is wrong, but I think there is considerable acceptable leeway in when you use each. What follows is my personal and professional opinion:
| # Run me: | |
| # ❯ nix develop .#work -c vault --version | |
| # mysql Ver 15.1 Distrib 10.11.6-MariaDB, for Linux (x86_64) using readline 5.1 | |
| # ❯ nix develop .#fun -c mysql --version | |
| # Vault v1.15.6 (615cf6f1dce9aa91bc2035ce33b9f689952218f0), built 2024-02-28T17:07:34Z | |
| { | |
| inputs = { | |
| nixpkgs.url = "github:NixOS/nixpkgs/nixos-23.11"; | |
| flake-utils.url = "github:numtide/flake-utils"; |