4 ms·
Here's an elucidation, taking that question seriously, supplying a bunch of "Why's" -- * https://medium.com/@ajay.monga73/why-developers-still-hardcode-credent
by ncr100 10mo ago
Here's an elucidation, taking that question seriously, supplying a bunch of "Why's" --
* https://medium.com/@ajay.monga73/why-developers-still-hardcode-credentials-a93312ca32d1 https://medium.com/@ajay.monga73/why-developers-still-hardco...
- robot-wrangler 10mo agoA root-cause analysis here that's about intrinsic difficulty is misguided IMHO. Secrets and secrets-delivery are an environment service that individual developers shouldn't ever have to think about. If you cut platform/devops/secops teams to the bone because they aren't adding application features, or if you understaff or overwork seniors that are supposed to be reviewing work and mentoring, then you will leak eventually. Simple as. Cutting engineering budgets for marketing budgets and executive bonuses practically guarantees these kinds of problems. Engineering leadership should understand this and deep down, it usually does. So the most direct way to talk about this is usually acknowledging willful negligence and/or greed
- catlifeonmars 10mo agoAgreed. Proper secrets management is table stakes for any company entrusted with paying customers.
- ncr100 9mo agoThank you robot wrangler - i don't have that insight without people sharing things like do here <3 I agree with what you write here. It was a bad proffer / explanation on my part.