All right, well, our next speaker is joining us from Amazon Web Services. Phil Estes' focus is on core container technology, another area where I hear some open source help could be needed with a large language model in generative AI communities. He works on offerings like Fargate, EKS, ECS. Currently, Phil is an active contributor and maintainer for the CNCF ContainerD Runtime Project. He participates in the Open Container Initiative as a member of the Technical Oversight Board. Today, he's going to explore the power of community in open source container runtime tools. Please welcome Phil Estes. Good morning, everyone. It's another great day at Open Source Summit. I hate to say this as exciting as my voice will get in the next 15 minutes. And I'll explain that with an interaction I had with a very sarcastic friend yesterday. He pulled me aside and he said, Phil, you're too high energy.  You're gonna lose people if you jump around on the stage and do your usual antics. So if you know me, you know, that's a big joke. And he's a very sarcastic friend. But regardless of that, no matter what you hear in my tone or demeanor, I am excited and honored to be here to talk about things that do matter to me and experiences I've had in open source. So I'd like to start with a story. It's not a very impressive story. It doesn't have a huge, exciting ending. But it does relate to something that my friend, Angel Diaz, said yesterday about first, and he was mentioning first, you know, do you remember your first computer? Maybe this week someone here is experiencing giving their first talk. But we're at open source summit. Does anyone remember their first contribution to an open source project? Maybe it's recent, maybe it's a long time ago. This screenshot is my first pull request to the Docker engine project in 2014, I think. And even though you can tell by the color of my hair, that was not the first software piece of code I'd ever written. But I felt like a newbie. Was like, man, this is scary, you know, create PR. That's like a scary step to take. Did I do everything right? Did I do the right signed off by for this community and their requirements?  But it was so exciting when I got an LGTM from someone famous, by the way, Jess Frizel. But it was amazing. It was amazing to all of a sudden feel a part of this community to feel like I had a role to play. I could help them, you know, make the project better. And like I said, this is not a very exciting story. This is an unimportant bug and an unimportant part of the interface for Docker back in that day. But it was my stepping off point that got me hooked, I'll say, on open source. And I only have a few minutes, so I can only summarize what led me to this moment for a few minutes to not bore you to death. But I came out of college and joined IBM and worked on OS2, and there's definitely some blank stares in the crowd. Some of you were not born by the time IBM put OS2 gently to bed maybe before you're born. But it was a great project for me to start my career. I had an engineering degree and so I wasn't really a software guy, but hired by IBM. It was kind of cool to work on an operating system and it was really at that interface with the hardware and device drivers and it had a kernel. And so it was a great project to cut my teeth coming out of college and just learn basic things about software development, how to work with others, how to debug a problem, how to submit a fix to a source code control system. And really over the next 20 years, I'm sad to say, I'm getting older, before I ever did that first PR, my world revolved around two major technologies. First was Java. IBM became a licensee of the Sun Java source code long before it was open source. And my team's job was to port that JVM to OS2. And so again, I learned a ton about taking a huge software system and making it work on a different operating system. And it was exciting to figure that out, to make it work. And around that time, I heard about this young operating system called Linux. And I thought, oh, this would be fun to just try out. The problem was it took downloading 15 diskette images stacked on my desk to install this thing. And IBM had this token ring network and the token ring driver wasn't part of Linux. So you had to download this random.c file, sorry, supply chain security folks. You had to compile this random file into your kernel so you get on the network. But my experimentation with Linux opened this new door for my career. Someone said, hey, why don't we take the JVM and port it to Linux?  Can you figure this out? And it was a really exciting point in my career to work with another IBM or to bring the JVM to Linux and turn that into an IBM product. But out of that, it was just kind of perfect timing. IBM created the Linux Technology Center. And Jim will finally remember Dan Fry, who's IBM executive who brought that organization to life, spoke in many of the LF events over the years. And so I worked on Linux for another decade, packaging it, customizing it for various IBM products, but never working on open source. It wasn't until that PR that I showed you earlier that I really experienced what it was to be involved in a community. And so I dove in after that first PR and did a bunch more PRs, became a maintainer. And I had my few seconds of fame when I got represented in a opening cartoon for one of the Dockercons along with Vincent Batts who's here this week, Jess Frizzle, Solomon Hikes and others. And it was, I was having a blast. But the point I want to make is not about me. It's about this community that I joined and the power, the feeling of being part of something and that everything I'd done with OS2 and Java and Linux, I could bring to the table in the Docker community and many others were bringing their experiences from other places. And some of you might say, well, I wasn't part of the Docker community, but I remember reading the new stack back in the day and it sounded like there were a lot of problems. Yeah, there was some big excitement around Docker and open source and Kubernetes. But I'll say for the most part that didn't impact the people who were dealing with that flood of pull requests every day in the Docker project. There was kind of a pressure cooker moment of just the project was so popular. There were so many people bringing their ideas and their interests to the project. But the cool thing that came out of that, even with all the complicated relationships and some of the fallout from those days, one of the coolest things about the power of that community is that that group of people has worked together in the OCI, in the CNCF, in Kubernetes, a bunch of new projects have formed out of that same group of people that you'll recognize many of the logos. And not only that, that group of people has continued collaborating around things like bringing C-Gurbs V2 support across all the ideas of runtimes and Run-C and Creo and Podman. We still work together in SIGnode and the runtime interface that Kubernetes uses to connect to runtimes. We still have brought rootless mode, not just to Run-C but to Docker, to Podman, to Container D to all these projects. And we're still working together on things like the OCI New Reference Types and Refers API and BuildKit has become its own project that many people use, not just Docker or Container D or other projects. So to me, this is the real power of that community is that there's continued collaboration and innovation. Now two years ago, just a little over two years ago, I joined AWS and one of the reasons I joined is that they were investing in Container D and I was seeing it in the community. They were using it in some of their services, they were contributing, and I was excited to come help them even contribute more upstream. And so while they had a small container runtime team, in the last two years we've seen that grow and we don't just contribute to Container D but there's dims many of you know from the Kubernetes community. He and many others are contributing upstream. We have SED maintainers on staff. We now have people contributing to other projects like Lima and Nerd CTL. And I'm short changing the rest of Amazon. This is my little corner of the world. There's many, many other projects that Apache projects and IoT projects and Java projects that Amazon is contributing to. But we don't just contribute, we also create. And so over the years, even before I joined and more recently building projects like Firecracker and Botteraka OS built around Container D and a snapshotter for lazy loading images on Container D that we recently launched last summer. And then one that's near and dear to my heart that I wanna spend a few minutes talking about called Finch in a minute. But we're not just doing contribution and creation, we're also investing in open source security. You probably heard a lot about the OpenSSF yesterday in Tracy's keynote. I've been tangentially involved in the OpenSSF. I was part of the original founding TAC. But we've even this week launched some new initiatives around the Cedar Policy Language which has used automated reasoning to prove out their language. And that's now open source. You can go to the booth today and see demos on that I think one and four. Our fine and fixed team has just launched SnapChange which is a fuzzing framework. You heard again about fuzzing from Eric in yesterday's keynote as an important part of securing open source. We've also funded several things in the OpenSSF like Alpha Omega which was mentioned yesterday. And so we're also funding Prosimo now for memory safety initiatives. If you're a Linux user, surely at some point you've had to type sudo or su. These are very important utilities that need to be secure. And so part of this initiative will be funding the rewrite of those in memory safe languages like Rust. So again, I'm proud of what we've been able to contribute, what we're creating, what we're funding around open source security. But I want to switch gears and use the last few minutes I have to again talk about Finch as just a really cool project that I've been involved in us creating and launching last year. I hope this isn't the computer you use on your desk. I'm pretty sure it's not. But with the economic times, watch out if your manager comes walking down the hall with one of these, hold on to your MacBook.  Most of us write Docker files that are meant to be turned into Linux containers that run on a Linux system. But I'm sorry we're here at an event that used to be called LinuxCon. Linux on the desktop is not here yet. We're still waiting. So if I'm writing on a system like this, I have to push that Docker file somewhere. Something has to trigger a build. I have to find compute somewhere to run it. And if I just made one simple mistake, now I have to do that cycle all over again. So developers love the tight inner loop of can I try this locally? Can I run it here, figure it out, make it work and then start to use automated CICD or push it to some compute somewhere? And so there's been a lot of innovation in this space.  This is hard data to figure out who's using what. But let's just admit that the line shared with enterprise developers are probably not on Linux. And so this space has been innovating all the way back to a project called Docker Machine in the early days of Docker. I just want a VM so I can run Docker inside of it so I can test out my containers. So we created Finch along these same ideas of we want to give Mac OS developers a simple command line tool to have that tight inner loop of development. And again, it's not something we started from scratch. It's built on existing open source, like container D and Lima and Nerd CTL and build kit. And so again, I've only got a few minutes left. I can't go into all the details of why we built it and how we built it. I did have the pleasure of helping write the launch blog that you can find online. We have a lot of ideas about offering an extensions framework and offering it on other OS platforms. So we'd love to make it a community. Like I talked about at the beginning, that power of community of being a part of something and contributing, we'd love for that to happen with Finch as well. So we would love for you to join us upstream. Again, not just in our project, but in the projects we depend on as well. And we'd love to have you participate in any way, report issues, contribute features, and give us feedback. Now, I followed someone who talked all about the coolest stuff ever, AI. When I was sitting two weeks ago in front of a blank PowerPoint screen, I was like, how do you get started? I was like, oh, I'm gonna ask an AI image creator to build me some Finches. And I even have the meta, there's a Finch contributing to Finch on his or her laptop here, but this was just my little fun to get my heads moving in a direction of creating the talk. But I titled this talk, Building Bridges. And if you know anything about image creators, I had to try several times to not give you nightmares of the gruesome things it created when I said, please build a bridge out of Finches. But this one was pretty cool. So I'd like to leave you with two things. One, find a community where you can experience what I experienced. Find some place that you can use your capabilities, the things that brought you to open source and use them. The second thing, as I just mentioned, we'd love to have you participate with us. We're definitely not creating a closed community, we're creating a community where you can participate, you can become a maintainer, you can help us move the project forward. So with that, thank you very much. Hope you have a great rest of your day at Open Source Summit.


This unit provides an overview of the field of psycholinguistics. First, we will define the hybrid term psycholinguistics and look at the main goals of the two disciplines. Then we will examine the main branches of psycholinguistics in more detail. Here is how we will proceed. First of all, we will look at the central definitions of the two component parts of this hybrid term. Then we will look at the main branches of psycholinguistics and their goals. And finally we will then concentrate on the main branches of the field. Let's look at some definitions first. Linguistics is defined as the scientific study of language. Psychology, the other term, signaled by this mind here. Psychology studies scientifically the human mind. Now, psycholinguistics is a combination of both. The goals are to study the psychological and neurobiological factors that enable humans to acquire, to use, to comprehend and to produce language. Let's briefly look at linguistics first of all to see where psycholinguistics within linguistics can be located. Now here you see the main branches of linguistics. Everything that has to do with sound, well, phonetics and phonology are the main branches. If you want to investigate the structure of sentences or words, you're concerned with morphology or syntax. And meaning is the big area where you look at the meaning of words, the meaning of sentences or even the meaning of utterances, semantics and pragmatics are these two branches of linguistics. Now linguistics can be combined with a number of, well, you might call them hybrid disciplines that introduce their scientific approaches and combine it with linguistics. For example, social linguistics. Social linguistics deals with the position and the use of language in society, dialectal variation and all sorts of things. Historical linguistics looks at the historical development of language and some historical cultural influences maybe. Computational linguistics, well, everything that has to do with computers, things like speech processing, machine translation and many more are dealt with in computational linguistics. Well, and here is our term psycholinguistics, psychology and linguistics. One of these hybrid or combinatorial disciplines that combine two fields with their insights with linguistics. Well, here are the main branches of psycholinguistics. And the central questions are in language processing, for example. The question is what happens in the human mind when we speak or when we listen? What is going on? What are the central processes and mechanisms underlying this very complex activity? In language acquisition, we're looking at young children and ask the question, how do they learn to speak?   But here now with the physical counterpart of the mind, the human brain. And the central question is how is language represented in the human brain? So these are the main branches of psycholinguistics. Let's now look at them in more detail. Language processing, well, two activities of language processing constitute the core area or the core of much of the work that is done in psycholinguistics. Speech production, signaled by this little symbol, speech production. That is the question, what is going on from thought to output to the actual production of a sound wave that is coming out? And the opposite or the complementary activity, comprehension. It's not just perception. There's a precise distinction drawn in psycholinguistics between perception and comprehension, but we will deal with that in another unit. Comprehension, that is, how do we interpret the input string and how do we identify linguistic units within it and how do we interpret this eventually in a conceptual way? How do we understand what is being said to us? It is really fascinating, not only from my point of view, to find out the phases and modules in these activities, which in reality last for less than a second, but are extremely complex, perhaps the most complex activity of human cognition. Well, the next big area is language acquisition. As you can see here, we are dealing with children. And the central amazing fact is that children, despite their limited mental abilities, acquire a language during, well, just a few years of their lives. And what is even more interesting is that they are confronted with an input that is degenerated, that is not complete, that is, well, sometimes even grammatically incorrect. So if you think about how parents address their children very often, then you find that it is some sort of very simplistic way of addressing them. So the language is not complete, yet they manage to acquire the grammar and all the rules of their mother tongue in a very brief span. So there are some central issues in language acquisition. First of all, we have to deal with acquisition studies. So how can we study young children? Well, they cannot answer our questions at a very early age, so we have to perform experiments with them. What are the central strategies that children apply when they acquire their mother tongue? For example, they over-generalize morphological aspects in what they produce. And then finally, what are the central phases? So what comes first? What happens next? How long are these phases? When do children start, let's say, pronouncing their first words and so on and so forth? So these are central goals in language acquisition.  And as you know, the use of speech is based on two central biological foundations. First of all, the central nervous system and then the vocal tract. Now the vocal tract is not really so interesting for neuro-linguistics, so it's the central nervous system. And in particular, the function of language in the human brain. Well, among others, the following questions are discussed in neuro-linguistics. You know, we have two hemispheres in the human brain. The left hemisphere and the right hemisphere. So what are the central functions of these hemispheres? Are they both equally well employed in the processing of natural language? Are there any brain centers here? Centers in the human brain, or this diagram indicates that there must be something in the human brain sort of centers in the human brain that are responsible for natural language.   And then of course a question, how does the brain develop during infancy? Let's summarize this. Psycho-linguistics with its three main branches. Language processing. Language acquisition and neuro-linguistics is an extremely complex field. You have to apply the entirety of linguistic knowledge from phonetics to pragmatics. But we will try and tackle this field in our virtual linguistics campus class with numerous animation simulations in order to make the complexity of this field clear to all of you.


Narcissists always do this at the end of a relationship. There is something that every narcissist will do at the end of a relationship. And this could be a way to identify whether or not you were dealing with a narcissist. Because they all do it. They have to do it. Because they think that it benefits them. They think that it is the most favourable thing for them to do. In any relationship, you might experience problems and difficulties. You might experience arguments and disagreements. This is normal. But in narcissistic relationships, these situations are dealt with differently. In a healthy relationship, both people will take responsibility. They will hold themselves accountable for their actions. They will recognise what they did wrong. And they will own up to it. Because they want to improve their relationship. They want things to be better. But narcissists do not hold themselves accountable.  And they don't want to deal with the consequences of their actions. So at the end of a relationship, the narcissist will always blame the other person. This is something they all do. When you first meet them, it's like you can't do anything wrong. Even if you do make a fault or mistake, they will overlook it. Or they will minimise it.  Because at that stage of the relationship, they are idealising you.  So they see you as being perfect. But in any relationship, problems and difficulties will arise. There will be arguments and disagreements. And this threatens to expose the narcissist's false image. Which is why they get very angry. Because in that moment, they feel like their false self is dying. It's like they're in a life or death situation. They feel like they're in a fight for their lives. So they will do whatever it takes to protect their false self. Even if they have to lie or distort the truth. They will blame you for everything. They will make you feel like you're not good enough. Because deep down that's exactly how they feel. But they don't want to reflect on it because it threatens their false self. So they have to see themselves as being perfect. They have to see it as though they didn't do anything wrong. Even if it was their fault, they cannot hold themselves accountable. Because then that would mean that their false self isn't real. Accountability is like death to a narcissist. But it is also the only thing that will make them change. Which is why there is no record of a narcissist changing their ways. Because they wouldn't know where to start. They would probably go insane or end up suicidal.  They can't deal with the idea that they messed up. So instead they blame you. They project their insecurities onto you. They shift the blame onto you. And then they spear your name. To get everyone to see you in the same way. To get everyone to validate the illusion. So that they can feel like they're okay. Because they don't care about the truth. They run from reality. Which is how they abandoned who they really were. And created a false self. If they abandoned their true self. It should reveal to you that you don't have a chance. Because they will abandon you too. If you dare to confront or expose them. Their false self is all they have left. So they will do whatever it takes to defend it. Even if that means lying or distorting the truth. They have to do that because their false self isn't real. So anything that is real. Threatens their false self. Which includes you.  It threatens to expose them. Which is why that is one of the first things they will target. They will target your credibility. They will target your quality of being trusted and believed in. They will say that you're crazy.  Because they know that's what they're doing. But they don't want to own it. They will disown any parts of themselves that they don't like. And then they will assign those traits to you. They see things in black and white. Where a person is either all good or all bad. And for them to see themselves as all good. You have to be seen as all bad. And they have to get everyone to see you the same way. To validate the illusion. To reflect back to themselves that they're okay. To reflect back to themselves that they haven't done anything wrong. They're very delusional people. Who are constantly on the run from reality. Which is why they all have some form of addiction. They constantly engage in escapism. Because reality is too painful for them to deal with. Which is why they abandon their true identity a long time ago. And created a false self. Because they just couldn't hack reality. They didn't have the qualities needed to cope with certain situations. Because they're emotionally underdeveloped. They experienced trauma and childhood. Which stunted their emotional growth. But rather than accept in this reality. They chose to create a false character who is mature and responsible. Which they displayed to the outside world. But when you get to know them. You realise that they're very different. They're very immature. They're very irresponsible. They don't want to take responsibility for anything. They hold you accountable for things. That they should be attending to. Because they just don't want to deal with anything. They're very lazy and unproductive. With anything that doesn't serve them. Yet they want to portray this image of them being so capable and efficient. But for them to portray this image. They need to have someone who they can blame for when things go wrong. Which is why when you first met them. You may remember that they blamed their exes or their family. They always had something bad to say about someone. Whether it was a waiter at a restaurant. Or their boss. They always made it seem like someone was doing them wrong. And they were the cause of some unfavourable situation. Narcissists never take responsibility for where they are in life. And that is why they always stay the same. Because they're always blaming other people. Instead of looking at themselves. And recognising what they're doing. Accountability is the key to success. And that is why these people remain stuck. That is why they're never going to change. Because they can't look at their own actions. Which got them to where they are now. Instead. They choose to blame everyone else. So although they may think that they're distorting the minds that they are winning by blaming you. It's just stunted their growth even more. It's what keeps them stuck at the emotional development of a two year old child. It's what causes their endless temper tantrums to persist. Because they just can't accept that they're just like everyone else. They can't accept that they make mistakes. They can't accept their flaws. They can't be vulnerable. But this is something that all Narcissists will do. At the end of a relationship. They will always blame you. They will exaggerate your faults and mistakes. And they will minimise their own. They will lie and distort the truth. And it may seem like they're running from the relationship. But they're actually just running from themselves. Thank you for watching. I hope this video resonated with you. Please like, comment, share and subscribe. If you would like to donate. My PayPal link is in the video description. Coaching queries. You can email me at coaching at Narcisfy.ver.co.uk. Thank you for watching and I'll talk to you soon.


When I use my leg and I would bump with my leg, I want you to think of this, keep your leg very relaxed. Don't tighten up your muscles and your thigh or in your calves, don't do that. What I want you to do is this, think about from the hip and the knee down, loose leg. So this is how I get firm with my leg, ready? I keep my leg loose. I keep my leg loose.


A single serving of blueberries can help mediate the arterial dysfunction induced by smoking a cigarette. They investigated the effect of a single serving of frozen blueberries on young smokers. Smoke a single cigarette, and the amount of your arteries to relax naturally drops 25% within two hours. But eat two cups of blueberries a hundred minutes before, and that same cigarette causes less than half the damage, demonstrating that a single big serving of frozen blueberries could counteract the artery dysfunction induced by smoking. However, of course, it should be noted that blueberry consumption cannot be considered a means of preventing health consequences due to smoking. This can only be realized by stopping smoking, or even better, not smoking in the first place. Two cups of blueberries is a lot, though. Yeah, you could easily chug those down to smoothie, but what's like the minimum dose? Boy, you didn't know until a group of British researchers decided to put it to the test to enable them to do a double-blind study. They had to create a placebo-controlled fake blueberry drink, so they used a freeze-dried wild blueberry powder to give people the equivalent of 3 quarters of a cup of fresh blueberries, one and a half cups, one and three quarters, about three cups, or four cups. They concluded blueberry intake acutely improves artery function in an intake-dependent manner. Okay, so what's the optimal intake? After the placebo, nothing happens, but after eating one and three quarters cups worth of blueberries, a big spike in artery function improvement within just one hour of consumption. And that seems to be where the effect maxes out. Less than a cup is good, but between one and two cups seems better, with no benefit going beyond that in a single meal. Can you cook them? Look what if you put them in a blueberry pie or something? The same remarkable improvement in artery function baked into a bun, just spiking an hour later since solid food passes more slowly through your stomach. And then if you eat blueberries week after week, you get chronic benefits, too, in terms of reduced artery stiffness and a boost in your natural killer cells, which are one of your body's natural first lines of defense against viral infections and cancer. But wait a second. How can blueberries have all these amazing effects if the anthocyanins, the blue pigments in blueberries, purported to be the active ingredients, hardly even make it into our system? Women were given more than a couple blueberries to eat, and they couldn't find hardly any in their bloodstream or flowing through a urine. Here's what's called a chromatogram, with the spikes showing all the little anthocyanin peaks in blueberries. Here's your blood before eating blueberries, obviously no signs of the pigments. After one hour, you start to see them appear, and a few hours later they become a bit more distinct, but all in all, just a few billions of a gram per milliliter show up. So either anthocyanins are extremely potent and therefore active at low parts per billion blood concentrations, or somehow their bioavailability has been underestimated. So researchers decided to radioactively tag them and trace them throughout the body. What happens is that blueberry pigments are metabolized by our liver and our microbiome, the good bacteria in our gut, into these active metabolites that are then what's absorbed into our system. So it's kind of a team effort to benefit from berries, and that would solve this mystery as well. Have you ever noticed this second spike in benefit over here at six hours? How does that make sense? Well, some of the metabolites peak in the bloodstream within an hour, but others ramp up more slowly, especially if the berries have to make it all the way down to the colon. And it's not just spikes at one hour and six hours. If you track them out even further, some go up even more. So like a day later, you may still be experiencing berry benefits as our gut bacteria continues to churn out goodies that get absorbed back into our system, feeding us as we feed them. Eating blueberries can so feed our good bacteria that it's like taking a natural probiotic, a win-win, all around.


Sesame Street and the Electric Company are teaming up to give children a new online resource to help them deal with the difficulties of having a parent in the military. Military children can now go to familiesnearandfar.org and find activities aimed at helping them express what they're feeling during difficult times such as when a parent is deployed. In the past, Sesame Street has helped younger kids deal with these issues and this new resource is aimed at children ages 6 to 9. Kids are a little bit older, they're starting to learn to use their words, they're starting to read and they understand the concepts a little better so they can get their emotions and express their emotions. They also have a new mobile application to find out more go to familiesnearandfar.org. Staff Sergeant Mike Hutchinson, Joint Base Meyer Henderson Hall, Virginia.