The Minister of Transportation Rotimi Ameji has inspected the obstruction on the track caused by the customs scanner and waybill building around Apapaport. Plus the Africa's correspondent Destiny Momo tells us more on the effort by the federal government in resolving this. On a walking visit to Lagos, the Minister of Transportation Rotimi Ameji inspects rail projects at the Apapaport. Accompanied by the managing director of Nigerian Ports Authority Hadidza Usman, the Minister addresses journalists on his findings. We have problems with some infrastructure that can either be removed or not to be removed. Luckily customs have a center where we should remove them but it's a bit difficult. We're going to the office now to have a meeting to know what to do about it. The second one is there are some cracks at the keys where we'll let the tracks come to inspect it and find solutions to it. While the purpose of the scanner is key to the operations of the customs, the importance of the timely delivery of the project is also jamming to the movement of goods. What will be done in addressing the bottlenecks? It's only when the engineers have come up with a proper solution and time-based solution that I can speak on time. Now I cannot speak on time on when that will happen. You know you can actually commission this project without that because it's not just one track. That's one of the tracks that we're going to fix. So all we're doing is to make sure that out of the three tracks one or two at least can get to the key. So now we can commission depending on when the other ones are completing a set of these challenges we will be meeting inside the seaport. Once they make a decision, it doesn't mean to make a decision. Once they make that decision then we can convey it to the public. The completion of the real project in Appapot will have the track go into the Tinkang port. The train is still operating skeletal services because of ongoing construction work at the tracks and stations. When fully operational it is estimated that the train's frequency will increase and its speed will also increase to 160 km per hour. Destiny Momo for PLOS TV Africa.


It's just insane. We just need to get government out of our asses. 99% of the laws on the books in every government should be eliminated. For the next 100 years, let's say 50 years, every government that comes in to takes control. The only thing they should be doing is opening up the books and deleting laws, getting rid of laws, repealing laws. From taxes to criminalization to everything. Just free humanity. Who are these clowns?


It came out right after Planet of the Apes. So I was a little bit on your list. Yeah, yeah, yeah. Number three thousand seven hundred and fifty. Yeah, I always think of the sea. You've seen Road Trip, right? Yeah, yeah.  And he's like, OK, whole or take this note down. And the guy's like, yep, I'm rained it down right now.  Oh, good.  All that's going to hear where I really love when they do a point where it doesn't even make sense in the context of the scene, but just adds an extra element. Yeah, on that note, I think, you know, on a note of road trip, how every conversation should end. Classic comedy from the fifties starting with the name Stifler. Tron William Scott, who I believe was was from my old stomping grounds in Minnesota. Yeah, we should end there. Cody, this was awesome, dude. Yeah, I had fun. You want to you can pick your channel one more time, I suppose. Yeah, if you guys just go to just search Cody Leach on YouTube, you'll find me at the name of my channel. I'm going to have a mission of possible ranking at some point tomorrow. That'll be kind of the new blood. But I just reviewed the newest movie a couple of days ago. And then we got Barbenheimer next week. So Barbenheimer. Yeah, I like it. Are you going to review them together in the same video? I don't know. That's an interesting idea. Maybe I'll wear a Ken shirt when I review Oppenheimer and then I'll wear like a nuclear physicist suit when I review. You could kind of do a hazy thing and just, you know, profile yourself profile yourself. Alrighty, that was Cody. Cody, this was awesome. I'm glad that you decided to come on, kind of like out of nowhere today. Appreciate you taking time on your schedule. Check out his channel. Of course, if you somehow came here from Cody's because, you know, you're awesome like that, subscribe to mine as well. I post movie content every week.  There's enough of that in the world. I just focus on movies, giving you my honest takes, trying to make you laugh. And hopefully you get something out of it. Because I didn't go. Alrighty, later, dude. And in broadcast, it's still.


How did I become interested in baseball? Wow. Was I ever not interested in baseball? I played since I was four years old, I think. I can't remember a time that I wasn't interested in baseball. I think there's probably no object in American sports that has as much ritual associated with it, has as much meaning associated with it, and has evolved as much over the course of the game. And there are a lot of stories to be told about economics, about manufacturing, about ideas about masculinity that come through the glove. And so it seemed like a natural object to study. The game was so different before there were gloves. I would find references to games in which there were 10 hits and 20 errors in a game. Now, today the average number of hits per game is probably about 9 or 10. The average number of errors per game is half an error per game. So if you think about something that's changed the game of baseball, nothing more than the glove has changed the game in the same way. This is a glove I've used pretty much since I started playing baseball again as an adult. What I like about it is it's designed and made in the United States and the Nikona glove factory in Texas. I also love how it broke in for me. I've had a lot of gloves that haven't broken in the right way and you'll catch a ball and it'll pop out of the pocket. This one, the ball just goes right into the pocket every time. And it's been a great glove for me and I've used it to play all my old man baseball.


Hello. Hello, CubeCon, Tracy from NuVector here, bringing you a little bit of security as code, egress inferno stand-alive edition. So what I'm going to be talking about today is Kubernetes security as code. We're going to take one specific use case and compare it against different ways of implementing within a Kubernetes environment. Those different ways are going to be with Kubernetes security policies, OpenShift, Istio egress control, as well as NuVector egress control, which is a commercial approach to egress control. If you're asking yourself, well, why egress inferno stand-alive edition? Well, that's what happens when you mix the conference theme with disco and throw in a little bit of copyright infringement on the site as well. Enjoy. So first, let's take a very quick big picture view of security issues for containers, Microsoft deployments, and then we will quickly narrow into our topic. Ideally, security is being built from the beginning of your pipeline. You're wanting to prevent vulnerabilities from getting into that pipeline. So you're doing scanning. You're also wanting to try to prevent misconfigurations with Kubernetes, the host themselves. If you are using Kubernetes, then you are all too aware that you don't want to negatively impact the velocity due to network issues or security. Everything needs to be as automated as possible. Once those containers are deployed, there are not only risks from the applications themselves, but now you have the new attack surfaces such as the Kubernetes API, the orchestrator itself, the container runtime, or if you're using a service mesh like Istio, the control or data plane can also be a potential attack vector. And finally, we have all the traditional attacks against applications just like we did before containers, vulnerability attacks, ransomware, crypto mining. These are all serious things to think about. But today I am going to focus on one aspect of security, and that is the connections leaving the container workloads to outside of the cluster. As my granddaddy said, don't rob a bank on half a tank. Getting away is half the battle. So if getting away is worth their time, doing egress control is certainly going to be worth your time. When we're talking about egress control, just just assume that's any connection that goes outside of the Kubernetes cluster, or that's for namespace for Kubernetes. OpenShift describes that as outside of the project. This could be a desired connection to the internet, an API service, a popular domain, basically anything outside of the cluster, even like to a legacy database or something like that. The reason egress control is worth at least 15 minutes of your time is because this is how someone actually makes off with your data. We too often focus on preventing attacks or vulnerabilities of getting into our environments, but the egress connections are literally the getaway car. In order to get the value of an infiltration, the attacker may need to use a reverse shell or connect to a command and control server, or in the case of crypto mining, you need an egress to get your Bitcoin credit. With Kubernetes, egress control can be a challenge because the source IPs of the pods change dynamically when they're spun up or moved node to node. This makes it difficult for traditional firewalls or gateways that need a source IP address to base their policies on. If you're trying to funnel all your traffic through a gateway inside of the cluster in order to egress, that too can become a bottleneck and that can create some performance issues or even obscure the source or the content of the requesting service. For example, if a certain service is allowed to egress coming from a certain pod and that pod needs to be identified by labels or service names instead of IP addresses. So let's take a look at some basic egress controls built into Kubernetes. This will be a very quick review. In Kubernetes, you must be using a CNI plugin that supports the enforcement of network policy in general, and it has to be enabled. Not just using the CNI without enabling it will not allow your network security policies to take effect. This is inner pod as well as egress control. The default is that all pods can egress to the cluster, but as soon as you enable a single network policy, egress control is then enforced. And in Kubernetes, you can create egress control based on a destination IP address or port, or you can block all egress controls. Again, this is a namespace based policy. Now, there are some limitations. For example, you can only allow specific egress. There's no concept of deny to specific IP. So if you've got a block of IPs that are in allow, you can't then ask deny specific IPs within those allows. There's no concept of external outside of the cluster. So you have to specifically allow connections outside of the namespace and then separately to specific services.  So if you're familiar with firewall rules, you know that rule order is important for how the rules are hit so that that can be cumbersome if there's no host name or DNS support. Red Hat's OpenShift extends Kubernetes and adds some nice functionality by using custom resource definition, or CRD, called the egress network policy. egress network policy is able to deploy an egress firewall, which does recognize the concept of egress outside a cluster. You can enforce one egress network policy per namespace, but not on the default namespace. So everything needs to be in a designated namespace. The OpenShift CRD does support the resolution of DNS names and adds the concept of rule ordering. The different rules shown for egress in the example I have here on the right is exactly the order that they will be enforced, much like a firewall. The egress network policy also supports deny rules in addition to the allow rules and has a granularity at the layer four port level. A few limitations. First, the egress control does not apply to routes. So if you're using routes to send traffic from the namespace through the pod to a router, the egress controls will not apply to those routes. Secondly, the egress controls you see here apply to the demo namespace, but notice there are no pod selectors. In Kubernetes, you can do namespace and pod selectors, but in OpenShift, you can only apply namespace rules. And in neither Kubernetes and OpenShift, there is not an ability to verify the application protocol at layer seven for egress. And that's another layer of security that can prevent tunneling or other types of attacks, which try to mask themselves inside of a network protocol. So the ability to verify the application protocol being used, not just define it, but verify it for like say MySQL, MongoDB, SSL, that is not supported. And as noted, the order of the rules here must be set and maintained in the YAML file. A third way of implementing egress rules might be through a service mesh such as Istio. If you're familiar with the architecture of Istio or Kubernetes service mesh products, you know that a sidecar proxy is deployed next to the pod for every application workload and the connections will go through that sidecar proxy. That's how you can actually implement egress control using a service mesh via that sidecar proxy. In Istio, egress is allowed through a sidecar proxy for DNS lookups as well as HTTP and HTTPS traffic. You can see the mesh example here on the right is setting an outbound traffic policy allowing HTTPS egress. You do have the flexibility to bypass the Istio proxy for a specific range of IP addresses and you can implement egress control in Istio via an egress gateway, which will allow access to external HTTP, HTTPS services from applications inside the mesh. A specific use case for this approach might be where a cluster or an application nodes don't have public IPs so the in mesh services that run on them cannot access the internet. By defining an egress gateway, you can direct all of the egress traffic through it and allocate public IPs to the gateway nodes so application nodes can access external services in a controlled way. The limitations of a service mesh, first and foremost, and I'm taking this from Istio documentation, a sidecar proxy is not considered secure and can be bypassed. So whether it's being bypassed for specific IP ranges or for a malicious bypass of the proxy, Istio will not guarantee traffic is going through the proxy. And as I said before, other than HTTP or HTTPS, there is no verification of application protocol. And if you're thinking about using the egress gateway approach and funneling traffic through that gateway, again Istio's documentation says it cannot securely enforce all the traffic that goes through the egress gateway. So if you really want to lock down your environment, you're going to have to probably use a combination of Istio gateway policy and maybe some basic Kubernetes network policies, combine those together to enforce all the traffic is going through the gateway and denying all of the other egress traffic, perhaps a little bit more prone to misconfiguration or potential unknown holes that allow egress that you may not be aware of. And finally, the performance considerations of a sidecar on every pod enforcing egress or funneling all of the traffic through the gateway, depending on your application performance, that could be an impairment there. So now let's take a look at a fourth way of doing egress control, and that would be with a commercial product called NuVector. NuVector is a container security product that can enforce network egress control policies based on IP address, source destination for applications running outside of a cluster, or DNS names that can be resolved. NuVector also verifies the layer seven application protocol provides support beyond HTTP and HTTPS to include TCP, UDP, DNS, and others. Also provides granular egress rules beyond network IP addresses or host names, but that also use the container native deployment names, labels, or groups of namespaces. And it can also be combined with process security roles and file access security roles. And so if you're asking, well, wait, how can I combine network security policies and process and storage slash file access together? How does that work? Well, so NuVector also uses a CRD, much like OpenShift, a custom resource definition that allows for there's the NV security rule that allows for egress, allows for ingress at the network level. And so that's both allow and deny rules, the layer seven protocol as well as any ports. NuVector also implements file protection or for specific file locations, directories, as well as process protection, basically blocking any process that hasn't been seen before. NuVector uses different policies. There's a discover mode that automatically learns all the processes and all the network activity so that you don't actually have to write this YAML file. It can be created automatically. It can be exported and applied to other clusters as security as code. So a quick summary for NuVector security as code allows you to define specific application behaviors in Kubernetes native YAML that can be exported and applied to multiple clusters with the same applications, same rule sets automatically learns the processes and network activity and you can add file system activity protection as well, integrates with our back, makes it easy to move rules from one environment to another and supports OPA and other integrations. So here is a quick summary, egress control comparison between the four. Feel free to screen cap this particular slide. And finally in summary, definitely should be looking at egress control. Again, it's half of the robbery. Lots of good ways to enforce via open source. Lots of good ways to enforce with commercial products such as NuVector. Definitely consider your egress as part of your segmentation strategies and include that process file protection as well. Basically assess your risks and apply security where appropriate. So thank you so much for taking the time to get through this entire video. Much respect. Hope you're having a great conference from everybody at NuVector. Thank you.


In the last 12 months or so, I have been working at least 12 of our key customers and trying to understand how Cloud is being used across different industries. Being part of the engineering team in IBM Cloud, I get to see the architecture and the implementation of both Cloud Foundry as well as the IKS, the Container Services. And also, I'm fortunate to have a close association and part of the open community, like I'm the co-chair for Istio workgroup. And then I'm closely working with Cloud Foundry and Kubernetes. So I could get to see three different point of views when it comes to Cloud and Cloud Foundry, a customer perspective, an engineering perspective, and then we get to see what's happening in the open community. Good afternoon, everyone. My name is Surya Dugiralla. I am an STSM with Watson and Cloud Platform and Engineering Guild Leader in IBM Cloud. So today, we're going to talk about three different things. We're going to talk about how containers evolved and what are the current pain points that customers are seeing and what we are working on to alleviate those pain points. And also, we're going to talk about some futuristic stuff, how the architectures are changing, especially Cloud Foundry, and how these three major open cloud communities like the Kubernetes, Istio, and Cloud Foundry, which are going in parallel, how they're actually going to be merging and actually going to integrate in future. So we're going to talk about the current design, and next, we'll get into some futuristic stuff. There are many projects that I'll be talking about today. And in fact, there are many breakout sessions that will go more actually into those specific projects. So if you look at these three projects, the open cloud community ones, the Cloud Foundry, Kubernetes, and Istio. So you might have heard about these things time and time again. So we're going to talk about how these three, within the Cloud Foundry, they're going to work together. So before we get to that, I want to just go down the memory lane. When this whole container stuff started, because we always talk about containers. So when these containers, these are not new. If you look at that, it all actually started with the CH route in Unix. You can call that as the starting point for this whole container journey, because that's where you could get the resource isolation concept that was born. But officially, like you can see in 2008, you have those Linux containers. That's where we really talked about containers. And then if you look at Cloud Foundry, when we have announced this around 2011, the Warden containers that are part of the Cloud Foundry in 2011, then from that Warden container point of view, then we moved to support the garden and docker side. How we went to that? In 2013, docker containers were born. And then 2014, you have the garden Linux containers, because that's where we were actually going from DEAs to Diego in Cloud Foundry. And of course, 2015, that's when Kubernetes was announced. And 2016, you have, of course, again, 2015, you have the Open Container Initiative. And then RunSea started there. And then we started supporting that in 2016 with the garden RunSea. And then if you look at 2017, that's where IBM, Google, and Lyft announced the project Istio. And now in 2018, we are talking about how these three projects are going to work together. Of course, there are many, many engineering issues that all these three communities are working in parallel. When it comes to Cloud Foundry, of course, there are many customers, but we still are working to harden the platform based on the customer input, on the performance, scalability, stability, resiliency issues. And also, the multiple integration projects that are going on that's also happening in the Cloud Foundry world. When it comes to Istio, Istio being very young. It has just started last year. We have gotten very good momentum for a year old project. And you can clearly see we need to harden the mesh because the potential is really high. There are a lot of people in the community working on hardening the mesh, especially performance and scalability aspects. And then we have announced the minimal Istio. Like, let's say, if you don't want to use all the features of Istio, you can actually deploy different through helms, a minimalistic footprint of Istio. And Kubernetes, as you can see, in Kubernetes, we have, of course, it's a very nice orchestrator and scheduler platform. But we still have some issues, especially if you look at the scheduler. Some of you might have seen there needs to be some more intelligence put into the default scheduler because it cannot really identify an unstable cluster and correct it to become a stable cluster. So imbalances in the cluster and those things, the default scheduler is not able to adjust them. So there is a project under the scheduler's track in Kubernetes called the descheduler. So what we are working there is to see whether we can actually dynamically adjust and dynamically move some of the parts to those nodes where you have resources, whereas you are just bottlenecked on a specific node. Things like that, we are working on the descheduler side. And then, of course, the new things like the SNI, like the CSI, like cloud storage interface and stuff. So there are a lot of stuff in each of these three cloud communities. Still, they're working to make them even better. Now let's look at the Cloud Foundry for a moment. Cloud Foundry, even though it's being embraced and used in multiple production environments, in fact, I myself worked on the health care, banking, and some consumer electronics and different areas. But these are some of the things that really some of you might have seen. When it comes to routing, you may see long tail latencies if you're not using the go routers keep alive. And when it comes to networking, because you know in networking, if you have microservices, let's say you have two-tier or three-tier microservices, then you may experience significant latencies, increased latencies, if you are not using container to container. And then when it comes to build packs, of course, you might have seen when you do a CF push. You may see a sudden spike in CPU. And that's mainly because the way the current build pack mechanism, how the file system works. It's a flat file system. And then you also might have seen CPU sharing issues, like the algorithm, the default CPU algorithm. Sometimes if you have a contended environment, you may see some staging failures because you don't have enough resources. And then, of course, the garden doesn't have a concept of a pod so that you can have multiple containers in a pod like Kubernetes has. So you can inject a sidecar, which is essential for supporting Istio. So that's another drawback. And then you have now, as many of you might have seen, if you're using both Cloud Foundry and Kubernetes together, you will have multiple scheduler issues. And then you have the service mesh support. Of course, lots and lots of people when they move to the microservices. As a developer, I don't want to get into any of those traffic management, security management, certificate management, all those things. If somebody else can do that for me, then I can focus more of my energy on my industry-specific, domain-specific problem solving rather than handling these plumbing things. That's where the service mesh support is really important. So we are working, and I'm going to talk about what are the things that we are working here to resolve the current design pain points and how we're going to actually get to the next architecture to solve some of these other problems. Yeah, you can see this here. The long-tail latency, we have run some health care application. And then we have seen this. If you look at the long-tail latency, for some of you who may not know about that, long-tail latency is a, if you look at the gap between an average response time versus the 99th percentile, if that is significantly higher, as you can see on your left-hand side, the max latency and the 99th percentile is much, much higher than an average response time there. And that's mainly because of the go-rotors' inability to have the keep alive to the back end. So once you enable, because we have that feature now, which is not on by default, but if you enable that, then you can actually significantly reduce that long-tail latency. So this is one of the things from a routing site, which we have worked on. And then the second feature which we have is the container-to-container networking. So most of you are familiar, like if Service EA is calling Service B in a microservice application, then Service CS, that invocation, it has to go all the way out to the proxy and then gets into the go-rotor. And then the go-rotor will go to the service. It may be in the same Diego cell. But still, it can't talk to each other. But once you have the container-to-container networking enabled, you don't need to go all the way. And actually, you can reduce those hops. And that's where you will see significant improvements in the latency. Again, you can see some proof here. This is a pharmacy application from health care. You can see the default without container-to-container. And then you see, enabling the container-to-container, you see almost 2 and 1 half 2.5x reduction in latency. And you can see the same thing with online banking application too. Significantly, it's reducing from 329 milliseconds to 278. So these are some of the things that we have introduced and we have optimized these features. But these features are not there on by default. So if you are a cloud provider, you have to make those things available. The third one about the CF push. If you look at these, you can see the Java application, Node application, Ruby application, all of them, they manifest differently from a CPU spike how much it is. From a Java, normally, you see a much bigger spike because Java being a little bit heavier compared to Node and other programming models. The reason why you see this big of a spike is because your droplet size is much bigger. You have a flat file system. So you don't have a layered file system like Docker. So each time when you push an app and you have that Docker, you have the droplet size, you need to do that zip and unzip, all those things that which are highly CPU intensive operations, that will maybe four or five seconds. But you will be impacted with those things. How are we fixing that? You might have seen the, you know, Jules talked about the OCI build packs. The OCI layer is actually addressing that. Basically, these OCI build packs, what it does is it basically changes the file system from a flat file system to a layered file system like Docker. So as you can see in this, so you have a much smaller droplet. So you don't need to spend that much in compression and the CPU spikes will be significantly lower. So these are some of the existing pain points and with the current design and architecture. But now let's look at, as most of you have seen, now Cloud Foundry and Kubernetes, they're actually working together. There are multiple projects that are going on here. And you can see there are at least five of these projects, mainly led by different vendors here. The first one is the CFE or the Cloud Foundry Enterprise Environment that Tammy mentioned this morning. And then you have SAP's CF, Kubernetes Integration Scenarios. And then, of course, the Irene project. I will touch a little bit on that. So that's another thing that where you will try to replace the Diego scheduler at the application level, not at the container level, and then you just use Kube instead of Diego. And then, of course, you have other projects like Kube and these things. So what exactly is the CFE, the Cloud Foundry Enterprise Environment? So basically what we are doing is actually we are dividing this whole as isolated segments. What we are trying to do is we have a control plane and a data plane. Control plane has all the, it's running on a Kube cluster. It's having all the CF specific, like maybe Good Outer or the Cloud Controller and all these different CF specific, fabric specific things will be deployed on the control plane. And then your applications residing on the Diego cells that will be on the data plane. So you have a nice isolation there. And all of these things are actually running on a Kube cluster. And the beauty of this is you will be running on that. At the same time, you have access to all kinds of services that are available in the marketplace. It may be a blockchain or AI or IoT. So you have the nice orchestration layer that's handled by the Kube. But at the same time, you have integration to all kinds of services there. And you have the concept of you can use the Helm concept. So it's kind of a first step towards a nice integration between Cloud Foundry and Kubernetes. This is just a dashboard. You can see that the application level, like the container level, and also the pod level, resource usage, and all that stuff, you can actually see it from there. So now let's talk about what kind of problems from an engineering point of view you will see. Now you will get into nested container issues. Then you may see, OK, so now I have the garden containers within the Docker container. So how am I going to scale? Do I have any kind of issues here? So all those things you will get into with this architecture that we have here. Because now the way we are trying to do is we're going to limit one Diego cell per node. So it is actually basically a pod. So that has other parts like the monitoring, like Prometheus pod or Fluenthe pod. But within that Docker container or the Diego cell pod, you will have multiple, maybe up to 80, or based on how big your node is. You can go up to 80 or 100 garden containers. So when you have this kind of a nested, so do we have any performance issues or scalability issues? That's exactly the first thing that we looked at. So we have a direct comparison of the IKS. You're running the same application, a network-intensive application, on the Kubernetes platform in pods. And then you do the same thing on SIFI, like Cloud Foundry Enterprise Environment. Of course, now you're running those applications in garden containers in the Diego pod. So you can see the performance-wise. You don't see any extra tax, of course, a little bit. But you don't have that additional scalability issue or anything on the SIFI nested container architecture. And you can also see the scalability. You can see that both the Java application, as well as the node application, you can clearly see how elastic and how you can actually scale those applications, even with this nested container architecture. Now, SIFI gives you a Kubernetes integration at the lower level, right? Because you're building your Cloud Foundry on top of a Kube cluster. But at the application level, you still use Diego scheduler. So now you have two schedulers. You have, at the container level, one Kube scheduler. At the application level, you have the Diego scheduler. Well, you may see some problems later on. So the project called Irene is actually mainly working. We are working on that. And Simon is going to be actually talking about this later. So you can see the idea behind this Irene project is because SIFI is pretty good for dev experience. So we'd like to keep the best of CIF part. And then Kubernetes is a lot of community behind it. It's a nice scheduler. So let's keep Kubernetes for scheduling. And then keep the DevOps and developer experience with the Cloud Controller and CIF push and all that stuff with CIF. So if you combine these two things, that's where this Irene thing will come here. So how it looks like. If you look at this, on the left-hand side, you can clearly see that the Cloud Foundry as we talk about the CFE, like Cloud Foundry Enterprise Environment, where you have the IaaS, and then you have Kube cluster on top, and then you have the Cloud Foundry stack. If you have CIFI plus Irene, then what you're doing, those stars you can see where you're replacing the garden scheduler and the garden cells, you don't have that. Now you will actually, when you do a CIF push, now it will be pushed to a Kube scheduler. So you have a Kubernetes. And then instead of the Diego cells, you have this Irene. So this is the direction that, in future, we may see Cloud Foundry. So for more details, actually, there are some sessions. Today at 3.50, we have a panel discussion where Simon and the rest of the folks are going to actually talk in detail on this. And then tomorrow, we have two more sessions, of course, the CFE from Simon and Tammy, and then another thing tomorrow again. So now we talked about Kubernetes. We talked about integration of Kubernetes both at the container level as well as the application level. Now let's talk about Istio. As I mentioned, Istio is mainly the one that's actually getting traction because to put it bluntly, it will make me as a developer. I don't need to care anything except my application because everything else will be handled by Istio. So what exactly is Istio? So with Istio, you get all these different qualities of service with microservices. You will get intelligent routing and load balancing. You get the resiliency that you need for microservices. Then you can enforce the fleet-wide policy enforcement. You can get all kinds of telemetry and reporting you'll get. And then between service to service, authentication, security management because it has its own CA provider, you will get the certificates. And for an application as a developer, I don't need to worry about the rate limiting. I don't need to worry about connection timeouts and all that stuff. Everything will be given by the service mesh. That's exactly the reason why Istio is getting actually more and more popular because everything else taken care by that. So as a developer, I'll be just focusing on my domain-specific stuff. So again, Istio has two things. You have the control plane and the data plane. So control plane has the pilot mixer and the certificate management, Istio. And then the data plane has the intelligent proxies as sidecars to each of your services. And then your service doesn't know where the other service that it calls reside because the sidecar, the intelligent on-way proxy will handle all that thing for you. And then pilot will control the sidecar. So you can actually, through configuration, you can actually adjust how you would like to have the traffic management and everything, like canry testing, A-B testing, and all that stuff. So when it comes to, there are some work items. And people are working on how we can get Istio and Cloud Foundry work together. But the main thing is Cloud Foundry has the highly opinionated and simple way of handling things. That's the main positive point for Cloud Foundry. We don't want to lose that. And the Cloud Foundry, again, remains the optimized for developer velocity. And we want to keep all these major design points while we are trying to integrate these things. And again, complexity of maintaining because we don't want to lose all the control that we have for the operators. And we should have the ability to control the service mesh resources. All these things are the major design points that we're actually trying to keep in mind when we look at the integration of Istio with Cloud Foundry. So where exactly are we trying to integrate Cloud Foundry and Istio? There are four points. There is a north-south traffic and east-west traffic. So north-south is like when you go through the go-router. So there is a plan to even replace go-router with envoy, which is the ingress controller or that ingress gateway that comes with Istio. And then for east-west, you need to have that sidecar kind of a concept. But that's where app-to-app communication and all that stuff, the east-west traffic, we want to have an integration point there as well. And then when it comes to security, because Istio handles a lot of security, we need to integrate with UAE for the OAuth and OIDC. So these are the four touch points that we are trying to get this integration going. But again, because Cloud Foundry didn't have that concept of pod, so you might have heard from Dr. Zools about the peas, which are kind of a sidecar pattern for our garden containers now so that you can have the envoy intelligent proxies attached to the services. So this is the work that the containers tribe did recently to support this. So what are the risks of embracing Istio into Cloud Foundry? Like, no, because the first and foremost is the performance and scalability. Because we have hundreds if not thousands of routes, so we want to make sure that Istio's pilot can handle and scale as we integrate that. And then we have to balance the desire to do the enhancements, because now we are getting into a completely two different, because Istio itself is a very active dynamic open source community. So we want to make sure that we have minimal enhancements to the Cloud Foundry. And keep the currency is also going to be a challenge, because as I said, like a four touch points, so there are multiple teams within Cloud Foundry that they need to really keep the currency when we talk about Istio and Cloud Foundry together. Luckily, of course, I am, as I said, we have taken the performance and scalability things into consideration as I'm leading the jointly that work group in Istio. So we have a few issues already opened. We are working on pilot scalability issues, apart from the other 13 things that we are actually working right now. So Istio, as we speak, is getting optimized in multiple fronts, right? From telemetry to cash management, buffer management, pilot, ingress gateway, everything is being worked as we speak. There is a SWOT team that I'm leading. We have a work item that's going on. Actually, you can see all the stuff that's going on here in those links. And also to make it easy for Istio performance, we are integrating multiple dashboards that will make it easy for anybody using Istio to understand the resource requirements. As you can see here, recently we have integrated this. How many VCPUs you need for 1,000 transactions per second for a specific Istio component? In this case, you can see Istio proxy, Istio telemetry, and the policies, everything, right? So we are making it easy. As I said, Istio is a very dynamic community. It's getting developed and deployed and optimized as we speak. For more details, I think we have some sessions. Shannon and Aaron are going to be talking about 2.30 today. And we have office servers and also Istio birds of feather sessions you'll get there. Again, if you want to put all of these together, like Watson, blockchain, Kubernetes, serverless, CloudForm, everything together, there is an app. You can actually see the CloudCoins. You can go and download it. And that will give you a perspective of how all of them working together and giving you an excellent user experience. So with that, I will complete this session. Any questions? Thank you.


Ukraine prepares a surprise for the Russians in Bakhmut. No one is withdrawing Ukrainian troops from Bakhmut yet. Said Nikita Shandiba, head of the press service of the 10th Adelweiss Mountain Assault Brigade, OK Ukraine. Thus Shandiba commented on the information of a number of observers and the media about the alleged tactical withdrawal of the armed forces of Ukraine in Bakhmut. The situation in Bakhmut is difficult. The Russian invaders are constantly trying to break through the defence of the armed forces of Ukraine with meat assaults. The road of life of the armed forces of Ukraine is being held. Active battles are going on for it. The Russians are trying to cut off our logistics, but the defence forces are holding it. On account of the withdrawal of troops from Bakhmut, 100% no. The soldier said he noted that the Ukrainian army is actively defending itself and is preparing a small surprise for the enemy. Meanwhile, Russia is focusing its forces on its assault of the eastern city of Bakhmut. General staff of the armed forces of Ukraine said that Russia is focusing its efforts on conducting offensive operations on the Bakhmut Avdivka and Marinka fronts. On the Bakhmut front, Russia continues to conduct offensive operations. Ukrainian troops hold up in a network of dimly lit and cramped basements in the city's western districts have been making a determined last stand against Russia in the longest and bloodiest battle of the war. Ukraine is defending street by street at a significant cost.


Hi and welcome to the session. Let us discuss the following question. Question says, construct the following quadrilateral. You are required to construct rhombus BESD in which B is equal to 4.5 cm and Et is equal to 6 cm. Let us now start with the solution. Now first of all, we will draw a rough sketch of rhombus BESD. Now clearly you can see this is a rough sketch of rhombus BESD and we are given that Be is equal to 4.5 cm, Et is equal to 6 cm. Now recall that rhombus is a quadrilateral with sides of equal length so each side of rhombus BESD measures 4.5 cm as each of its sides is equal to Be which is further equal to 4.5 cm. Let us now start with the construction. Now first step of construction is draw Et equal to 6 cm. Now clearly you can see here we have drawn Et equal to 6 cm. Now to construct rhombus BESD we are required to construct two triangles, triangle Est and triangle Et. And note that both the triangles triangle Est and triangle Et have the same base Et and both of them lie on opposite sides of base Et. Now second step of construction is with ER centre draw two arcs of radius 4.5 cm on opposite sides of Et. Note that Est and Eb both are equal to 4.5 cm so we will mark two arcs of radius 4.5 cm with ER centre to locate point S and point B. Clearly you can see we have drawn these two arcs of radius 4.5 cm with ER centre. Now next step of construction is with ER centre draw two arcs of radius 4.5 cm each to intersect the previous arcs at points S and B. Clearly you can see TS and TB both are equal to 4.5 cm so we will draw two arcs of 4.5 cm to intersect the previous arcs at points S and B. Clearly you can see we have drawn two arcs of radius 4.5 cm each from centre T. Now this point is point S and this point is point B. Now to obtain rhombus BEST we need to join BE, ES, ST and TB. So our last step of construction is join BE, ES, ST and TB. Now clearly you can see we have joined BE, ES, ST and TB. So BE, ST is the required rhombus where ET is equal to 6 cm, BE is equal to 4.5 cm, ES is equal to 4.5 cm, TS is equal to 4.5 cm and BT is equal to 4.5 cm. So this is our required construction. This completes the session. Hope you understood the solution. Take care and have a nice day.


Hello friends welcome to the session I am Malka, let us discuss the question that is differentiated with respect to x, the function in exercise is 1 to 11, our given function is sin x minus cos x to the power sin x minus cos x, where y by 4 is less than x is less than 3 pi by 4. Now let us start with the solution, let y equal to sin x minus cos x to the power sin x minus cos x. Now taking log of both the sides we get log y equal to sin x minus cos x log of sin x minus cos x. Now we differentiate both sides with respect to x, differentiate both sides respect to x we get 1 upon y into dy by dx equal to sin x minus cos x into 1 upon sin x minus cos x into dy by dx of sin x minus cos x plus log of sin x minus cos x into dy dx of sin x minus cos x, this implies 1 upon y dy by dx equal to sin x minus cos x upon sin x minus cos x into cos x plus sin x plus log sin x minus cos x into cos x plus sin x, here we see that sin x minus cos x will cancel out with sin x minus cos x and this implies 1 upon y dy by dx equal to, now we will take sin x plus cos x common, this will give us 1 plus log sin x minus cos x, this implies dy by dx equal to y into sin x plus cos x into 1 plus log of sin x minus cos x, this implies dy by dx equal to, now we will substitute the value of y which is sin x minus cos x to the power sin x minus cos x into sin x plus cos x into log of sin x minus cos x plus 1, now this implies that dy by dx equal to sin x minus cos x to the power sin x minus cos x into sin x plus cos x into log of sin x minus cos x plus 1, where sin x is greater than cos x, so this is the required solution, hope you understood it and enjoyed the session, goodbye and take care.


I need to find a place for you during this series. You're just you're kind of in the way. Is this Does this work? I know there's gonna be a couple comments like that's like Jack. Yeah. Yeah, leave it like that It's not doable, buddy. Ladies and gentlemen, welcome back to chainsaw man episode 2. What's the episode called? We have a rival in Tokyo today now the first one setting up the series quite Beautifully we met dingy the main character I'm assuming and found out how he exactly becomes the chainsaw man kind of using his body with pochita This this little chainsaw dog. Hopefully it's not the last we see of him at the very end He was recruited to become a actual professional devil hunter if you miss the first episode I go watch there's a lot We're gonna hop into this one if you need a channel drop us up and let's get started God dang them pupils His little blotch that was cute Thank you Bro, he's already been called a dog by the other dude who's seen as a just a hound Damn bro, then you just goes from dog to dog Hey, what did I say scary more like I mean did you a listen I think this is a good middle ground He's actually dead dead that's so sad Thank you There it can speak you as Bro he We already know that's like what he wants is a girlfriend like that, but he's like She's actually like being nice. Yeah Dude, there's like spirals in her eyes, it's a little creepy. I can't tell I feel about it Oh, let's go free meal Like how you asked if it's okay He's tired Bro Yeah, dude is so kind of inter technically It's a long story Maybe not that long You already Like how he's like that. Oh, he's kind of like a devil human sort of It's a shoes you'll tell he wasn't You know He's literally inside of him Like that's kind of reassuring to him to that there's a part of but she literally in him Well, it's cool He's like asking permission Everything Is it cuz he's been like so poor is he's just finding an excuse to get her to feed him boy is down tremendous Oh my gosh Describe me Let's go Oh, dude, that's me. This is so adorable He's just had a loss We figured out who he was in the first episode what he wants He's he's my man's head over heels Headquarters regularly looking building You Was like actual government double hunters. It's not like he's been a double hunter. He's becoming like more official Fingers crossed for you, bro I like how straightforward he is It's like the same thing she's wearing like the tie and the dress shirt this is dress pants Yo, isn't this guy in the intro? Aki looks very Keeping him on a hook hard make sure you tie your tie young man Also, I was told that dingy. This is like his like third voice acting job like he's very new So I guess I recognize his voice or nothing Now he's gonna do the best possible job that he Come on a key spilled the way Aki doesn't even spill the beans. It seems nice. Oh What was it cuz he asked that?   I'm rooting for you. You're the emcee.  Oh, that's down, right? I'll try to remember as high Cow up Makima What's the usual This is a random, but he reminds me of fry from Futurama, and I have no idea why I'm trying to figure it out So the fact that he's double and human is really really really rare Dude, so he's basically stuck either like whether he likes it or not be killed He's basically technically a devil and that's their jobs to get rid of them I feel like you would you would take that opportunity if you got it What Little backstory. Ah, there's the flashback. Oh, maybe not. What are we? He's asking if she's a good person Maybe he just wants like like affirmation Did he say that because like again like he's never hugged her Oh my god, he's making a mess You can tell he's never like He's a dog, bro Wow, wow, what did he create in the bathroom? I a cow. Okay. I need to keep her. Hi cow. Hi cow. Hi cow. I'm Makima. Does he have an axe?  Oh my god.  He has like pincers that's so gross Oh, that was easy. He didn't use his power. Okay I think he was fine with that. He just wanted to see what you could do No wonder he's a double hunter. Oh my god Oh He's new I mean even if they they're fiends somewhere in between He's realizing dingy isn't like trying to be annoying to him. I think their personality is just class I I'm serious about this Well cheetah watching from inside him like this dude He is living the dream. Yeah, he's living the dream It's almost like like he said like as much cheetah was Dying What was that the close-up? Oh my god This is his dream This is his dream Is he trying to imagine what it's like the right plan, what do you mean plan brother? He needed something like this He's got the right mindset. He's just dumb, bro. Oh Not him buddy But Oh another girl Double the odds dingy.  They're both a little goofy She's gonna push them all away He decided I don't think he's manipulative like that.  I'm so sad when the episode ends I'm like learning more and more about this world and like getting more and more into it It's just like I gotta wait another week I mean the first one was a lot longer because I had to kind of like I said set up the world But now we're meeting some devil hunters. I'm guessing who we're going to be sort of the main ensemble Makama drawing a lot of mystery and how he asked if she was a good person and we we don't really know a lot about her She is odd very very odd Hayakawa kind of being the more more the rock type like very just straightforward No nonsense. He's got a goal in mind He's got a mission in mind And of course learning more and more about denji this episode I mean, we pretty much know who he is at this point though So we can start to see some character development since we know who he is What his goal is and how goofy sort of is and the addition of power who just made a hammer out of blood That was a sick animation though. I mean, I gotta be honest The guys that has been here for episode two of our chainsaw man watch you Luminum we thought episode two down in the comments below was this week's episode did it did it deliver And as always I'll catch you guys in the next one Peace peace


I'm gonna start. I wasn't gonna do this because it seems kind of self-indulgent, but it's gonna be fun I'm just gonna start off by giving you my own very convoluted Religious background which sort of explains like why I decided to ever put on a conference like this So I was raised I was raised Catholic and I was a I was very I was very good little Catholic boy There's a lot of pictures of me actually with my with my hands like this kind of looking up In the sky and I was actually the best little Catholic boy in my class I was the Catholic boy who got to carry like the cushion that the crown of roses for Mother for Mary's day was on and I got like A's and religion.  Anyway, I was I was gone from Catholicism at that time I left Catholicism at the age of 18 and And then I guess I would describe my years for the next 20 years as sort of a Kind of a hippie Taoist Zen Buddhist. I was that's how I define myself to other people You know, I had long hair and I read the Tao Te Ching and every translation I could find and I took like You know Psychic reading classes and things like that I Went through it kind of an interesting phase from about the age of 28 to 38 where I actually I heard voices I heard voices maybe once a year and these voices would say Kind of interesting things to me This was I was reading the Seth books the Seth speaks books anybody ever read those and what? Sure, of course you read that I read those and and sure enough I started, you know, semi-channeling, but I was a very resistant You know, I never actually did very much of what the channeler told me to do but I did do a couple things that the Channeling voice told me to do it told me that I should become a minister and it told me that I should study religion So I was always looking for the inexpensive way out. So I became a universal universal life minister, which is only $40 It's from the Church in Modesto. So I actually became a minister and I married about eight couples of of whom about half are divorced and the other half are still together and and I also I went back to school and I got a master's degree in religious studies and I wrote my My thesis my master's thesis on Jodo Shinshu Buddhism in the insect haiku of Kobayashi Issa who is a poet I very much like so after that that kind of that kind of That was that summed up about that was like that takes me up to about age 40 something like that a little bit later, I you can say that was kind of like my religious space until about Until really about six years ago about six years ago. I got interested in Quaker ism. I started attending a Quaker church in San Francisco and I dragged my whole family down to Costa Rica where there's actually a Quaker colony Monteverde Costa Rica and we live with the Quakers for a year and And I almost I became an attender, but I never actually joined because then I got I got waylaid by atheism I got I got suddenly very angry at at Pope Benedict I was I got simultaneously angry at Pope Benedict and did Islam I was angry at the Pope Benedict because he that was when he said that condoms in Africa were a bad idea because they were actually promoting AIDS by promoting sexuality and my My angry Islam was from reading Ayon Hirsti Ali's book called infidel so I suddenly became a militant atheist and I plunged right in and I actually Put on you know, I left the Quakers and I put on it was actually at the time It was the world's first atheist film festival. I put on this atheist film festival in San Francisco Which is now in its fifth year, but I only did the first year but I put that on I was a militant atheist and I actually put put out a Atheist calendar 2010 I think it was but I actually became disillusioned with the atheists in about three or four months I went to an atheist party. I thought it was really boring They ate really bad food and the big event was the Bible throwing contest to see who could throw the Bible the farthest and I actually You know, I kind of think the Bible has a lot of great literature in it So I didn't my actually my daughter won the contest. She's very good at throwing the Bible And they were pleased with her But I was not very interested in the militant atheist scene most of because I thought it was really negative It just had to do it seemed to me it was all about bashing people that believed in religion So I very quickly became a transhumanist after that which was wonderful because transhumanism is It has all this optimism in it like like just like a religion like you're gonna live forever Perhaps, you know pretty great.  Well, there could be you could be trapped in a bad Stimulation or something but anyway, so I became a transhumanist and I was very thrilled about that and I kind of retained some of my Militant atheism as I was a transhumanist because in transhumanism I ended up doing a survey of transhumanist and I and I found out that 90% of transhumanists are actually Atheists and rather militant atheists and I was running. I was managing director of a think tank website at the time called IET Institute for Ethics and Emerging Technology where I met many of of you a few of you and Actually, I remember I got launched though, you know the website into a few debates about atheism and transhumanism And I was I think I wrote a few essays of just basically saying that religion was really stupid and that why are there religious? transhumanist that's really stupid and So I was like the militant atheist transhumanist then and then a couple of things happened one was One of the religious transhumanists wrote me a really interesting email Where he basically pointed out that one of the highest values in transhumanism is to live a long time and That a lot of studies show that people who are religious live longer and how was I going to reconcile that? Why was I going to ask people to abandon religion and die younger and that didn't make any sense? And I thought that was actually interesting and at the same time I decided that I was going to throw a transhumanist party at my Vacation home on the Russian River, which I've since gotten rid of because it's a money pit So anyway, so I threw a transhumanist party at my vacation home And I invited all transhumanists as it turned out Instead of all the militant atheist transhumanist showing up Lincoln's laughing sure enough only five people showed up and four of them were Mormons So there I am and I'm with you know religious transhumanist and other religious transhumanist like Julia Prisco or emailing and saying Which I could go and all of the militant atheists who? militant atheist transhumanist who I thought Would be happy to go They didn't show up and which reminded me of the other email I got from the religious transhumanist which basically said religious people live longer and one of the reasons is they actually have Better community it may be that they have they believe in more positive things that help them or it could be that They have a better community. So then I was I thought about that one thing about myself as a young Catholic boy was If you to ask me as a Catholic boy, I would have what I wanted to be when I grew up I would have said missionary and I was one of those kids They always did these collections for the pagan babies and I was one of that I was the kid who was always giving a lot of money for the pagan babies and I named a lot of them Henry, which is you know my name. I was very into the idea of being a missionary and Like I said I left Catholicism, but there was something that I believed in Catholicism That I want to talk about briefly. It's actually Corinthians Chapter 13. Does anybody know that right off the top of their head Corinthians chapter 13? I'm gonna read you just a I'm just gonna read you parts of it. It goes Though I speak with the tongues of men and angels and though I have the gift of prophecy and understand all mysteries and all Knowledge and though I have all faith so that I could remove mountains and have not charity. I am nothing Charity suffereth long and is kind then it goes on and on about charity and it concludes with Faith hope charity these three, but the greatest of these is charity. So that is something that I retained Even though I left Catholicism I believe that charity was the was the best of all virtues and it was it was what was It was the it was the goodness. It was what made somebody religious in my opinion It was the only thing that I actually retained out of that So and then I had I've had a couple of experiences in the last two years that involved Charity and perhaps transhumanism the first was when I was working for Institute for Ethics and emerging technology They asked me to run a Africa futures project and to launch a cell phone drive. I Was very excited about this. It was a combination of being charitable and being transhumanist at the same time And I was convinced I told my boss James Hughes that I will I will collect a thousand cell phones Transhumanists will be really into this transhumanists have old cell phones They will mail them to me and we will send these cell phones to Africa and the and this will benefit the Africans enormously they all need cell phones and And so I worked extremely hard at this cell phone drive and the conclusion was that I did not gather a hundred Thousand cell phones I gathered a hundred cell phones only a hundred I got 30 of them from my mom who is a Catholic and works for a thrift store on occasion She's a volunteer. I got 30 30 of them from my brother who was not a transhumanist, but he runs a Silicon Valley corporation He just told all of his employees to bring in their cell phones and they did that I got 30 of them from a Mormon named Roger Hanson Who is a very nice and philanthropic guy and he collected them from everywhere and he gave me 30 and I got the last 10 from various friends of mine Who are just not transhumanist but just friends and happen to have them all around So the conclusion of all that was I got absolutely zero from Atheist transhumanists I got zero and this was more than a little bit discouraging because like I said my primary Value and virtue that I believed in was charity and that the transhumanist had absolutely failed in charity and this sort of confirmed which had been sort of a suspicion of mine and I think some of the public that that perhaps the transhumanists are not Essentially philanthropic and perhaps they care a lot about living a long time And they don't actually care what happens to poor people in Africa And they don't really happen care what happens to people who are lower on the economic rung and this is actually was actually a very kind of depressing because I was very fond of transhumanism as you know as the next of my Six or eight, you know belief systems So I was it was very disappointing and it's and I had it's kind of a deal-breaker with me that I would like transhumanism to improve in its charitable giving Because I I don't actually want transhumanism to be a little generous because Charity is actually my primary virtue.  It would be this kind of confluence this kind of merger of two values, which would be charity and and and a Non-scientific hope for immortality now the next thing I wanted to mention is that I I'm involved in it I was in I am presently involved in another charity Project, which is ten years ago. I was running a preschool As it happened I have two kids who were preschool age and I had a basement and so I started a preschool and and I decided that I needed a sister school and so I looked around for a Affordable sister school meaning a really impoverished school somewhere and I found one in the Philippines with this indigenous tribe called the man Yang's Where the average man Yang makes? $30 a month and it's just this indigenous tribe That is you know among the poorest of the poor So I started a sister school program there And I actually largely funded it all by myself. I've been doing this for about ten years funding this indigenous tribe I I bought them some land because they needed some land And I thought well this you know I don't know if any of you have gotten involved in helping people But it's you always think it's gonna end and they're gonna be self-subsidized Anyway, I thought I'd get them some land and they could grow bell peppers and they would never need me again but it actually doesn't work that way there's a constant flood of letters and So that went on that's been going on for ten years and I had a fight with him about five years ago Because she said you know, there were about 60 of us that moved on to your land and now there's 300 We have so many babies and I said well, why don't I just buy you condoms next time and you can stop it having You know, I can't afford taking care of 300 people and they said we're Catholic We don't use birth control and I was so mad. I just didn't give him any money Or even even reply to their desperate emails for about a year and a half But I since crawled back into helping them. I decided well There's still people even though they're Catholic and and I this is my this is what I have to do But I'm quite annoyed about that and I'm gonna get back to that in a second So most recently I got another email and she said, you know, we're still here and we need about four thousand dollars and There's still a lot of us and we all have tuberculosis and we all have these parasitic worms Which I always think is like the worst Yeah, I don't know if you ever saw that movie the fly where she's giving birth to like a larvae and yeah These parasitic worms so they're always crawling on it. Anyway, it's just a horror story and they have they have diarrhea and they have just everything horrible and So this time I thought well, I'm sick. I can't afford to keep giving him my money So I'm gonna send out a petition, you know, to everybody I know and see who I can raise money from and I didn't even try to get any money from transhumanists. You're all transhumanist I didn't spam you for money on this because the transhumanist failed me so miserably last time that I just figure I can't get any money out of them So although I did contact Roger Hansen again because he was philanthropic and he might help clean up their water supply I did contact my family again and my family failed again My family my family was great last time or this time they failed They were good at handing over cell phones use cell phones, but handing over cash. They're not so good I got $2,000 from a Filipino a rich Filipino friend of mine who'd have thought of it a rich Filipino friend She gave me $2,000. She's basically gonna sponsor all the kids. So How does this tie in? It ties in I did I what I did do is I sent About 40 emails to every Catholic church every Catholic school Every Catholic college in the Bay Area and I asked them for money and I basically Blamed them eyes and I said and I actually wrote an open letter to the Pope I said if you're gonna be anti-birth control You need to take care of the extra kids that you bring into the world because I personally can't take care of them Because these people still have Seven and nine children each and I actually think I could take care of them if they only had two But I can't they have seven and nine because they're Catholic and they won't use condoms So I even wrote a letter an email to the Catholic Church and school I used to go to when I was a little kid and I said My grandfather bought you your altar Can you give me some money for these people and I haven't yet heard from them? so the conclusion of this is That I also mentioned earlier that I was thinking of joining a synagogue But I probably won't because it's looking like The limited amount of money and time that I have is going to be devoted to Taking care of these people so basically I think my religion has become charity I don't have any extra time or any extra money to give to a congregation and I personally don't even believe in a congregation that Doesn't devote a lot of you know money to charity I my understanding about a lot of churches is sure they collect money for charity, but like 90% goes to administration So I would probably join a church at this point if they said you join and will give you a lot of money for your Filipinos, I would probably join that church. I would be that would be great and I would take care of this so that is my Conclusion on that I would love to see there has been I would it would It would it's amazing to me that after this conference probably the person that I resonated most with was Amin the Muslim I would have Shocked me before this started, but he talked a lot about equity I think that transhumanism needs to address economic equity in the world and It needs to Not present this idea that there that the rich people are going to live forever and the poor people are going to stay poor And I think that transhumanists should Be philanthropic for people who are less fortunate and should be more tolerant to people who disagree with them if they're religious and should Healthy unfortunate


Good morning everyone and thank you for joining me. So early bright and early in Helsinki Just start off. I'm Alice Pentink. Thank you to the hosts for a very kind introduction But I would love to know who you are.  Okay, good excellent shout out to the founders hands up if you're an investor Okay, a couple of investors you can always spot the investors. I was at Heathrow Airport yesterday and it was very clear In security who the investors were and hands up if you're thinking about being a founder one day Okay, these are my people these are my people and this talk is specifically designed for you So as I was saying I found a co-entrepreneur first and also me and my co-founder last year wrote a book called how to be a Founder and in this we talk a lot about ideation and where ideas come from. I Think the word idea is actually pretty unhelpful because Google is an idea stripers an idea But also you probably had an idea in the shower yesterday These are all ideas, but they are obviously at totally different ends of the spectrum So even talking about ideas. I think sometimes can be unhelpful What we're going to go through today is how do you develop a unique idea? How do you validate a problem that is different differentiated to everything else that's out there? I I've been investor for a long time a founder and investor for a long time and I've worked across Seven different geographies across three different continents I'm always amazed at when I do investment committee and I might do one in Bangalore Followed by one in Paris followed by one in New York. You hear the same ideas again and again So when you're a founder one of the things you've got to assume is that whatever you're building somebody else is trying to build it, too So what we're going to go through today is how can you give yourself some green space? How can you find an idea? How can you develop an idea that no one else is working on? So just a little bit of context on entrepreneur first. So I founded entrepreneur first now ten years ago It's pretty much what I've dedicated my career and life to for the last ten years and we are a talent investor We invest in the very very earlier stage We invest in individuals before they have a company often before they have a team and often before they have an idea When we get people to apply to EF we don't ask them for an idea What we found is that when we ask people for an idea You can have incredible people who are super smart very talented wonderfully skilled But their ideas suck and we found we were making a bunch of really bad selection decisions because we were saying this person seems great But have you seen their idea? This is crazy and not good crazy So we're very very curious in that we believe in talent We believe in founders, but we also believe ideation is a process It's something that you can learn it's something that you can get better at We're lucky to be backed by some of the world's best founders and investors And I believe I've got the best job in the world because I spend a huge amount of my time with people before they've been Started a company and get spent a huge amount of my time with some of the best founders and investors in the world And my job is to work out how this group can become more like this group So what is an idea? What are the the kind of key concepts that we're going to talk about today is secrets? And how can you as a founder find a secret now? This is a Concept that comes from Peter teal. What valuable company is nobody building every correct answer is necessarily a secret So why does he say this? He says this because he doesn't believe in competition He's pushing founders to find spaces that aren't crowded and this is the problem with problem-based ideation I'm sure many people when you say where do I find an idea? How do I find an idea? People say think about a problem you've experienced The challenge is that problem is typically a problem that many other people have experienced think about food delivery and ride hailing holidays Dating man, I've had so many dating ideas in my time It's very very hard to have a truly differentiated idea and what that means is you're going to have a huge amount of competition from day one So what we encourage our founders to do is to find a secret as of today We're going to be talking about how to find that secret So what counts as a secret? Many of the world's best ideas are founded on secrets that are non-obvious They are Controversial and they're often laughable If you think about something like Airbnb the idea that you could get Strangers to stay in another stranger's house and pay them for it willingly Seem totally crazy at the time Reed Hoffman is on our board and one of our early investors and he was one of the first investors in Airbnb and his partners told him He was crazy to make that investment because nobody would be so crazy as to do that If I think about one of the companies in our portfolio with a company called tractable Which is one of the largest computer vision companies in the world now. They start attractable in 2013 the secret that tractable was founded on was that Humans was that computers would become as good as humans in visual classification Now now that seems totally obvious ten years later, but at the time it was a real secret and again, they were ridiculed Seen as a bit naive and they struggled to raise their first round so When I speak to founders about early ideation Instead of thinking about it as the moment where you have the idea We think about it instead as a process of finding the idea and this is one of my favorite quotes about ideation Even though it has absolutely nothing to do with startups This is a quote from Michelangelo one of the world's greatest artists and he says, you know Every block of stone has a statue inside it and your job as the artist is to chip away chip away chip away at the layers To find that the angel David whatever it may be inside and as a founder, that's what you have to do as well The other way I think about it is as an onion layers of an onion that need to be unpeeled so that you can get to the secret in the middle typically the layers for that onion is Stuff known by people and outside the founders face and this is often where I find lots of founders stop weirdly We get founders that come to to us at EF and and they begin pitching ideas where it's like There is a massive problem in healthcare People are dying because of X That's not a secret everyone knows that The next level in in your onion is telling me things that If I was in the space, I would probably know so sometimes as an outsider you can be like wow Yeah, that sounds really cool, but the minute that you talk to somebody in the space. I like yeah known problem The next level in is knowing stuff that other founders in the space know That's still not sufficient because then you're just competing So you have to go one stage further and really get to the core of what your secret is which is something that no one else knows So let me take you through an example. Let me see if I can get the clicker to behave. There we go Think back seven years ago seven years ago had two amazing founders Jacob and Lawrence join EF they didn't know each other they started working together and Jacob was passionate about antimicrobial resistance the World Health Organization had said that Over-prescription of antibiotics was causing this massive and challenge within health and how do we stop it? This is the first layer They spent three years trying to solve this problem and as they dug into this problem more They realized that actually there are a bunch of multifaceted reasons why doctors couldn't stop prescribing antibiotics It only started working when they began to spend more and more time observing doctors and actually Understanding the challenges that doctors were experiencing day-in day-out They then realized that it was a communication problem It wasn't about antimicrobial resistance the thing that was holding back health outcomes was that doctors and patients couldn't effectively communicate But a bunch of other founders knew that in the space It wasn't until they realized that it was as simple as doctors couldn't send SMS text messages to their patients to remind them to take their pills to help them book an appointment to tell them come in for a repeat prescription whatever it may be Accurates went from three years of sort of you know in the wilderness as founders often find themselves to being in every single Primary care practice in the UK within 18 months One of the fastest growing health tech companies So they accurate Scott there through three things they use that edge They relentlessly spoke to customers and they created a behavior explosion So we're gonna go through each of those three things so you can understand how to get as quickly to the core of the onion You're gonna think I'm obsessed by by onions by the end of this So use your edge. This is a key EF concept and it's something that we talk about a lot in how to be a founder Your edge is your personal competitive advantage in solving a problem Compared to other founders and it comes back to this idea of whatever you're building whatever the idea you have Someone else probably has it too. So how can you make sure you have an advantage? Your edge is important as well because it's a constraint if you look at any of the research on creativity and Idea generation constraints actually increase both for quantity and quality of ideas that are produced Sometimes when you're a new stage founder You know you could work on anything if you take the problem-based approach You have millions of problems every day that could be could be solved So how are you meant to know which one to solve by using your edge? It gives you a starting point and it gives you a starting point that you already know something about This is Barney Barney joined entrepreneur first after having worked at Wonga for a year Wonga was a big FinTech startup in London in the 2010s When he was at Wonga, he realized that The the world of FinTech was very much set up to serve an older demographic and not Millennials and Gen Z He used his edge which was sufficient experience in FinTech. He only had a year. This is not about deep experience He used his sufficient experience as a starting point for his idea, which was Clio Clio is now the fastest growing FinTech app that Europe has ever seen and is making making 80 million dollars a year Some of the best secrets from the most unusual secrets come from combining two people's edges Entrepreneurs first were massive believers in co-founders. I've had an amazing co-founder for the last decade or so And people come to EF to find a carefully screened carefully selected co-founder That could help turbo charge their business One of the things that people often underrate about a co-founder is that your co-founder will help dictate the quality of the idea that you produce So they're not just about increased productivity They're not just about having you know an emotional support system So you get a beer at the end of the day. It's about generating a better idea and it often comes When two edges combine that's where you get the magic This is James and Sasha they've built an amazing company called Unitary James had a background in computer science. He had a PhD in machine learning and then had worked at Metta he'd been a content moderator for a long time and That was his edge, you know, he'd seen how difficult content moderation and keeping harmful content out of social media platforms was Sasha did her PhD with Steve Hawking on black hole theory They were really interesting combination because they were able to come up with technology that no one else was able to do by Combining their edges and generating a secret that was based on technology They were able to beat off some of the much more developed and experienced content moderation software to win major contracts with big social media firms that I can't name that you would know or An alternative example here. You've got Xena and John Xena and John created synantic Synantic creates the world's most emotionally realistic voices Some of you may have seen them in the press recently because they helped Val Kilmer get his voice back for the top-ground film Again, this is a really interesting combination of backgrounds where you've got John who had a PhD in Machine learning and then you have Xena who'd been working with autistic children for the last decade All throughout being a teenager. She'd been working with autistic children And she was able to use her knowledge about voices Expression and combine that with John's PhD Synantic was bought by Spotify for a very large sum of money about a year ago So if that's your edge and using your edge as the starting point, what next? Relentlessly speak to customers and if there's something that founders always Undervalue and always don't do enough of it's this bit because it's hard and sometimes it's pretty frustrating To be honest the pushback. I always hear oh And this is how you get into the into the heart of the onion the pushback. I always hear is Well, Henry Ford says that if he'd gone to his customers and asked do you want a car? They would have said no I want a faster horse Henry Ford. You're doing your customer development wrong You are not asking the customer for the solution you are trying to find out the secret that the customer holds You can't crowdsource an idea you can't crowdsource a product from a group of people what you need to do instead is Build intuition about what the answer should be what the product should be One of my least favorite things is when a founder says to me in my survey 70% of people say this is a massive problem and 90% of people say that they would pay $15 to solve it bullshit If it's in a survey, it doesn't count If you've done a survey, you've missed the point of customer development This is not about building an argument about why you're right customer development is about truly understanding how somebody thinks Feels relates to a particular problem. So the very best people do customer development through speaking There's an amazing book on this. It is definitely the kind of best-in-class book called the mum test Has anyone read the mum test? Excellent got some mum test fans And what I love that Rob Fitzpatrick says about this is that instead of thinking about customer development as a You know a business moment where you're you know, you're writing things down and ticking boxes Customer development should be like when a friend comes to you and says I've just broken up with my partner I'm gutted and you go wow that sucks. Tell me everything. How does it feel? What do you think what are going to be the next steps? What could you do instead? This is how you do customer development well by really understanding how somebody experiences a problem and then Beginning to get ideas about how you might be able to fix it. This is Rafi and Nittish Rafi and Nittish were on entrepreneur first many years ago and and they are building something called genie AI. I bumped into Rafi recently at a dinner and Asked him how things were going. He was super excited. He said we've reached product market fit and we're beginning to see and a massive inflection in adoption that we can barely keep up with Product market fit is always one of those things that and people say How do I know if I've got product market fit and the answer which is one of those unhelpful answers is you know When you've got it if you think you might have product fit product market fit, you don't have it You know you've got product market fit because the product is flying off the metaphorical shelves way Faster than you can you can cope with I said Rafi. How did you get there? What did you do was there like an aha moment where it all came together and he said no It was tiny incremental nudges to improve the product every week every month for the last five years One of the things he did think is super impressive and the very best founders do is that every Friday He had spent five hours doing customer development every Friday He would have meetings with different customers to hear how they were using the product Meetings with prospective customers to understand how they might use the product And this is how he built up that intuition. It's not about building a data set It's about you as a founder building up that intuition and this is why you can't outsource customer development It has to be something that the founder does themselves that the founder owns If you think back to that example about accurate Accuracy as well Really really understood their customer because they worked alongside them in the doctor surgeries every day for about a year Then when they got their own offices, they actually built in their office a doctor's workstation with a sort of you know national health service 1990s style computer to really understand what it would be like for their customer to use their software When we talk to founders about Customers One of the pieces of advice we often give is that you need to love your customer and founders always say yeah Yeah, no, we love our customer. We love our customer sometimes I think what founders mean is I think this customer could make me lots of money. So I love them Being a founder is a resilience game Being a founder takes a long long time to succeed I've been doing this for 10 years and I feel so lucky because I adore our customer I want to spend time with our customer My job is going out and meeting incredibly bright ambitious young people And talking to them about what they want to do with their lives I could do that for the rest of my life very happily The best founders want to spend time with their customer So think carefully about who you choose to be your customer because you're going to be spending a lot of time with them One of our internal mantras at EF is strong beliefs weekly held It's really hard to get to the core of the onion. It's really hard to get to a secret and often what we see people do is They sort of have many things that they believe And particularly if you've got an a co-founding team you can see people having slightly different beliefs What we see the best founders do and what we encourage our founders to do Is to commit to a strong belief that is weekly held. What does that mean? It means putting a line in the sand today about what you think your secret might be What you think the problem might be and what you think the solution might be And understanding that there's probably all wrong and it probably is Unfortunately all wrong, but that's because ideas don't come out fully formed They are a process that you go through of getting better developing and iterating The weekly held bit is about getting that input from your customers No one has the answer. No one has the right answer The only way to understand what is the right answer is to get whatever you're doing out there speak to people and get that feedback Often in the early days of founding a company I'll be doing an advisory session with two founders And one saying we should go this way and one saying we should go this way and they're really butting heads on it Basically, they're both right and they're both wrong. Who knows? They just need to pick one direction not both directions and begin getting it out there in front of customers A very common mistake that we see people make is when they try to keep everyone happy in their founding team By saying like cool. We'll just simultaneously test everything That is not a strong belief we weekly held that is splitting your time across too many things and not focusing The final point is create a behavior explosion And this is often where some of the most exciting companies in the world come from The quintessential example here is uber. So I think most of you probably would have heard the example that if you look at the Original market size for mini cabs in san francisco uber totally blew that out of the water They created a new market. They augmented the existing market And if as an investor you had discounted uber because the market wouldn't be big enough Then you'd completely misunderstood the importance of the behavior explosion that they were about to create Airbnb is another great behavior explosion Where okay, no one would have guessed that people would want to stay in other people's houses and pay them for that But even more importantly, I don't think anyone would have guessed the behavior explosion Where people then wanted these authentic experiences where if you're a gen z you kind of get ridiculed if you stay in a hotel You know real travelers stay at airbnb's and it means that airbnb has become the world's most valuable Hotel company without owning a single property. It's amazing The way the or the statement that you need to answer to create a behavior explosion is If x were easier cheaper or faster, there'd be way more demand to it and we'd be the gatekeeper So let's look at a couple of examples This is dishpatch and dishpatch is an ef company That was funded by andreason horror. It's a couple of years ago the behavior explosion that dishpatch was creating was And it was formed during the pandemic as you couldn't probably tell from the idea Was that it's really hard to get amazing fine dining at home And there's a bunch of people that for whatever reason can't leave home to get fine dining And i'm talking sort of michelin starred fine dining So wouldn't it be cool if they could get a meal kit delivered? By one of the world's best chefs that they can create at home Now that's cool, but actually the real secret was that the Way to do this and the demand and the behavior explosion that created was on the supply side So yes, there were plenty of customers that wanted this plenty of consumers that wanted this But the other side of the marketplace the chefs Who typically were constrained to delivering food within a restaurant that had a set number of seats Saw this as suddenly a really important revenue stream and so it meant that you had some of the world's best chefs And publish and publicizing this on their twitter pushing this out and creating this incredible noise for dishpatch that meant their growth just went through the roof Another example that is such it's such a clever idea. This is scarlet So in some ways it's a very very unsexy idea, but it creates the most amazing behavior explosion You may not know this but if you're building a medtech startup and you're building a software product Every time you want to release an update. It has to be approved by a notified body in the eu or the uk So this means if you're running a medtech startup Even though you should be moving like a software company You're often restricted to moving like a sort of you know a physical products company. You move very very slowly Scarlet has completely transformed the process of getting your Software updates approved. They've become a notified body and they've reduced the time for releases from months like 12 months down to five weeks The behavior explosion that they're then creating is it's now way easier way cheaper way faster to build generationally important medtech products So how do you know if you found a secret? So we've talked about the process of going through a secret We've talked about how important it is to use your edge to use that constraint How important it is to relentlessly speak to customers and how the very best secrets often create a behavior explosion But how do you know when you found it and again, is it like product market fit where you sort of know it when you see it? kind of There's a couple of questions that if you get this right you should be able to answer The first one is why is this a hair on fire problem? And for whom and we say hair on fire problem because if your hair was literally on fire You're probably not thinking about anything else. That is the problem that you want to solve When I do investment committees with startups what I often find is that many of them can't really articulate this The error mode I see is where someone says over the last four weeks was spoken to 50 different customers And the 50 different customers say x. I'm like, okay. Tell me about one customer. Okay. What was their name? What's their job title? What do they care about? How do they think about their budget? Tell me how they think about this problem What exact words did they use to describe this problem to you? Where do you think this problem sits in their stack rank of problems? It's amazing how many founders do breath and forget that the most important thing is depth The next question you should be able to answer is what is underrated about this problem by other people? Now if you're working on a true secret, it will be non-obvious It will be counter-intuitive and it will often be ridiculed To be honest, this was the early days of entrepreneur first We walked out into the london venture capital ecosystem and said we are going to find strangers And we're going to put them together and they don't even need to have ideas and we'll give them money And the venture capital ecosystem said that's crazy instead You should build a careers fair for students and we're like We're not going to do that and the reason we weren't going to do that was because we were hearing relentlessly from our customer That they wanted our product But the first three years of EF no one gave us any money It was impossible to I mean we ran on a very very tight budget for a long time because people thought the idea was stupid But the great thing was we had no competition for a very very long time So yes, it was hard to push through at times. We wondered if we were kidding ourselves But it actually became the most amazing foundation for our company Oops Oops The next point is around market size So how do you envision this becomes huge and again typically what I'll hear is this is a trillion dollar opportunity This is a multi billion dollar opportunity That's not what I want to hear What I want to hear is the story about how the market doesn't even exist yet And that the process you're going to go through is going to explode whatever market there currently is The story is more important than the time And then the final question why is no one else done this before why now what's changed what's special If you can get through and answer these questions with some really great strong beliefs weekly held You're on the path to having a secret Oops If you found this interesting and want to learn more Um, do buy a copy of how to be a fan. It's a great book a really great book One the startup book of the year last year. Um, thank you so much for listening. You've been an amazing audience I hope that some of you will consider Starting startups if you haven't already. Um, and if you do want to start a startup Do you check out entrepreneur first? We would love to hear from you. Thank you so much