system
Given the following post, respond as if you're commenting on Reddit:
human
AITA for having a different coding "style" from our senior?

Our team: two junior (me and my mate), one senior engineer. 

Project is a backend in java for a web application in a IT company of 20 people. We are based in a medium size city, so not a big tech place.

My mate loves clean code rules, he avoids creating long methods and instead breaks down the code in smaller methods with suggestive names. I became a fan because its easier to understand.

I like to use lambdas instead of passing an anonymous class as a parameter to a method.

Our senior hates our approach because, in his opinion, breaks code consistency. 

We are designing new endpoints and usually the senior's handler only has a single method of 200+ lines. He also doesn't use lambdas. 

We feel that we aren't breaking code consistency and that he is being to uptight and protective of his code but since we have little work experience, we aren't sure if we are reading the situation correctly. 

Are we assholes for not wanting to comply with his rules?

Edit: to the people down voting - please also leave a comment, I'm eager to read your reasoning and learn from it.
gpt
When working on an existing project, it is customary to follow whatever style the project uses.

In some cases it's fine to change some things, especially when the language as evolved. In your case, writing smaller methods and using lambdas doesn't seem too bad, but the final decision is always in the hand of whoever manages the code-base.