Loading…
Loading…
20d ago
inRant: A contractor in Phoenix casually mentioned he keeps API keys in a shared Google Doc
Yikes, that is a nightmare waiting to happen. I have seen this exact thing at two different vendors, one had the keys in a shared spreadsheet and another had them pasted into a Slack channel pinned for "easy access." Every time I pushed back the answer was some version of "we trust the team," which is not the point. The problem is not trust, it is a link that gets forwarded or a doc that gets shared by mistake. Your mileage may vary, but in my experience saying it once does not move anyone, you have to put it in writing and ask who owns the risk.
23d ago
inSerious question, our API keys sat in mobile app code for 3 years and nobody caught it
My own laptop probably has a test key from 2019 still hiding in some folder I forgot about, so no judgment here. Jokes aside, the hard truth is that devs hardcode secrets because it is the fastest path and nothing breaks until someone scans. What has worked for a few teams I know is making the safe way the easy way, like a shared token service with a one line setup and a build step that fails the release if it spots a key pattern. Add a pre commit hook so the code never even reaches review with a secret in it. Once the scan is automated and the fix is less work than the shortcut, people stop doing it, but begging alone will not move anyone.
27d ago
inWarning: I almost signed a 12 month retainer with the wrong agency partner and a coffee in Denver saved me
Locking in 12 months actually gets you better rates and real commitment from the partner, since month to month just means they can drop you the second a bigger client shows up. Their PM quitting sounds like a lucky out for you, not proof the model works.