ABI Speaker’s Corner
Three of our own from BNY Mellon were invited to speak at the ABI Speaker’s Corner, right in the middle of all the action of the career expo. Quick 10–15 minute lightening talks provide our leaders, Gabby Szasz, Lucille Mayer, and Rosemary Wang, an opportunity to give the inside scoop on the work being done at BNY Mellon!
QA in an Agile World — Gabby Szasz, Head of QA Community of Excellence BNY Mellon
Agile doesn’t solve world hunger, even in QA! It’s not the answer to everything, but how do we make it better? How does QA work better with the rest of the team?
At the beginning of the cycle, dedicated team members who understand the requirements — small chunks of functionality- during the entirety of the sprint are a necessity. As a whole, we need to work to change the behavior of our executives, the developers, and of QA — become more transparent & become closer to the business. Automation and collaboration are key.
How Digitization is Changing Corporate Culture — Lucille Mayer, CIO, Client Experience Delivery & Head of Innovation Centers at BNY Mellon
Take a look at Uber and AirbnbEng and Instagram — these companies are overtaking the long standing, more traditional organizations. They are built for speed, scale, and innovation. So how does a 232 year old company keep up?
Transformation and Innovation.
We are changing how we work to be more successful focusing on the process, digital platform, and people. Between our Innovation Centers around the world and our NEXEN platform, we are growing from a supplier into an ecosystem driver.
Our NEXEN platform is designed to achieve consistent access and experience, to provide user and developer communities, reusable components, and an open platform for external contributors from around the financial services industry.
Microservices — Rosemary Wang, Lead Systems Engineer/Programmer, Infrastructure Architecture at BNY Mellon
Microservices are a kind of software architecture, just like a food recipe. There is no one-size-fits-all software architecture, it depends on the use case. The counterpart to microservices are monolithic architectures, similar to pizza. Monolithic applications have a shared database and messaging (crust and cheese, respectively). If a topping goes bad and you’ve already made the pizza, you ruin the entire pizza. Similarly, if you do not like an existing topping, it takes a lot of effort to replace with a new topping. This describes the failure behavior and agility of monolithic applications.
Comparably, microservices are like sushi. Each piece can be unique or you can duplicate it. Each sushi (microservice) has its own rice (database) and seaweed (REST API). If one piece of sushi goes bad, you only have to remove that piece of sushi, just like a microservice doesn’t affect the remaining services. Similarly, if you want to replace a type of sushi with another, it is easy to take it off the plate and put the new sushi on it.
A quick update on the booth: Our partnership with FEED is providing 10,000 meals to the World Food Programme — swing by #2321 to pick up your bag!
Interviews are also well underway- here at the conference, talent is endless and we are excited to find the next generation of leaders!