


So, you are tasked with building the architecture for a new product... where should one begin? A good Product Manager knows the right questions to ask at the beginning of any project, like, how do you build a system that lasts? What about balancing stability and agility? Speed of evolution...
So, you are tasked with building the architecture for a new product... where should one begin? A good Product Manager knows the right questions to ask at the beginning of any project, like, how do you build a system that lasts? What about balancing stability and agility? Speed of evolution and code quality? Preparation aside, it's also key to remember...
“The only constant in life is change”-Heraclitus
Join this virtual Q&A with Yana Nikitina, Director of Architecture at Braintree to learn the principles for future-proofing your architecture!
In this talk, we will cover:
As Director of Software Architecture, Yana builds robust solutions for Braintree. She is passionate about finding the best solutions that are lean, scalable and future proof. She is a holder of multiple patents in Fintech and medical technology sectors.
Outside of work, she enjoys travel, hiking and exploring.
She is in her element when seeking the ideal solutions for problems and bringing people together from diverse backgrounds to achieve a common goal.
What would you emphasize in Cloud design comparing with on-prem solutions?
How do you see liaisons people such as scrum master or project managers playing a role in the future?
What are common design decisions that are often overlooked at the outset of a project? And how can teams proactively address these kinds of cases earlier in the process?
How do you evaluate your software architecture for Security best practices?
1) What qualities sets you apart from other leaders within your organization? 2) How did you communicate your leadership skills to obtain your current role?
Yana, could you provide an overview of Braintree's architecture? Very much looking forward to your talk.
I've found that there's generally a big push to do only the minimum required when it comes to building security in from the code up as it were. What are your thoughts on this? And how do you...
What advice do you have for someone who is currently an individual contributor looking for career growth into management?
How many itérations of a product is a good number to have in mind when initiating a product platform and the durable architecture that supports it?
How to evolve architecture incrementally?
Do you always design with cloud tech in mind from the beginning?
How does your decision making change when the product you're architecting is nearly 100% pre-validation in the market and is likely to require big changes in response to feedback almost as soon as...
How do you think about upstream and downstream integration when designing new products in potential legacy environments.
Large projects like these are rarely static. How do you adapt to new information that could change the architecture mid-way through the project?
When building new a new product, how do anticipate and manage cut-over related deliverables when designing for future maintainability and scalability? Especially when the cut-over (final rollout...
Do you have any advice for connecting the dots between *knowing* an architecture design principle, and figuring out when and how to actually *apply* it in practice when looking at a given problem?
What tools do you use to check your architecture designs for security, fault tolerance, etc?
Is there a specific question you have for the speaker? Let us know!