Adam Sand explains why teams should request tools and resources in advance rather than scrambling last-minute. He warns against leaking API keys and database credentials, and describes a provisioning system where team members submit requests by 4 p.m. so everything is ready and locked down before they need it.
Chapters
And so you don't think about it, but you're like, your team's gonna need things and you have to have a plan for how they're gonna get those things and you're gonna do it in a way that's safe and secure so you don't end up like those other jack-o'-lanterns that I found that had all their API keys, environment variables, like Supabase database keys and stuff like this. It's stupid. So this way I was able to keep everything on lock, But they had to come to me to let me know what stuff they would need provisioned so that at 4 o'clock I went and tried to get as much of it ready as possible. But then of course their Claude would be like, oh, you need this, you need this. And so I'll talk to you guys later about how I made sure that everybody had the stuff that they needed. That's awesome.