The senior dev having a grand vision of the perfect architecture and overengineers three trendy design patterns into an unmaintainable mess.
I have seen bad VIPER, two different kinds of promises, a reactive framework in one application that originally had a very sensible object oriented approach. All of this crimes by seniors who think the my are very smart.
Oh, there are those as well, I’m not dunking on juniors.
It’s just that my problems always tend to be caused by mismanagement of people.
Like just today I had to clean up after a “let’s do a quick and dirty experiment, oh it works so now it’s production, make 200 more features in a month built on top of the quick and dirty let’s just try it code, what do you mean we lost millions because of a regression nobody even noticed” situation.
The problem is that so is the junior dev they hired to do the two seniors’ jobs who left for less inhuman pay.
Code problems are usually people problems.
The senior dev having a grand vision of the perfect architecture and overengineers three trendy design patterns into an unmaintainable mess.
I have seen bad VIPER, two different kinds of promises, a reactive framework in one application that originally had a very sensible object oriented approach. All of this crimes by seniors who think the my are very smart.
Oh, there are those as well, I’m not dunking on juniors.
It’s just that my problems always tend to be caused by mismanagement of people.
Like just today I had to clean up after a “let’s do a quick and dirty experiment, oh it works so now it’s production, make 200 more features in a month built on top of the quick and dirty let’s just try it code, what do you mean we lost millions because of a regression nobody even noticed” situation.