Earlier quoted context omitted.
Yeah, like mirko said, being pressured by project leader to merge absolute crap (I was in charge of merging), "because it works and we don't want to suppress less skilled colleagues". "Try to explain nicely how to do it better" while that other guy a) doesn't want to learn and b) has feelings that are more important that making better software / learning. Edit: to clarify, that other guy couldn't understand the proje…
Hey, I don’t know your situation so this may be nonsense, but what you describe doesn’t sound so PC. The guy’s code worked? Doesn’t sound unreasonable that the project leader would want it merged. Put the technical debt on the backlog, get on with writing other code that works. The project leader presumably had a team to manage. Seems perfectly understandable that they would want all their team contributing, even if…
Piling on lots of little bad changes is only possible if you have a good cleanup process (that I’ve never seen, who likes cleaning up bad code that isn’t breaking yet).
I think this may just be different management / development philosophies.