▲ | seeknotfind a day ago | |||||||||||||||||||||||||||||||||||||
Here's the dangerous way I put it that I only tell senior people: understand why rules were made and make sure the people who made them would be happy. | ||||||||||||||||||||||||||||||||||||||
▲ | chias 19 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||||||||
I saw this put really, really well not too long ago: > A lot of us got the message earlier in life that we had to wait for other's permission or encouragement to do things, when in fact, all you need is the ability to understand the situation and deal with the consequences | ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||
▲ | _fat_santa 9 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||||||||
As a manager the way I approach rules with my reports is I always tell them to understand the "chesterton's fence" behind any rule. I looks at rules like business logic in code, the "logic" was added there for a reason but there are often edge cases where that logic does not apply. I don't tell my reports to either break or follow any particular rule, but to understand why that rule is there before they decide if they need to either follow or break it. And from personal experience i find that when you give people that level of autonomy, they will almost always approach what I told them about rule breaking in good faith. | ||||||||||||||||||||||||||||||||||||||
▲ | nearting 20 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||||||||
> Here's the dangerous way I put it that I only tell senior people: understand why rules were made and make sure the people who made them would be happy. If you aren't absolutely sure those senior people know what they're doing, the this is a great way to end up with originalism. | ||||||||||||||||||||||||||||||||||||||
|