Good news... the feature seems to work and didn't break prod. Bad news... Turns out when an env isn't set in the CI, it's pulled from the dev .env file. I forgot how complex I made this app's build process to share env variables btw dev and prod (classic "seemed like a good idea at the time").

Just merged a new reporting feature into prod and deployed. It was behind an env called ACTIVATE_REPORTING. I left it unset in the CI just to make sure nothing breaks. But logs show people using it...

Amazing, if you have a 3090 or better, finetuning an LLM with LoRA is basically just point and click now-- https://github.com/oobabooga/text-generation-webui/blob/main/docs/Training-LoRAs.md

The E-Myth Revisited has you make an org chart, which might feel unfamiliar for non-corporate types (it did for me). Solution: ChatGPT! It generated an org chart in markdown for a small SaaS and drafted "position contracts" (E-myth term) for each position.

E-Myth Revisited explains my business failures-- the coder in us ("technician personality") can produce results-- but without sticking to a well-formed plan the product can be valueless. Working on Ch. 12 right now, "your primary aim." Answering these is kind of triggering a midlife crisis.

Joined yesterday and already made a cameo on a video by marketing for developers extraordinaire @justinjackson.ca. Bluesky's been great!