|
|
|
|
|
by Cube189
2355 days ago
|
|
Never been in a project that took all those rules into consideration. Usually, when pointing out the issue, it was me who was supposed to defend my point as opposed to the person who wrote the code (or my comments got ignored altogether). |
|
> it was me who was supposed to defend my point
Professionally, on the other hand, it feels like I'm screaming into the void, or sometimes at a brick wall. It's deeply frustrating, it's basically got to the point where I just stop trying to change anything for the better, agreeing to whatever inane changes they want to the code (even when I can see the clear disadvantages that will hurt them more than me but they want it anyway), never bothering to disagree with anyone more senior, basically being a yes man for code. I've occasionally been able to work on something brand new, where I have a little more control over the quality.
> opposed to the person who wrote the code
Getting someone to change code they "own" always seems to be impossible too, no matter how tactfully you approach it, no matter how much evidence you present that indicates a design flaw, no matter how well you explain why an alternative is better, it's just so pointless.
The stuff I work on outside of work is usually where I get to write clean code.
> (or my comments got ignored altogether)
Basically, it boils down to this. I don't know how people cope with it, at times I feel totally hopeless about it. I see people sprinting towards the cliff edge and no matter how much I try stop them, they are determined to keep going. Sometimes it feels like they double down or deliberately do the opposite of what I'm suggesting.
It's a totally uphill battle, some people just don't want to listen. I'm all out of answers.