Don't ever start pointing out things that need improved two weeks on the job. Even if you're Developer #2, you simply don't have enough background knowledge of the systems and processes in place. The absolute best case scenario is that you're 100% right and come off like a know-it-all ass. Worse and more likely scenarios involve you missing key aspects of the business, or regulation, or something else that everyone is already aware of, and you end up coming off like an incorrect know-it-all ass.
> But I don't like to criticize without showing a better way, so I decided to immediately start fixing the most glaring issues that I had observed during my initial contact with the micro-service I had been working on.
So now you're getting paid to do work nobody asked you to do...
> I broke up the work in separate pull requests and hoped for some help from the guys to make sure the assumptions the tests were making were valid.
And taking up other folks' time in the process...
> That's when my relationship with the team started to degrade.
Not the least bit surprising.
> his knowledge of the Java runtime was clearly very limited. This lowered my confidence in his general expertise significantly.
I know Cassandra is written in Java but do you need to be a Java expert to also be a Cassandra expert?
> I started responding like "This is just not true", "I don't believe you"
> I could not imagine a database that does not provide such basic functionality as paginating over the whole data in a table!
> if he was so expert, maybe he should be writing the code
> that from someone who did not write a single line of code to help us
> like any civilized database client would
> I was accused of being stubborn and never changing my mind
> Well, I AM actually stubborn!!
> This accusation lead to another confrontation where I became aggressive
There's a saying about right-of-way with regard to driving, something along the lines of "you can be wrong and alive, or right and dead," the point being it's sometimes best to let someone else go when you have the right of way if they're not paying attention, etc.
The author seems much more interested in being right than being a good teammate and good employee. The language in this post makes it clear that he was smarter than everyone else, they're all idiots, and their code is garbage.
I don't care how smart or technically skilled he is, I'd never want to work in the same building, let alone the same team.