I didn't say directly that their code is bad. But asking is futile, communication is bad. They dont want to make it a prio and 8 hour time diff makes it hard. I spent too many nights up to have video calls about it.
But you're advice aligns with other people here. Regardless of he sate, I should be help drive it with refactors and just deal with it indeed.
This resonates, I also suggested that I might not be a good fit as I dont think the result impact is there.
This was probably not good career move here, as it is being discussed higher up.
But I honestly am unable to create impact with this codebase. This could also just mean that I am not fit for the job and they need other people.
I do understand the goal tho, that's why I raised the issue that I cant deliver enough impact in my eyes. And I think it's the right thing to raise.
Thanks for your reply, it now makes sense that quality is not a goal. At my level I should be able to work with this instead of just complaining.
I'm frustrated for sure. I am looking for some pointers tho.
How do people handle this "patch on patch" code. It reminds me a lot of the sunken cost fallacy.
How do you approach this to the people who wrote it?
I didn't say directly that their code is bad. But asking is futile, communication is bad. They dont want to make it a prio and 8 hour time diff makes it hard. I spent too many nights up to have video calls about it.
But you're advice aligns with other people here. Regardless of he sate, I should be help drive it with refactors and just deal with it indeed.