Java – how to handle inept management

A project I am working on has been completed, so I have been transferred to some new tasks by my employer Previous work was very agile, small team, program progress, etc

Anyway, I'm working on a new project - I find myself confused about how to deal with management They have no real understanding of object - oriented programming, current technologies or methods They seem to be afraid of change. Recently, we moved to the latest JRE

We did these code reviews, and I had to listen to "gray beard" about how good it was in Ada, or what they used to do with C But when they try to write reviews - they lack even the most basic understanding of OOP design and development, and they pay more attention to the style of code; Spacing; Method name; wait

One of the senior staff said that we should write our own recorder instead of using log4j, because log4j was negatively commented in the academic PDF a long time ago

What should I do? How can I explain to them that their design is wrong, or that they are really behind the times, rather than being an asshole I've worked in this organization for about a year - so I don't know how much credibility I'll have

Solution

About code review, I want to say make them happy Name and space the way they like Of course, focusing on better design and enjoying the memories of ADA can still provide you with some background of today's things and how they get there

In other words, don't take that part too seriously Worry about the importance of completing the work In this case, the job is to make important people feel that you have made a positive contribution to the project

Regarding log4j, I just suggest a different framework Built in JDK logging (can't complain, it's a built-in API) or something like SLF. It allows you to insert anything you want (including your own, I guess, and then you can discard and replace it. When they realize that this is an error, they just need to change the classpath

Now sometimes it's important In this case, try to make it sound like their idea For example, in logging, it is declared that there are many logging frameworks representing many lines of code, and you want to know if there are other ways to take advantage of the work of the project, and then let them "figure out" the solution

Sometimes you have to come up with some ideas - there's no other way In that case, stick to the evidence, build relationships with those with good reputation and influence as much as possible, and realize that you will fight every battle and lose your position even if you win (perhaps especially if you win)