Page 1 of 1
Dev Experience Survey: Managing Secrets & Environments
Help a fellow dev validate a side-project. No spam, takes 60 seconds.
How big is the development team you currently work with?
*
How big is the development team you currently work with?
A
Just me (Solo)
B
2 - 5 devs
C
6 - 20 devs
D
20+ devs
When you add a new API Key (e.g., STRIPE_SECRET) to your local .env, which methods do you use to share it with your team?
*
When you add a new API Key (e.g., STRIPE_SECRET) to your local .env, which methods do you use to share it with your team?
Send via Slack / Microsoft Teams / Discord
Send via WhatsApp / Telegram
Update a shared document (Notion / Confluence / Google Docs)
Commit a .env.example file
Use a Secret Manager (Doppler, Vault, 1Password)
Commit the .env file to Git directly
Other
In the last 3 months, how often has a local build failed or a feature broke because someone on the team didn't have the updated environment variables?
*
In the last 3 months, how often has a local build failed or a feature broke because someone on the team didn't have the updated environment variables?
A
Never. Our process is perfect.
B
Rarely (Maybe once or twice).
C
Monthly occurrence.
D
Weekly occurrence (It's a constant annoyance).
If a new developer joined your team today, how long would it take for them to get the file configured and the project running locally?
*
If a new developer joined your team today, how long would it take for them to get the file configured and the project running locally?
A
< 5 minutes (Automated/Instant)
B
15 - 30 minutes (Copy-pasting from docs/chat)
C
> 1 hour (Chasing people for keys/debugging)
How confident are you that your team's local development secrets have NEVER been leaked or left in plain text (like in chat logs or git history)?
*
How confident are you that your team's local development secrets have NEVER been leaked or left in plain text (like in chat logs or git history)?
0
1
2
3
4
5
6
7
8
9
10
Terrified
Neutral
Extremely Confident
Imagine a CLI tool that works like Git: to encrypt/upload your .env, and for your team to download it securely. No servers to manage. Would this improve your workflow?
*
Imagine a CLI tool that works like Git: to encrypt/upload your .env, and for your team to download it securely. No servers to manage. Would this improve your workflow?
A
No, I'm happy with my current method.
B
Maybe, but I wouldn't pay for it.
C
Yes, definitely.
D
Yes, and I'd pay a small monthly fee to solve this headache.
Submit
