7 ms·

I've seen single line changes cause data loss, corruption, system outages, remote root exploits... I'm not sure that the number of lines makes the change more

by rm-rf 16y ago

I've seen single line changes cause data loss, corruption, system outages, remote root exploits... I'm not sure that the number of lines makes the change more or less risky.

ichverstehe 16y ago
And how exactly does this relate to the way they deploy their code? As far as I can tell, they actually review code before marking it ready for deploy. That kind of changes would be an issue with "usual" large batch deploys as well.
chaz 16y ago
I've also seen many devs look at a broken release and instantly realize their mistake. A forgotten production config, a hard coded variable, or an empty cache. If code is in fact reviewed before going to production, the risk is significantly lower.
cool-RR 16y ago
Nice choice of username, by the way.
MartinCron 16y ago
The safest change to make to a stable system is the smallest change possible.