This bitch at work is afraid of hard work and is currently spending more energy fighting the work than just doing it.

She wants to keep a legacy setting that's on the wrong scope -- per merchant, not per payment -- in addition to the setting I've added on the correct scope. She's bringing in management two levels up all because "I've already moved on from this" and "it will require me to write code quite a bit" (first paraphrased for clarity, second is an exact quote)

Bitch, your way is dirty as fuck and is going to break things. Roll up your sleeves and do your damn job!

Lay down the law @Root!!!

A feels bad moment.

It will require me to write code quite a bit?!?!

Wish I could use that as an excuse for not doing something...

Well, I have fucked up feature requests, that add things on fucked up scope too becouse they want super granular controll over everything going inside system. So, I had something that was not for 2 levels like here but for 3 levels + ignore setting flag, just in case. For every level of "wtf-ness".

Only difference is I work as solo dev in smaller company.

E: brainfart => wrong word

Boss sided with her.

I offered to add deprecation comments explaining not to use the incorrect-scope data, but he insisted i shouldn't "push the issue." So now it's both cruft and a landmine for any future devs.

I'm pretty pissy.

Also, some of the bitch's code is wrong.
and she actually, intentionally doesn't add coverage for some areas, and this is one of them. That's only half true: parts of it intentionally have no coverage, part of it has coverage from bad tests because she wasn't listening. It makes me laugh seeing her shoot herself in the foot. I just wonder how she's going to try blaming this on me 😅 I fucking hate her.

To make things better still: because I insisted on doing things properly, it uncovered a bug in her code that would have made it to production and caused all API payments to fail. The mess it would have created also would have required a lot of cleanup effort. Instead of being thankful that we caught it prior to QA, she's pissed off that she has to come back to the ticket and is trying to blame my changes for it.

Fuck her. I hope the corona scrambles whatever eggs she has left.

I do love me some juicy office drama first thing in the morning.

But nothing rides my rails... pun intended... like a lazy dev who won't fix a problem because it's hard work, or maybe I'm the crazy one for going out of my way to fix it🤔

@Root, maybe let some of the large impact, low effort bugs through and have a patch standing by?
Enough of those bad boys should get people's attention.

@C0D4 this isn't a bad idea to have patches ready to go for when it fuckes up.

I normally just write a test proving something is broken and as our pipelines fail to deploy if the tests fail it very quickly get attention.

@C0D4 I has forgotten what office drama was like. (Apart from managers). I miss the ignorance.

.

Dirty job from a dirty whore...

Where is ruthee when you need one for the jokes?

I usually write a ticket for bugs that can be 100% reproduced after a person that worked on it (last) is refusing to acknowledge the issue.
A simple GIVEN / WHEN / THEN works just fine. So when it hits the fan you say "ta-da".

A bit irresponsible but works as a last resort.