4 ms·
This is weird. Author wants me to agree, that I have to unconditionally submit to someone because of their title. No ifs or buts, just do as you're told. I work
by DominikD 9y ago
This is weird. Author wants me to agree, that I have to unconditionally submit to someone because of their title. No ifs or buts, just do as you're told. I worked with people who loved to manage like this and in every single case when they asked for a wrong thing it was later developer's fault that he did something (it's his name on the commit after all). On the flip side every competent, cooperative manager I've worked with had no issue with people not wanting to do something. But yeah, YMMV. Perhaps in some bizarre world "I command you to do X" is the civilized way to talk to other people.
- naasking 9y ago> I worked with people who loved to manage like this and in every single case when they asked for a wrong thing it was later developer's fault that he did something (it's his name on the commit after all). So log your protest and the command in the commit message too.
- DominikD 9y agoTelling people "I demand that you do it" or even "do it, or else" is a symptom of a greater problem with said person. I don't see how waging battles with this type of lead in commit messages is going to help me.
- naasking 9y ago> I don't see how waging battles with this type of lead in commit messages is going to help me. What a weird way to phrase it. The problem as stated is that the developer gets the blame because his name is on the commit message. If you document that you were specifically instructed to implement this commit, then that solves the problem.