Interesting. Although I find it matches style, organization, etc. better on big, existing projects compared to small or new projects. Still think it's worth trying to automate away any small parts so you can focus on the more important parts. Requiring 100% test coverage seems to be a big advantage.
You could add a title helper that includes `CONDUCTOR_WORKSPACE_NAME` in the development environment so you don't have to rename tabs.
Also, curious what commands, MCPs, plug-ins, tools, etc. you're using, if any. I started github.com/tristandunn/... to avoid manual style adjustments.
I've been using Monaspace Neon Var since 2023, which is the second longest I've used a font.
Based on my configuration history I started with Monaco in 2010 then switched to Droid Sans Mono in 2011, Hack in 2019, and SF Mono in 2021.
Is there a RTFM version?
"Too right, mate! I can spot a few areas where this beaut of a schema could use some fine-tuning, like a crocodile hunter sharpening his knife."
For fun I was just telling Claude to "ONLY respond in the tone of Crocodile Dundee." which I imagine would work in ChatGPT too. Using a funny or familiar style seems like an easy way to get people more comfortable with AI.
Depends on the size of the project but I'd probably start with a Kamal accessory on the same server then move to a separate server or switch to a managed version based on needs.
Inspired me to finish my article on how to set up Kamal deployment for my Rails template. Might not be exactly what you're looking for but could help. And I just merged Terraform configuration that uses `cloudinit` and targets DO, which could help with the hardening. tristandunn.com/articles/dep...
