mjander writes "About 2 years ago, a taskforce initiated by myself among other colleagues started a software project. From the beginning I had a very clear architecture picture in my mind. I explained that to the taskforce and everyone agreed. Since nobody had time among other excuses, I proceeded with the core part of the software coding itself as well. I did not really wanted to, but it was not much work at all, and I also wanted to make use of the new thing.
Some time ago a colleague which was not really active on this project when it started, know is trying to take leadership, taking decisions without telling anyone and checking them in, prohibiting use cases to other colleagues, blocking access to the software repository to any person he decides and messing up the entire architecture. This colleague is of the type of programmer that sits down and starts coding without any plan. Aspects as cohesion, coupling, dependencies, what ever are turning into a mess beyond good and evil. We even had some training on software architecure some time ago, but despite that it did not help to increase any awareness on the matter. He talks about it, but prooves that he does not have any clue on a line. He prefers to take decision on "how it feels". Its very frustrating to see how that project is being messed up without hope to make him to understand. I'm somewhat scared to talk to our boss about this. The project is becoming more and more an important part of our productive process, so I think it is even more important to keep it clean of clutter and conceptual nonsense.
Any suggestions what to do ? I don't like what this colleague is doing, but I don't want to end up in a war with him, and others taking party either.
The other thing is that I was designated to be the software architect on another project. The first time at where I do work that somebody is called like that. It was not my initiative to do this, but I also believe that I'm the fittest for that task. If not, I should definitely quit on that task I guess. This may also be causing some sort of envy perhaps, despite there is no reason, since there was no big announcement, nor do I get more pay.
Has anybody experienced a similar situation on the way to senior engineer ? Any thoughts to share about ? Or is this the ominous midlife crisis ? Thanks."