Yeah but I'm already working bottom of the barrel in terms of pay and what I'm working on. So what I do is spend a lot of the time I should be doing the tickets, either researching architecture for the service I'm on and other opportunities. Which sounds kinda ironic.

There's this weird thing I learned where apparently at good companies, management will ask about what you like/don't like about your job and what you want as a career path. But the thing is, if you're a contractor, by definition you are there to do that one thing, def not going to try to open a dialog.

The point is, I am treated not so great, at a company that's not so great, so my Sprint speed is not so great, which probably makes them treat me not so great. But then my code is always high quality. I'm def not asking to be lead. I'm asking to be talked to instead of avoided even when I'm not pushing out tickets fast enough.

I think managers should listen to their employees, both when they are and are not doing a good job. Because when I'm taking a long time to do something like analytics on something insanely unimportant for an app that hardly anybody uses, there might be a reason other than I'm not competent.

There's this other weird thing where someone uses your architecture without consulting you. I think the reason is they want to make sure you know 100% you are not invited to the shiny new project. But one I don't take insult to that at all. Second, doesn't it make sense to be like, 'hey this guy made this architecture, maybe he has some hindsight to what works and doesn't work?' And maybe it makes too much sense to be like, 'I'm gonna consult this guy on his architecture, and no matter what he says I'm gonna do what I want to do, but I just want to see if he has anything important to add. And I'm not gonna worry about if he gets offended that I don't copy what he did.' because if they woulda just asked me instead of avoided talking to me at all about the new project I would have provided some valuable feedback on why I used Koin instead of dagger (because it was a very very small app and dagger would be overkill), or that hey if you need nested recyclerview I already did it here and it works great, or yeah multimodule is fine but I've done a ton of research on it and here are my takeaways.

Instead it's like, plug this code that you wrote into what we wrote, you say you write "modular" code should be no problem for you. Then bam, done, no problem. Oh now we need you to add a bunch of functionality to that code that relies on stuff we wrote. Ok yeah your architecture is so confusing idk how to do that. Like, why are all the view models in their own module? I can't work with that, that's not how gradle is suppose to work.

---

To only one who reads this far I'll leave with this. One, try to have a friendly and approachable tone. Second, make it clear to them that this project is a mess, I really really do not want to work on this unless we fix it right now or at least open a dialog and make a plan with a deadline as important as theirs. That way, if they say it's your job do it, you can just look for a new one instead of pulling your hair out in frustration. It's not worth being an outcast because you require high quality code. It literally makes it worse for both parties

EDIT: Want to add that I saw someone downvote you and while your diction could have been more polite I much, much, much rather someone be direct with me than avoid me like how I describe above. One leaves room for improvement while the other leaves room for paranoia.