As one such developer, it is a powerful ability to be able to bypass restrictions meant to be used sparingly for a good reason
I rarely commit the same kind of code the full time professional developer do(when bypassing policies).
Typically it is stuff like urgent patch in prod that may not have coverage , or partial long running refactor which breaks existing tests but better to be able merge quickly than keep the branch constantly free of merge conflicts , or experimental exploratory new type of code(new lang , stack whatever )for which we have to yet evolve processes, part of what the lead is supposed to be exploring and so on.
Although In my experience junior leads more often than not abuse their privileges than use it well.
I rarely commit the same kind of code the full time professional developer do(when bypassing policies).
Typically it is stuff like urgent patch in prod that may not have coverage , or partial long running refactor which breaks existing tests but better to be able merge quickly than keep the branch constantly free of merge conflicts , or experimental exploratory new type of code(new lang , stack whatever )for which we have to yet evolve processes, part of what the lead is supposed to be exploring and so on.
Although In my experience junior leads more often than not abuse their privileges than use it well.