I work with programmers who can only think in terms of SOLID, design patterns, abstraction layers and who want to interface everything and their grandmother.

Although I know there is some merit to applying patterns where needed I also feel more connected to extreme programming and like to think about something from a usability view.

For example whenever I have a controller with a request in PHP I would like to set my session variables like so:

$request->session()->put('key', 'value')

This leaves my coworkers in shock in horror because they are programmers to the bone who only think in setters and getters. So obviously their major improvement would be:

$request->getSession()->put('key', 'value')

I am getting sick and tired of constantly bickering about this but I feel there is value in the readability and simple use of how I like to write it. Frameworks like Laravel have gotten huge because of the simple things like this. At least that's how I feel like.

You will no longer differentiate between a setter and getter once you have written your core logic because it will be set in the application logic before you even touch your controller. So it would not make sense to use a getSession() anymore. Their counter argument is ofcourse that everything needs to stay in line with eachother so everything should be getters and setters with get and set prefixes.

I value the tiny things but I can't seem to change their minds because programmers will be programmers. I guess I needed to vent but how you encountered something like this before?