I had a "go to" guy quit my team. This guy always came up with new frameworks, technology, and all engineering stuff. Anyway, he did not really knew about these tech stack and always over engineered everything. Since he did not know the stuff and loved over engineering things, he applied so many things in the wrong place. He wrote one code pattern in one place, and another pattern in another place.
This guy is respected by many junior engineers in my team and I have a feeling that they think we lost a good team member which is obviously not the case. After he left (about a week ago,) our work progress is much faster compare to when he worked in the team and touching code here and there.
I do not want any of my team members feel that we lose anything. In fact, my team is much more productive without this guy. Should I address this in a team meeting by stating facts and reasons why he was out? or Should I just not say anything? What is the best thing to do in situation like this?
The reason I felt I needed to address this was because he was a "go to" guy for few engineers. He talked as if he knew everything but he did not. I just did not want these guys to feel bad.
What I did was, I waited until a weekly team meeting and told everyone that they had done a great job and I was so proud of them. A couple guys who picked up his code realized that it was badly design or over engineered.