Pros
there isn't much a pro working here other than job stability
Cons
outdated mindsets, standards, processes that causes so much bottle necking for work. Lots of teams just like to blame others when problems come and unable to realize that a lot of the problems are actually from their own teams. People cannot communicate well, so many last minute meetings, actions for things that had plenty of time to do. Managers are not transparent with deadlines, processes, goals with their own team. My previous manager likes to micromanage (common case here), would not listen to opinions, assumes you know it all and everything is easy and takes no time for you to finish. Likes to deny team members and cannot provide any support to the team other than to complain at them all day, but sucks up to upper management, like a puppy. It is 2024, why are we still using email chains to manage workloads... JIRA boards do not exists I guess (even though CIBC has) Some teams really do not need to exist, they are the PROBLEMS of why bottlenecks exists, imagine building a CI/CD pipeline but it is so restricted that the yaml, config files HAS TO BE in a specific format with specific keywords and spacing, else it breaks the pipeline to deploy. I guess I have a different understanding of what CI/CD pipeline are lol. Imagine having a team just to perform deployments to staging and when the pipeline fails they just send the error logs to other teams to get it fix, when they are responsible for the deployment. They do not even look nor try to understand the error.