I usually reformat, or completely remake, my team's work... Is it too bad?

You're wasting time on stuff that already works.

I know the temptation, i did the same on some cases, partly because some older stuff doesn't comply with our new style guidelines and i can't bear seeing 299 warnings all the time.

@CWins I do that maybe because I've found a better way to do that, or a more scalable system.
I do that with my own code too, and I should stop because I'm wasting a lot of time even though I'm working on a better system

Why bother with a team? get the suits to sack the others and combine their salaries into your own.

@helloworld I'm actually the leader of the team, I mean, the lead of the project

Sounds very familiar 😒

@HAlex
Stop doing it.

@D--M oh, ok.

Why not teach them how to do it themselves and save a lot of your time for other stuff after they learn?

@ameware well, I tried... "Follow the conventions" is what I always say,
the idea is: "We should make it modular, as error-less as possible", "The system should only be restarted if it is crashed"

@HAlex seems like a healthy approach, so why won't they listen? maybe they got stuck on something and decided to drop it and code their way?

@ameware I guess so...