 Hello everybody, I'm glad to be here and I will dedicate the next five minutes of your life to a conversation or a speculation, if you will, about a perfect Cloud Foundry engineer. But before we start our conversation about a perfect Cloud Foundry engineer, I would like to speak a little bit about a perfect Cloud Foundry deployment. So imagine yourself moving into a new house. You come in, you do a tour, you like big rooms, you like automated garage door, you like that the kitchen is fully functional, and you decide, okay, I like it, I'm moving in. And quite soon after that, you understand that the water is leaking, that the garage is too narrow for your car, that there is some terrible smell in the bathroom. And you can understand what kind of disappointment my developers feel, who just onward to a new shiny Cloud-native platform, and they have issues with logging, they don't have proper services configured for them, they don't have CI-CD pipelines set up, and it happens quite often, we can see this in organizations that rush into scaling out the Cloud-native platform. They have goals of migrating several hundreds of applications to a new platform, several dozens or even hundreds of developers, and they make a mistake of growing too aggressively and not trying to address the requirements that the users have, and not being attentive to what they want to have, what they expect from the system. There could be an opposite situation when organization is just moving from one PUC into another PUC into another PUC, another PUC, and nothing happens. Another type of an issue that we often see is insufficient preparation for surviving a disaster. Companies rely solely on Bosch, that Bosch will solve all our problems, but they don't do proper testing, and actually Bosch is not technology that covers you from everything. There could be a situation when software engineers are not sufficiently educated about what platform can do for them and what developers have to do to take the benefits of the platform. In this way, they just stop using it and continue doing the things the way that they used to do on their old infrastructure, with their old methods, and often we see that engineers deploy their applications to cloud native platform, but they do this in their old way without addressing those 12-factor bullshit. In order to understand what kind of skills we expect from cloud founder engineers who do the deployment, who do the support, let's think about what are the activities that those engineers have to spend their time on. And its deployment, its maintenance, education of users, their teammates, its monitoring of a platform, its building high-level infrastructure, ensuring proper security, providing buoyant manifest, and in order to ensure resilience and portability, they develop Bosch leases. So what actually is the knowledge that we expect from the candidates who are applying for cloud founder engineer position we expect to have? They need to be proficient in infrastructure as a service, maybe some of those. They need to understand the continuous integration, continuous delivery concepts. They need to understand what 12-factor apps is. They need to work with versioning, with the source controls. They need to understand the concepts of disaster recovery, of cloud applications, high-level ability, networking, performance tuning, virtual and understand what is the difference between virtual machine and container. Some candidates just don't understand it. Besides that, they need to have soft skills, such as communication, understanding of methodologies, software development life cycle. They need to be good in coaching, mentoring, be a good team player, dedicate sufficient time for their self-education, be curious, proactive, have good problems with skills. And finally, they need to have a correct mindset, a possibility to see the big picture, understand the constraints of the organization they work at, help driving cultural change inside the organization, and being realistic, that's my favorite. And now, when we find the right candidate with the right mindset, right ground-level skills, we will teach them about cloud foundry. And we will teach them about this new shining concept that they don't know, these components of cloud foundry such as, I would just scroll down, and also, they need to know cloud foundry a system. And finally, and finally, they need to know how to configure all this stuff. So we are getting a kind of universal soldier, a man with many, many heads. And to give you some piece of useful information, this is the percentage of the time that they have to spend on acquiring those types of knowledge. Take a picture, moving on. So the choice is, do we want to have universal soldiers, do we want to cultivate those universal soldiers in our organizations, or we want to have a team of specialists, some of those will be specialized in deployment. Some guys will be proficient in login monitoring, disaster recovery, some guys will be good at writing service brokers, that's up to you to decide, whichever route you choose to go, either to have a man with many, many heads, or have a team of specialized professionals. And Altos can help you with providing a training platform. It's in beta, it's free, please go in, register, give us your feedback. It will be going into the production very, very soon. Would appreciate your input. And we're also here to help. Thank you very much.