Engineering deep-dives, security thinking, and practical guides on keeping environment variables off disk and out of your coding agents' reach.
.env files with your team (without Slack)Pasting your .env into a Slack DM works for about a week — then keys rotate, copies go stale, and nobody knows who still has the prod password. The real options for keeping a team in sync, with honest trade-offs.
.env secretsCursor and Claude Code can read your .env any time. The fix isn't hiding the file — it's not having one.
An honest comparison: how simple each is to run, whether secrets ever touch disk, and what it costs as you grow.
Occasional, technical, no spam. Security notes and engineering write-ups when we publish them.