Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'll be honest. I could be that guy giving seemingly contradictory advice. The first one is a general rule. To be applied in most cases. The second one is an advice in a specific situation. The situation might dictate going against the general rule. In that case I can even relate to him asking you to contact him in any case you might want to not apply the general rule. It makes sense for him to keep tabs on the exceptions. If the number of exceptions grows large even (this) might change.

If I read you correctly, I can relate to your side as well. Don't stipulate general rules if their not general. But that would mainly mean the prescription of what to do when (this) becomes not a simple rule, but a handbook. I fear the workplace with handbooks for (this) and (that).

It's a matter of leadership style and personality as well. I like clear rules. I over-generalise for speed. I like team members who give me hell for anything they don't agree with, up and until the moment we decide what to do. After that I want buy-in. Quite some people don't work that way and it's up to me to notice that and relate differently.

My final tip for keeping sane in an office environment is to never attribute to malice etc. Most environments aren't toxic so don't expect toxicity when you've not yet encountered it. If most people would act that way, the world would be a better place. Act strategically only after someone has proven to act with bad intent AND you've taken the time to try and talk the situation over and have not resolved it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: