Yes. My take is they are reshaping the way things are done, it looks good on paper, and to bosses or share holders, it places more emphasis on middle manageme

Yes. My take is they are reshaping the way things are done, it looks good on paper, and to bosses or share holders, it places more emphasis on middle management for when things work well, less on the mere grunt(s) pushing out the code. Over all I look at this as if it were a job inside a factory or work shed. An employee is coasting, long in the job, they are independent and performing well and probably understand their area more than any other employee. The new team have arrived and have decided to install the latest ideas even if they're not entirely appropriate, but it's what's wanted, and the updating process might allow the new team gain a better insight. It's a win win for the new team, since the process will allow them to see something familiar as well as appearing to be implementing the new way of doing things. (Not that I greatly understand it, but IMO the microservices architecture fad is just that, something new, but as I understand the concept, a lot of scope for trouble and security issues that will be hard fought behind the scenes.) However it enables the new team to make it harder for the old employee to coast along, because not only are they continuing to do the old job, they now are pressed for time to utilise so that they can build towards the new system. To add insult to injury, any pertinent questions the employee has about their new direction are sidelined by various tactics. The employee is not being treated well and ultimately being marginalised.