3 ms·
This resonates so much. One way to gauge the gap is to look for redefined reliability terms: - Do they call it continuous deployment when it's really continuou
by l0b0 6y ago
This resonates so much. One way to gauge the gap is to look for redefined reliability terms:
- Do they call it continuous deployment when it's really continuous integration? CD is when the build pipeline goes all the way to production without any human interaction (except possibly a review step).
- Do they call it continuous integration when it's really nightly builds, manual builds, local builds, or per-feature rather than per-change?
- When HTTP doesn't redirect to HTTPS, when common credentials aren't rotated whenever anyone who knows them leave, when full-disk encryption is optional, when someone can walk in from the street and look at or change anything, when not using common password storage protections or anything like that, even an amateur knows it's not "excellent" security.