What is an example of a safety rule who’s conditions no longer exist which would not have the conditions almost immediately return if the rule was removed?
My job is populated by dinosaurs that only recently adopted git for version control. They had some rules and procedures that made a kind of sense when deployment meant “I’ll scp the files to the prod server”, but don’t add value anymore.
Some people had a rule where after “deploy” they would SSH into prod and check the md5 hash of the files and compare them to their local copy. You don’t have to do that.
They also wanted to only allow one person to work on a file at the same time because “you can overwrite their changes”. Git handles that fine (unless you really fuck up the merge conflict, admittedly)
My job is populated by dinosaurs that only recently adopted git for version control. They had some rules and procedures that made a kind of sense when deployment meant “I’ll scp the files to the prod server”, but don’t add value anymore.
Some people had a rule where after “deploy” they would SSH into prod and check the md5 hash of the files and compare them to their local copy. You don’t have to do that.
They also wanted to only allow one person to work on a file at the same time because “you can overwrite their changes”. Git handles that fine (unless you really fuck up the merge conflict, admittedly)