3 ms·

I forgot to add that my manager might be cosidered a "micro-manager", I've heard him tell other developers that they should change a single variable name. and r

by _RPM 13y ago

I forgot to add that my manager might be cosidered a "micro-manager", I've heard him tell other developers that they should change a single variable name. and re-commit. Another thing that I've noticed, and that has happened > 1 time is that I'll write something, spend like all day on it, then come to work the next day to have found out that the manager re-wrote it claiming "simplification" of the code, which is in fact not true, or claiming my code had a "bug" These bugs aren't security bugs, or anything for that matter. Their small user permission things that I was never told about and is not documented. I don't care if I can't work on something, but if you want to do it, then do it, don't ask me to do it, then re-write it because I could have been working on something else in that time.

imdsm 13y ago
That is part of life though, and as frustrating as it is, you'll sometimes have to expect that other people will rework your code.
- room271 13y ago
  It is, but it's definitely not a good way to treat new people to the team, especially people on their first job. Much better to explain the bug/problem and let them fix it.
  - imdsm 13y ago
    Very true, again highlighting some of the flaws of OPs current workplace.
neilk 13y ago
> I've heard him tell other developers that they should change a single variable name. That is totally legit, if there is a naming convention in place on the project and the developer violated it. If it's just his personal caprice, then yeah it's dubious, but better an idiosyncratic dictator than no standards at all. > then come to work the next day to have found out that the manager re-wrote it claiming "simplification" of the code, which is in fact not true This is extremely common. You've already documented how this shop has no good procedures, so people waste a lot of their time rewriting stuff. I hate jobs where I have to be someone else's extra hands. It's a sign of poor organization on every level. That said - I hope as an open source programmer you've learned not to get attached to your code.

by _RPM 13y ago

imdsm 13y ago

That is part of life though, and as frustrating as it is, you'll sometimes have to expect that other people will rework your code.

room271 13y ago
It is, but it's definitely not a good way to treat new people to the team, especially people on their first job. Much better to explain the bug/problem and let them fix it.
- imdsm 13y ago
  Very true, again highlighting some of the flaws of OPs current workplace.

neilk 13y ago

> I've heard him tell other developers that they should change a single variable name. That is totally legit, if there is a naming convention in place on the project and the developer violated it. If it's just his personal caprice, then yeah it's dubious, but better an idiosyncratic dictator than no standards at all. > then come to work the next day to have found out that the manager re-wrote it claiming "simplification" of the code, which is in fact not true This is extremely common. You've already documented how this shop has no good procedures, so people waste a lot of their time rewriting stuff. I hate jobs where I have to be someone else's extra hands. It's a sign of poor organization on every level. That said - I hope as an open source programmer you've learned not to get attached to your code.