Hello, I'm Philip Kahn. Today we're gonna talk about where we are overall with the coronavirus COVID-19 pandemic. Let's get into it. For our overview, I'm gonna talk about the little bit of history and sort of the terms that we're using, the global situation, briefly where the United States fits into that, our particular kind of failure in this pandemic, and then the crisis that this has generated, a few different crises that are obviously all overlapping. And then some comments on the future. A pandemic, a pandemic comes from Greek, pan and demos, it's all people. We use it in modern times to mean the worldwide spread of a new disease. This particular pandemic was declared by the World Health Organization, the authority for things like this, on March 11th of this year, 2020. The way to think about the relationship between a pandemic and an epidemic, an epidemic is the spread of disease. Our epidemic here in the United States is part of the global pandemic. So we're living in a pandemic and you can describe the epidemic here and there in our situation. There have been a number of pandemics in the past. Here are a few, the big ones in the last 100 years, starting with the great so-called Spanish flu, the 1918 influenza pandemic, probably did not come from Spain. About one third of all people in the world were infected during that pandemic and about 50 million people died, including more than half a million Americans. Remember the world population was a lot smaller back then. That was a very, obviously a very bad pandemic it spread all the way around the world sort of twice. Other flu in epidemics that became pandemics in 1957 and 1968 killed about 1 million people each, those influenza pandemics. One of those viruses is still sort of running around now, but not as bad as it used to be. We had the precursor to today's coronavirus pandemic was in 2003, the SARS pandemic, which only killed about 800 people, but spread very virulently and was extremely scary before it was controlled. The much larger swine flu, so-called swine flu or H1N1 pandemic in 2009, which killed about 200,000 people, not as many as we are seeing die this time. We are already up to almost a million people died and you'll see millions and millions of cases around the world. That's a little bit of context for this pandemic in light of previous ones. We call it coronavirus. There are a number of coronavirus diseases that affect humans and other species. This one is the novel coronavirus 2019 because it was discovered in 2019. We are pretty sure it came from a bat to a person, possibly through some other species. So somebody ate a bat or a bat bit somebody and then transferred from that animal to people in or near Wuhan, China late last year. The virus SARS-CoV-2 causes coronavirus disease, COVID-19. So we can call it coronavirus, we can call it COVID-19, which is the disease of the viruses SARS-CoV-2, okay. Why is COVID-19 so bad? Why is this epidemic so bad? Well, because it's a novel disease that means we are not immune to it. So as far as we know, nobody was immune to it when this started and it's very highly contagious. So it spreads very easily between people and all they have to do is interact or be close to each other. If there's not taking any precautions and the virus transmits and nobody is immune. To make matters worse, it transmits asymptomatically. That is, there are people who show no signs that they are sick who can transmit it. So it's hard to avoid people who are transmitting the disease. It transmits through aerosols, which are tiny airborne particles that you can get just from breathing. So you don't have to spit or cough or sneeze on somebody to transmit the virus. And on top of all that, it has relatively high mortality. Our seasonal flu infection fatality rate that is all the people who have the infection out of every 1,000 of them less than one dies somewhere between 0.3 and 0.7 normally die from the seasonal flu. And the COVID-19 infection fatality rate is probably about 10 times that. We're not exactly sure, but something like six to 10 people out of every 1,000 who get the infection seem to die. So that's a much higher fatality rate than flu. And of course, in addition to all the people who die, many other people are seriously ill or suffer other health consequences from getting the virus. To show where we are in the world pandemic right now, here are the cases and the deaths. Notice the scale on these two figures is different. So we're up, the world overall is over 20 million cases approaching 25 million now in late August. These are cases that are diagnosed or so-called confirmed cases. We think a lot more people have been infected with the disease, but we don't have a count of them. I show the United States on here for comparison, the United States is over 5 million cases out of the world's 20 something million and rising. So we're taking up a big share of the world pandemic here. In terms of deaths, the world has something over 80,000 confirmed deaths from the virus, the United States approaching 200,000 of those. So approaching a quarter of the global deaths have occurred in this country. So let's put that in context. Here's the world distribution of cases. You can see it has spread around the world, started in China, spread to Europe, spread to the United States. The US now has the most confirmed cases of any country, 5.5 or so million. You see the other biggest countries in terms of raw numbers are India, approaching 3 million, Brazil with more than 3 million. Of course, those are countries with big populations, especially India. You can see a million or so spread around Europe and Russia approaching a million, half a million cases in South Africa, most of the rest of Africa, not that many cases yet, still spreading there and hopefully not as bad because of precautions taken. It's global around the world and the big countries you can see, US, India, Brazil, Russia and some places in Europe. Just looking at high income countries to sort of see how the United States compares with its peers, sort of other, these are countries with at least $30,000 a year annual income and 5 million population. So what we call high income countries and not that small. The United States in this group has more cases for every 1,000 people in our country than any other country by quite a bit. Israel is next in Singapore. We're up around 17 cases out of every 1,000, 17 cases for every 1,000 people in our country. You can see if you get down to Poland, Denmark, Germany and so on, it's several times less than that. In terms of deaths per million in our population, there are five large rich countries with higher death rates than we've had, Sweden, Italy, Spain, United Kingdom and Belgium. That's on a population basis and then all the other rich countries had fewer deaths per person than we did. But this is a little bit misleading because it doesn't show the trajectory of what's happening now. That's what we really have to understand. So here I show the United States in the red line and all the other rich countries in the black line and then some of the specific, the larger ones shown in little faint gray lines so you can see what's happening. Look at the figure on the left side first. This is the daily deaths. You can see that in late April, when we had our peak, there were those five countries with higher peaks than us, including much higher like Italy and Spain, many more deaths at that time per person in their populations. We all started to decline after that but the key thing is that those countries had a faster decline and a more continuous decline. So by June, our daily deaths had stopped declining by the end of June and actually started rising again in July and August, which is virtually unique in the rich countries. And now we're at about 10 times or more deaths per day, relative to our population than the other rich countries of the world. The figure on the right shows you the deaths per million population if you add them all up. So we're up over 500 deaths out of every million Americans, the other rich countries of the world down around 200 per million. So the US has high rates, but more importantly for now, the US has not had that steep drop in rates down to a manageable level of the pandemic. So we still have something of a raging epidemic compared to these other countries. As you probably know, the impact of this epidemic has not been equally shared across the country. There's very big geographic concentration for example, New York and Detroit and New Orleans and Houston and places that had lots and lots of cases. But overall, as it is spread around the country, we have seen a very big disparity by race and ethnicity. Black Americans have had the highest death rates, 85 per 100,000 people. Whites, Asians of Pacific Island just had the lowest with Hispanics and American Indians in between. We can talk all about the long run and short run causes for this, the discrimination that leads to the other things, the inequitable access to healthcare and good healthcare, working in occupations that involve frontline or central services where people are interacting with members of the public at work, inequalities in income and education and wealth, sort of the resource that people have to deal with or prevent a disease like this and then housing, quality and quantity, so how crowded and where people live and so on. So all of that together, coming together to produce very big disparities by race and ethnicity. Now let's look at more specifically what went wrong in the United States. I'll talk about a few things that Trump did, President Trump. Before all this happened, he was already cutting funding for the Centers for Disease Control and Prevention. You can see it was up around over seven and a half billion dollars per year two years ago and already cut down by about a billion for the 2020 budget. So we're already cutting down our investment in public health infrastructure, which was not a good idea as we now know. More specifically, President Trump canceled, closed down a pandemic office operated by the National Security Council, which was supposed to stay on top of and coordinate responses to global disease outbreaks. When that happened, there was a very clear message from the Center for Strategic and International Studies here, but many others also, it's unclear who would be in charge at the White House with the NSC not doing this in the case of a pandemic and that turned out to be true. Trump specifically ignored warnings very close to him, despite claiming falsely in March that nobody knew there would be a pandemic of this proportion, nobody's ever seen anything like this before, which as I just showed you, totally not true. In fact, in his own administration, they were running a functional exercise scenario. They were gaming out what would happen in the case of a global pandemic that came from China and it had all kinds of good information and recommendations that were all ignored. There were warnings broadcast out through the popular media also. Here's an article by journalist Ed Young in 2018. The next plague is coming as America ready. The US is disturbingly vulnerable in some respects becoming quickly more so. Public health programs are low on money, hospitals are stretched perilously thin, crucial funding is being slashed, that's 2018. Even Joe Biden running for president last fall said we are not prepared for a pandemic. Trump has rolled back progress, Obama and I made to strengthen global health security. This was not that much of a surprise. The details are always a surprise, but the fact that this was inevitable at some point and that we were not prepared was no. In addition to those programmatic failures and bad budget decisions, when the pandemic began and as it spread, the president was more concerned with how it made him look than he was with actually dealing with the epidemic. So he said over and over again that things were going fine. They were not going fine. We have a totally under control. It's one person coming in from China and we have it under control. It's gonna be just fine. And we think we have it very well under control. We have very little problem in this country at this moment, five. And those people are all recuperating successfully, but we're working very closely with China and other countries and we think it's going to have a very good ending for us. So that I can assure you. Now the virus that we're talking about having to do, a lot of people think that goes away in April with the heat, as a heat coming in. Typically that will go away in April. We're a bridge, we have 12 cases, 11 cases, and many of them are in the chain now. We have it very much under control in this country. And again, when you have 15 people and the 15 within a couple of days is gonna be down to close to zero. That's a pretty good job with that. It's going to disappear one day. It's like a miracle it will disappear. And we're prepared and we're doing a great job with it and it will go away. It was obvious at the time that that was all wrong and self-serving on his part. So let's look at these failures. Let's look at how the failures compounded as the epidemic rolled out across the country. From the very beginning, we did not have enough testing. So we did not know who had the virus and who didn't. That meant we couldn't do contact tracing, which is when you find out someone has the disease and you immediately find out who they've been with and you make all those people stay home so they don't spread it. You can only do that if you know who has it. We didn't have enough testing from the very beginning. Partly for that reason, we essentially did not contain it. It spread. We didn't do anything to stop travel within the country. So there was nothing to stop people from leaving New York and going to New Orleans for Mardi Gras and bringing the virus with them, for example. And the numbers got too big. The testing and tracing only works if you have low numbers. Once we realized, we, meaning the federal government caught up with everybody else and admitted it was a very serious problem, the policy efforts at that point were slow and weak. In other words, we never had a very strong lockdown. We never closed everything. We never stopped travel within the country and so on. When the cases were exploding and hospitalizations and deaths were out of control, especially in the New York area, there was gross mismanagement of the vital equipment and supplies and professionals needed just to handle it. And so more people died than should have died even once they already had the virus. We had a whole category of outbreaks in institutional settings, in nursing homes, in prisons and factories that were largely unchecked, especially at the beginning. And then those became epicenters from which the disease spread out into their local communities. And the communities where nursing homes and prisons and the meat plants especially are largely low income and minority communities. And repeatedly like you saw from the Trump clips, but much more than just that, I'm a mix of happy talk, mixed messages on the advice we were getting, a general attitude, a cynical or negative attitude about science and expertise coming from the top. A lot of conspiracy theories I'll talk a little bit about. And then this sort of useless kind of hero talk where warriors were tough, were strong. That's not how you fight a virus, basically. You fight a virus by acting weak and staying home. And we didn't do that. So I'm gonna give just one little case study to show how another country dealt with their worst epidemic and ended up with a better outcome, in a better place now than the United States is. And this is Italy. And you can see Italy had a huge spike in deaths. And this is per million population. So it's, or holding the population size constant between these two countries. A huge spike in deaths in March, about a month before ours, a steeper and greater rise in Italy. Italy, one of the first countries to have a serious outbreak. It spread all around before, we knew what was happening sort of. And they were just figuring out what to do as they went. But then you can see the very steep decline they had ended up much steeper than ours. And now we have more than 10 times the deaths ongoing than they do. They're getting ready to go back to school. Here I put some lines that show what happened in Italy and how they did. Just to give us a sense of the things that we didn't do that helped explain why we have so many more cases and deaths at still at this point than Italy does. So you see the very first red line there, the first two deaths discovered at the beginning of February. And the first thing they did was lock down a few towns in the North with checkpoints and barricades. And they've gone to just contain it. It didn't work. It was too late. The virus that already spread out from those few towns. And so by early March, they closed down the whole Northern region of the country and tried to contain it there. And again, they restricted movements. They had police and checkpoints and tried to contain it in that part of the country. Within a week or so of that, they closed all schools and all sporting events around the country. And shortly after that, they realized it wasn't enough. They already had cases around the country and they went into a national lockdown around the second week of March. Their lockdown was much stronger than anything we had in this country in that you could not leave the house unless you were going to the doctor to get necessary supplies or to go do an essential job. And the police would stop you and you had to explain what you were doing. We had nothing like that in this country. You could not travel between regions of the country by and large. You couldn't go from one city to another or one state in the country to another. We never had that restriction in this country.  Factories were closed. Anything that was not an essential workplace was shut down. You can see they did that for about five or six weeks. And then they were able to start reopening. The debts were falling, but the debts that we count reflect cases a few weeks earlier. So as they were seeing the great decline in debts, the cases were already falling faster than that. They were able to do some partial reopening. They allowed people to travel within their home states. They opened up some factories to get the economy going. A few weeks after that, they had further reopening. They allowed most businesses to open with social distancing. By now they're wearing masks. They allowed travel only within regions but still not letting people move all the way around the country. Then by the third week in May, they're opening pools and gyms and other sort of businesses that involve more close physical interaction and all the way out to June 15th. They're opening theaters and they're pretty close to back to normal with distancing, with masks. And now they have a low enough number of cases that they can do testing and tracing, isolate people who get infected and manage contain the epidemic. We never reached that level of containment in this country. We never had that level of closure and now we never had a small enough number of cases that we could jump on them, isolate them and stop outbreaks as they occur. So our epidemic is relatively uncontrolled. Still at this point, it's only controlled to the extent that people are wearing masks and staying home as much as possible. So that just shows a successful case and an unsuccessful case and sort of what it would have taken for us to do what Italy did. So why did we fail so badly? A number of reasons. I mentioned the bad decisions that Trump made, but we have some things that followed from that or related to that, including this very partisan attitude toward the science of the pandemic. These are four questions that have correct answers and Republicans get the answers wrong much more than Democrats do because they believe what their political leaders tell them instead of science and the facts. And that's a defect in our culture that that happens. For example, social distancing measures are helping a lot to slow the spread of the virus. The first question, that is 100% true. Liberal Democrats 76% agree with it, only 47% of conservative Republicans. The coronavirus spreads more easily than other infection diseases. Absolutely. There are some that spread more easily like measles, but most do not. Democrats know that much more, 78% than Republicans, 58%. There's not enough testing. This is uncontrovertibly true. It's just a true fact. 82% of Liberal Democrats know that 31% of Republicans. So science can answer these questions, but because of the way our politics corrupts our science or our science fails to penetrate into our political bubbles, we are impaired from being able to do smart things. Worse than failure to be educated are the efforts to miseducate or diseducate, spread misinformation and disinformation. We have raging conspiracy theories in this country, which are partly related to politics and partly not. The so-called pandemic is the idea that the whole thing is on purpose for profiteering and so on. Totally not true. There's the idea that the virus is spread or enabled somehow by the 5G cell phone network, also completely not true. There's the idea that masks are bad for your health. There's some kind of plot to weaken us, also completely not true. And then there are the fake cures and treatments, many of them spread by important people, including the president. He retweeted this about high druxichloroquine. I'm saying it should be over the counter. It would solve everything. It just is not true. So there's so much disinformation in our public square that is very hard for people who are not full-time debunkers to figure out what the true story is. On top of this, we have racism and xenophobia affecting how we react to the pandemic. A lot of white people think it is a disease of non-white people. Just like a lot of people in Texas or Arizona thought it was a problem in New York. The president himself has spread a lot of anti-Asian racism, referring to the ugly face of the virus and blaming China, calling it the China virus. There have been vandalism against Asian businesses, random attacks on Asian people. You see the Asian face on the pinata in a restaurant in St. Louis and these sentiments from the president. It's got all different names. Wuhan. Wuhan was catching on. Coronavirus, right? Kung Flu. You can see the crowd, hear the crowd cheering on, egging him on to say the racist smear. Then when it comes to our southern border, the president has also maintained that border control is key to stopping on the virus from spreading. And at this point, probably it's better for Mexicans than for Americans to have the border closed, but he has continued to press this message as well. Using our emergency public health authorities, we prevented a coronavirus catastrophe on the southern border, shutting down human smuggling and swiftly returning the crosses. We call them crosses. They cross, now we bring them right back in the old days. It would take years to get them back. They wouldn't get them back. Without these public health measures, the southern border would be a global epicenter of the viral transmission. Yes, well, the southern border is a global epicenter of virus transmission on our side of the border. And the Rio Grande Valley in particular has been extremely hard hit in Texas. Okay, so let's talk about the crises that have followed from the disease epidemic. Probably most prominently, the economic crisis. This is the number of people employed, not counting farmers, the number of people employed from 2000 to the presence over those 20 years. You can see it was about 130 million, those are thousands. So it's about 130 million people employed in the early 2000s, rising, rising, rising to what we used to call the Great Recession, 2008, a big drop, Obama took office and had to dig out of that hole. You can see the rising, rising, rising number of employed people. Of course, the population growing too. Up to over 150 million employed people by the time Trump is in his third year. And then April of this year comes and it just collapses. 20 million fewer people employed suddenly in one month. It may in some ways worse than that because some people had to change jobs and so on so they count as employed but they're not in the job they were in before. We've chipped back a little bit of that but the economic crisis has been extremely severe and tens of millions of people have been extremely hard hit by that. You can juxtapose the food lines in Queens, New York, now versus lines in New York City during the Great Depression, 1931. People are lining up for free food. They have no money, they have no jobs. We have a crisis in education that comes from having shut down schools which was the right thing to do from a public health point of view but still caused massive educational disruption which will widen inequality. You look at the first figure here, this is from a company that tracks online math participation by students. You can see in the higher income zip codes math participation online dropped about 20% right away in March but it was dropped over 60% in low income zip codes and then the richer zip codes bounced back, got everybody online and back to work by May but the poorer zip codes never did. The second figure shows some estimates of how many months of learning we're going to lose if we don't have in class instruction this fall which we're not going to for a lot of the country and judging by the estimates of how many people get online, how many people participate, and they made some educated guesses and estimate that overall we'll lose about seven months of learning on average but it's more for blacks and Hispanics than for whites and much more for low income students. That's based on the participation rates that we're seeing now. So an extreme education crisis and one that is widening inequalities. On the other hand reopening schools carries great risks which are also unequally distributed. As schools have reopened we've seen viral outbreaks in colleges also but I'm thinking here about K through 12 schools and so we have to face the decision of keeping schools closed and harming the education of children versus keeping schools open and having the virus spread uncontrolled. The little bar chart up there shows the much higher five to eight times higher hospitalization rates for black and Hispanic versus white children, just much more likely to get coronavirus and get very sick from it than white children. The figure below shows the percentage of seniors who live with a child. So if we open schools, this is who we're putting at risk and you can see only 4% of white seniors live in a household with a school-aged child compared with 11% of black seniors and 13 to 19% of people in other groups. So if we open schools, we're putting these older people at greater risk and that's not equally distributed. So there's no good choices. The epidemic has produced a family crisis in a number of dimensions. One is violence and abuse without adequate intervention. We don't have great data on this because the way we collect data on this is from people leaving their houses and doing things like going to work and going to school and going to the doctor and a lot of that has not been happening. So for example, one study found that there were fewer visits to the emergency room with sort of injuries related to domestic violence, but the injuries there were showing up were more serious. So it looks like a lot of people are getting injured or having abuse happen in their homes but are not making it to the emergency room unless their injuries are very serious. So this is a bad problem. We don't know exactly how bad yet. In terms of families also, we have an unequal gender impact of the shutdowns that we experienced. So that as the figure shows, the group with the most likely to drop out of the labor force from February to April in that key period were women with children and school ages. So we have women dropping out of their jobs more than men doing more of the childcare and housework at home. Although there's also evidence of men sharing in those burdens when they are home. So it's gonna be interesting how that sorts out. And the care work burdens themselves, taking care of children, taking care of elders without a lot of the supports that we have in normal times have made things really hard for a lot of people and a lot of families. So that's something we really have to watch. On top of this, an extreme mental health crisis and this is very extreme. The stress of fear from the pandemic itself but also the isolation from being alone or living alone, being separated from friends and loved ones, the despair simply at all the bad news and the likelihood that bad news will continue and also being separated from services, whether medical or counseling or other services that people need to keep their lives in order. This has produced a lot of depression, anxiety, suicidal ideation that is thinking about suicide. Just wanna pause to say here, if you are anxious and depressed, if you are thinking about suicide, you are obviously not alone. A lot of people are, a lot of people are not talking about it. There are the numbers there for you to call and seek help at any time. And you should not feel like you're the only one or you are burdening anybody by asking for that help, so please do. I was astounded by this figure put together on the percentage of young adults who were seriously considering suicide in the past 12 months. Before this year, we would have been pretty troubled. We were pretty troubled by the rise from about 7% in 2010, up to 11% of young adults seriously considering suicide in a given year, up to 2018. And now in a survey taken in June 2020, 26% of adults under age 25 reported seriously considering suicide in the last 30 days. So obviously in a very extreme time and we know a lot of people are really hurting right now. So something we really have to try to address. So where are we gonna go here? What's gonna happen next? Well, here's a kind of a worst case scenario, one way to think about it. We've had about 177,000 deaths as of today out of 5.7 million cases. So our case fatality rate that is the number of people who died for every case we had is about 3%. So about 31 out of every 1,000 people that we know got it have died. However, we think that maybe as many as, 10 times as many people have had it than we think. Maybe 50 million cases already. And maybe our infection fatality rate as opposed to the case fatality rate is only three out of 1,000. So that is a lower death rate in a lot more cases. Maybe we've already had 50 million people infected and a lot of them with no symptoms or minor symptoms. So if you play that through, if we do kind of a worst case scenario with those numbers, if we do nothing to stop it, the virus spreads all around. Eventually, and this is pure speculation based on other diseases, it might be that when it gets to about 70% of people, so we've got 330 million. So when a few hundred million people have had this disease, maybe we would approach what they call herd immunity where the virus is people are breathing and it's sneezing it out and it's just running into people who are already immune. And so the spread rate drops. If that's true, 230 million people end up getting it, that might mean 700,000 deaths. Right now we're at less than 200,000 deaths. So as bad as that has been, if we don't get this under control, it will essentially probably more than triple. Or we figure out how to treat it better, which they're obviously working on, or we have a vaccine or multiple vaccines that can either slow or maybe even stop this transmission. So we're somewhere between now approaching 200,000 deaths and maybe something like 700,000 deaths. And the question is, can we slow that down as much as possible so that we can get some kind of medical intervention to prevent getting through all those deaths? When will it be over? Well, it seems likely there will be waves of outbreaks for months, hopefully not years, but it's not contained medically. If we're not really shutting down the country, it will be spreading around and we will be reacting locally, staying home as much as we can or when we find out that there's an outbreak and so on, unless we really change what we're doing in terms of the government. We can only do an effective tracing and isolation policy when the numbers are down lower. If there's 100,000 people a day or 50,000 people a day getting it, you can't make all those phone calls and find out who they've been interacting with instead of all home, you can't do that. You need to have the numbers down before that's really effective. Regardless of what happens here, we're not gonna be traveling around the world much for the next months, years, we don't know. So the world is narrowing for a lot of people in terms of the travel that they're not doing. We don't know when vaccines or treatments will be ready. They're testing vaccines. If they work, we don't know how well they'll work. We don't know how safe they'll be. Unlikely to be affecting us personally very much in less than the next 18 months, but that's speculation. The whole question of herd immunity is actually unknown. That was theory what I said before. We could have, we might not have herd immunity even when we get to 70% people could maybe start getting infected again. We don't know yet. So that's still up in the air. And then how will the world change? That's a big question. That's something that we wanna think about. And try to prepare for as much as possible. So where are you in all of this? Well, this is my advice. Follow the public health advice, the real public health advice. Don't jump on the bandwagon of every fad or something you hear, but follow the solid public health advice from especially your state and local governments. Your sociology professor is probably a good source also. If you can stay home, stay home. It's boring. People are very frustrated. People are lonely. It may be impossible to really pull it off, but if you have the choice, if you can, it's just better to stay home. Even if you're not infected, you're not dealing with somebody else who's infected. You're just adding people to the mix and the fewer people moving around, the better. Take care of yourselves. This is extremely stressful. You've not experienced anything like this before and neither is anybody else alive on earth today. So keep an eye on yourself. Keep an eye on your friends and neighbors and your relatives and try to figure out what you need and what they need and provide it. If you are distressed, sad, upset, anxious, depressed, one kind of behavior that may be helpful is to find ways to help people. That can be done online. That can be done with money. That can be done with different kinds of volunteering, political activism, interacting with people interacting with people who are themselves struggling in different ways. Lots of ways you can help others which gives you a sense of purpose in your life. So that's very abstract, but it's advice. And then to think about the future. Where are we going after this? The world is gonna be very different. Politics will be different. Society will be different. Science will be different. Your career plans and hopes and dreams may have to be radically altered.  But it's a time to think big. We are probably gonna get through this and when we do, we're gonna have the opportunity to make some changes around here. So think about what you might like to see done and start thinking about how you can get there.


There are no rules for good photographs. There are only good photographs and some add-ons. Create U Heart Institute of Photography


Hi, my name is Dan Sambore and I'm a second-year master's student in the Atmosphere and Energy program at Stanford. My research focuses on how to design renewable microgrids quickly and more accurately so we can bring clean, reliable, and affordable electricity to remote areas of the globe. Here at Half Moon Bay, I plan to design and build a microgrid to move my research into practice so we can learn firsthand how to provide renewable energy to those who need it most. First, in order to design renewable energy systems, you need to know the resource available. Thus, I have built a weather tower to record wind speed and solar radiation. However, while accurate, collecting enough data takes time and only one specific location is measured with a met tower. Thus, part of my research also includes innovative resource analysis methods such as using drones to determine resource potential at various points in the site quickly and cheaply. Next, the optimal energy technologies must be designed to harvest the resource and meet the load at the site. This requires tailoring the technologies to fit the topography, demand, and regulations at the location. For example, here in Half Moon Bay, we will not be able to put up a large conventional wind turbine due to potential visual sites from scenic Highway 1. Thus, I'm working with John DeBerry to install vertical access wind systems at the site that take advantage of the abundant wind resource within a smaller size and profile. Overall, by employing new design methods, analyzing innovative renewable technologies, and integrating them in an optimized way, I hope to improve the entire microgrid value chain one step at a time. We believe that everybody in the world should have a right to clean, safe, and reliable electricity.


Less than 5% of people can solve the following riddle. You are shown 4 cards on a table. For each card, one side has a number and the other side is coloured. Below the cards is a rule. If a card has an even number on one side, it must be red on the other. Now, one of these cards breaks this rule and your job is to fish it out. You can turn over any card you want, but if you choose a card which doesn't need to be inverted, this will count as a fail. Which card slash cards must you turn over? Pause the video now to think about it. The correct answer is to turn over the 8 and the blue card. Remember, the rule was, if the card was even on one side, it must have a red dot on the other. Since the rule is only about even numbers, we don't need to worry about cards with odd numbers. Now, a common mistake is to choose the red card. But, if you turn over the red card and it has an odd number, this doesn't actually break the rule. The rule was only if a card was even, did it have to be red? So, you need to check the 8 to make sure it's red and you need to check the blue card to make sure there's not an even number on the other side. This might be a little confusing. But, what's interesting about this riddle is that there are many variations and some are much easier to get than others. For example, try this one. You are given 4 cards again. By this time, the 4 cards represents 4 people drinking at a party. One side has a person's age and the other side has their drink. The rule is, if you're under 18, you are not allowed to drink alcohol. So, which cards should you turn over? Pause now to think about it. The correct answer is 16 and alcohol. Once again, we don't really care about the 41 year old or the person drinking apple juice. All we care about is whether the 16 year old is drinking alcohol and if the person holding vodka is older than 18. People tend to be better at this version, but why? The logic behind it is the exact same. One theory is that humans didn't evolve to solve logical problems in the cold hard way of the first problem. Instead, we are social creatures and as such, are much better at solving problems in a social context. So, how did you go with these riddles? Also, if you're a content creator, it's probably not likely that you've evolved to track all of your work online. Copypants.com tracks your images and helps you engage positively with the people using your work. They're the sponsors of this video, so check them out. It's free to sign up and you can get $30 of in-app credits when you register with the code P2G.


Russian stealth kamikaze drone undergoes tests in Ukraine operation. A loitering kamikaze quadcopter with a low radar signature is undergoing tests in the zone of the special military operation in Ukraine. Vitaly Dolgov, head of the Laboratory of External Piloting and UAV operation in the Kartsev Research Institute of Computer Systems, told TAS. The loitering kamikaze has been sent for tests to the zone of the special military operation and currently two of our drones are being employed there. The drone has proven its worth. The drone's hull has been created using special radar absorbing material that makes it almost invisible to enemy electronic warfare systems. The coating is added to composite materials in making the drone's frames. It absorbs up to 50% of radar electromagnetic emissions, the researcher said. The latest drone is capable of carrying a 4kg payload, he specified. The loitering kamikaze has two objectives. It can be used as a loitering munition and can deliver and drop explosives. The drone can easily carry a payload of 4kg to a distance of 10km. We keep upgrading the aerial vehicle and are currently working on the system of dropping as many as 6 munitions. Dolgov said, the Kartsev Research Institute earlier unveiled a grumb mobile folding quadcopter designed to ferret out targets and drop munitions.


This paper presents a new technique for analyzing proteomes from single cells with high sensitivity and accuracy. The technique combines miniaturized sample preparation, low-flow rate chromatography, and a novel-trapped ion mobility mass spectrometer to achieve greater than 10 times higher sensitivity compared to existing methods. This enables precise quantification of proteomes and their changes in single, FACS-isolated cells. It also reveals unexpected proteins and allows cell phase prediction. Compared to transcriptomic analysis, this technique shows a stable core-proteome despite perturbations, suggesting that the core-proteome is more stable than previously thought. This technology can be used to analyze proteomes from small cell counts, allowing researchers to gain unprecedented insight into cellular heterogeneity in health and disease. This article was authored by Andreas David Bruner, Marvin Thielet, Catherine Vassalopoulou, and others.


You're muted Michael. Ha look at that. Today's January 6th. Here we are. I'm still Being a lot of stuff there Hey, welcome everybody today is January 6th you all know that It's a lot of fun out there in the world But hopefully we've got good news here. I heard I heard a little bird and say that we had good news So all those clowns will be back in session in an hour Well on the on the more local front Who do we want to go first Chris there Chris B wants to go first sweet. Let's do it All right, so Cheers The beers were opened early today In conjunction with mr. Mr. Smith. I believe we have fixed the microphone issue Yeah, I I changed a C program which I haven't done and I'm not even sure how long but But I did import import audio basically what we did was We put a I found a patch online for port audio that takes the return code that was causing the failure and It skirts around it using something called an extra run that I still don't know what that is, but it's working My microphone has been running now for a half an hour so and Every time it gets that that error code. It just Restarts the audio and keeps going. So I think we're in good shape It's not the cleanest of fixes, but it is what we have And I will post my fix to the panticore dev channel after this meeting and hopefully will be will include this the other thing we found today is that There's a lot of defaults in not only our code but in the speech recognition code that are not suitable to our microphone So we actually went into some to some library code and changed it as well so The defaults are for 16-bit rates but we have a 32-bit rate not only a 32-bit rate, but they're a float 32 bit rate So it took us a lot of thinking that out. So that's in there and I also We also changed the sample Sample rate to match the microphone. So And the result is that the failure that was occurring frequently now occurs with much less frequency and when it does occur the We have a patch that it gets it gets around So yes, I think we're in great shape with the microphone so That was my day today The The underlying data piece of data the underlying data set that we use for training is that data set in the same at the same bit rate with the same Bit that's a good question. I Do not know the answer is no they're primarily 16 kilohertz Yeah, I thought there were 16 kilohertz like 16 bit mono or something. I mean they weren't they weren't particularly sharp That's because they were coming from an old pie But now you have a high-end Audio studio level hat delivering your your audio so Sample we can down sample from 30 from 32 bit to 16 bit and it'll be a lot Cleaner than if we up sampled from 16 or 8 anything. So I don't believe it's gonna be an issue in training Because I believe it's converted anyway in the training code, but I can verify that but There is code like this and the precise Chris Gusselin pointed out to we probably need to look at it as well, right? Correct. Correct. That's gonna need some Addressing in the runner. There's some hard-coded values there But but Josh the answer is we're better off with higher fidelity samples and worst case We can run them through a down sampling algorithm and bring that like my question was primarily it can our exist it Can we improve our existing model by improving the fidelity of the data set and then running it again? It's another training another training it through another training cycle Perhaps and the other concern obviously is when you train against 16k samples and you get 40k 48k input How well is that going to match up? So those are all TBD? but you know today is a Good day to celebrate Good awesome. Yeah, that's great. That's great news. So we're able to move Move into getting the rest of the demo working Yes, so tomorrow questions on it Can we um early and we and we do we understand you said something about like, you know I don't really know what that next next run or whatever the patch thing was can we We need to do some you know basic checks about where that code coming from and what it's doing and and all that sort of stuff And the other one just want to make sure are we changing hard-coded values in the In you know precise runner and stuff or are we dynamically loading those now from the configuration of it? So there's two answers to that first is As chris mentioned We had to go into some modules some python modules And hard code some stuff change some hard-coded stuff To match our hardware and we're not sure that that's absolutely necessary So the answer to your question is we just don't know we're gonna need another day to test with it run with it figure out the minimalistic changes necessary to get where we're at And by the way, this is a workaround. It's a band-aid because we know we're still getting overruns And it'd be good to make them go away Since we weren't getting them before But that being said I implemented is actually getting pulled into like debbie into and stuff too. So Yeah, that being said People with this problem far from it actually right. This is a valid workaround for now Until we can address those issues at a deeper level um, you know, it remains to be seen What it'll ultimately um turn out during our recognition when we run it But it was good progress. We're not done yet. We're not done yet, but it's good progress And we have a little bit more to go to get it over the finish line There's a change in the band-aid to core and to some configs. I mean, there's what I have on my device is all hacked right now I do know that he's not gonna be hacked and and yeah, that's that's tomorrow's work probably Yeah, yeah, we have a true monkey patch on our hands. Uh, so yeah, I mean We don't know yet chris. Uh, the the patch comes from a debbie in upstream So we feel pretty confident that if debbie and incorporated it It's not going to cause any troubles And the the x-run chris was talking about is Basically anytime you get an unrecoverable or what they consider a uh overrun or underrun error That's what the x-run stands for x is under or over And it's an over or underrun error. They used to just um assert out What this does is ignore the assert Reset the ulcer device and continue along its merry way So, you know less than ideal But better than where we were yesterday and something we can probably go to market with initially Awesome. Yeah, he said I'm very happy. I would crack a beer if it wasn't 8 a.m All right, well that that is very good news and but like everyone's noted it does seem like it's a patch. So I've taken a Uh a ticket in Jira and assigned it to ken. You can add details and reassign it as appropriate I just don't want to track of it. We don't have to you know, we can prioritize it as necessary But I just didn't want to lose track of the issue Um, great. So, uh, ken, do you have anything to add on your side or other things that are? No, no, no, I just held chris's beer while he solved the problem All right, sounds good. Well, I'm glad you stuck with it then Uh, can point at me in the right direction Uh, great. Well, let's go over to giz then uh Yeah, so I was doing some investigation on this branch as well. Um Uh Have set up a meeting with panicle for Thursday not friday because your friday makes it like, you know, just before midnight on friday night in europe, which is a pretty brutal thing um And we should we get this in then we should have um We should we should very much be able to do a new demo um to show the progress uh I did some investigation around The wi-fi set up um and tapping into xdg across containers um in pentcore uh, which it seemed possible, but I And chatting with them about yeah, the best ways to do that. Um Uh Particularly because it's on the system debuff. So we don't want to sort of, you know, just expose that to everything under the sun um But in the interim, I'm just gonna Get the rest of it set up so that it's it's in the image It's getting pulled into the image in terms of the demo and and it might just be on a timer to start with until we until we get some Triggering off the debuff messages properly. Um, but at least we'll be able to see it working and um Can kind of move forward on that Um other than that, uh There's uh, uh, I've been a really cool project coming from the community called magill to magill You know the um, what's the name from star trek? uh, anyway, uh It's a it's a front end framework. Um They've they've hooked up They've hooked into the the message of us and doing lots of stuff with amazon video and and youtube and and uh and codie and and a lot sort of stuff, um on a desktop so Uh, it's a cool little project. I just wanted to give it a bit of a shout out. Um I'll post a link in the team chat as well. Um Yeah, so for today we I'm gonna get that Wi-Fi stuff in I've been working on some voicom stability things We're seeing still seeing errors like randomly pop up. Um, part of that is because we haven't done a releases core in a long time So the chains of bug fixes that we have been doing are actually being run in our voicom thing, um But the market is really the priority at the moment. So Um, but as soon as we can get back to doing a release, that will be good. Um, 2102 is coming up pretty quickly anyway. So I think that what we'll end up doing is doing one point release In 2008, um with just all of the bug fixes and then do any of the Breaking changes for 2102 That is me. Okay. That sounds great. Um, Derek Hey all See so today we uh, we had a little meeting with, um Joe our uh similar down in Florida and Michael might talk a little bit more about that, but some of the things I was doing kind of um to help Johnny mostly get prepared for stepping in and helping with that is putting together finishing the spec documents for all the purchase parts and Getting everything ready to label all of that stuff and Kind of pass that knowledge on to me so that he can assist in the You know the handoff to Joe So, you know, like a lot of those spec sheets we didn't have for the different parts and stuff. So gathering together all the information that's necessary to understand what they are communicate that um I also had to make a change to our laser cut part This morning. There was some issues with the file. So fix that And uh, I got the audio chopped up for the um For the new onboarding walkthrough stuff. So At some point I'll have to handle it after I assume to guess to So we might need to have a meeting soon to Talk a little bit about that Or I can just send an email And uh Tomorrow I uh, so I got received the two boards from Kevin and um I would love to fire these up tomorrow with working mites so Um, let me know if you guys get that into something that I can get my hands on too And uh I'll throw them into some laser cut enclosures and we'll have two more How long it takes the panic for guys to integrate some of this stuff Sure, sure Yeah, that's what that's what I'm up to Okay, well theoretically, uh, if you push your changes up to the repo, don't they get them by, you know midnight One of the changes is something they're gonna have to apply the change to the board audio Something they're gonna have to do themselves Anything we do a core which we'll do tomorrow. Um, yes, you're correct. Okay. Got it um All right If we can if we can get all the details of that to like, you know down this evening Uh, then they'll have all of their tomorrow to work on that and Yeah, if it's just a patch to port audio, it should be pretty quick I can't see any if you like Getting in getting any changes in in a single day Yeah, I'll I'll write a post to the panic or dev channel. Um after this meeting Wait Uh, so Derek just to clarify. Did you only receive two of the sj 201 boards? Yes, I've got one for chris and one for myself and then kevin Sent uh one to ken directly which hopefully he got And then he sent one to panticore directly um Yeah, so that's where that's where I think he had more He could put more together, but that's that's the amount that he was able to get done Right, right. Okay. Yeah, I was expecting two more. So um I think uh, he's trying to deal one one came to me So you've got it No, I think no, I don't have it yet. I've got a tracking number though. Right. Yeah, I was All right, great Okay, I was expecting another one for rollover, but we'll uh I'll check in with him. He was having some trouble with the panticore shipping and customs and some nonsense. So um I'll check in with him after this Um Josh do you have anything you want to add? Nothing on the development side Right Okay. Yeah, likewise. I mean the meeting Derek alluded to Was just to check in with our fulfillment partner Crossing the t's dot in the eye is making sure we've got everything lined up So we can get the units out expeditiously once all the parts have arrived from the various suppliers Um, so that's looking good and um Yeah, that's about that's about all the news that is there so um Anything uh, people want to bring up outside of status updates or world news Yeah, okay Excellent. All right. Well, um I guess we'll call it there for today and we'll chat again tomorrow


Hello and welcome to the talk today. We'll be talking about Clanggo, so how many of you have you heard about Clanggo? Cool. And how many actually use it? Okay, impressive. So at the time of submitting this talk, because the title to get the bad and the ugly, I was very frustrated with Clanggo, so I've come to terms with it a bit better, but at the time we were trying to extend some things that really didn't work then, so yeah. But I will try to end on a positive note and try to hopefully do some constructive criticism rather than bashing it. So my name is Lily. I'm a developer at Kinfolk and why am I qualified to talk about Clanggo? It's basically because I worked on a few personal projects that heavily included Clanggo, as well as the Habitat Operator, which I do at work with Chef, and basically that heavily relies on it. So as I mentioned, I work at Kinfolk. We have a boot, so do come and see us and talk to us. We're basically a consultancy based in Berlin. So let's start a bit about the good. I hope the gifts are turning out okay. Sorry for it's very heavy, so I apologize for that. So yeah, let's start a bit about what Clanggo is. Some of you might not know. It's basically a library used to communicate with the Kubernetes cluster and includes a collection of different clients. It basically is an upstream Kubernetes repo. It has 563 stars, which is the most important metric, and there's responsibility for it is the API machinery, and they're really nice, so do go over to their Slack channel, Kubernetes, if you have any questions about that. So some of the use cases, it's mainly used in operators, as you might have heard of them. They're basically controllers in Kubernetes, and they're used to extend the Kubernetes API. So something like, as I mentioned before, the Habitat operator, the Prometheus operator, the Puzzgress one from Zalindu, and also Flannel uses it, which is a network solution for containers, but it doesn't actually extend the API, but it integrates with it. And also, Kubernetes indirectly uses Clanggo as well. So let's first set up a client. So basically we will try to communicate with the Kubernetes API. So here we see we only need a few lines of code to actually get all the functionality and all the power from it. So first, we get the config, and we do that by building it from flags. And if the flags are not present, it defaults to ncluster. So we can pass in the master URL, which I'm not even sure if anyone does use that anymore. And you can pass in the kube config path. And after you get the config, you just pass it into the new for config, which basically returns the client set from where you can actually communicate with the cluster. So as I mentioned before, there are two ways to do that. You can run it outside of the cluster. So basically that is if you're developing for it, or if you have some special use cases for it. And that basically you just pass in your path to the kube config, and everything works fine. And you can also customize the master URL. Has anyone done that? No. So I guess no one uses it. And inside of the cluster, basically what it does is it doesn't use any paths or anything, but it sets up everything for you. So it uses the service account. And the token is used to enable the communication in the Kubernetes cluster. And it's in that path in your container, in your pod. And it also configures the TLS certificates, according to your Kubernetes cluster's default. So once you actually have the client set, this is how easy it is to actually communicate. So this is used to list the deployments. And all you need to do is just access through the client set, the deployments resource. And you just list all the resources in the default namespace here. You can pass in some different parameters, like the field selectors or labels. So what actually happens behind the scene is that the list we saw earlier in the previous slide, that is basically just this, it's basically just an abstraction or helper to communicate, to talk to the Kubernetes cluster. So basically it's just to get requests, nothing more than that. There's no magic behind it. So yeah, this is all it is. It just makes your life much easier, so you don't have to actually reimplement everything yourself. It's quite powerful. So how actually client go goes about doing all of this. It's basically out of generated from Kubernetes itself. And it does that by using the Kubernetes, under the Kubernetes repo, the staging area. And it's published by a bot. And these are the repositories that are generated. And then you can see client go is one of them. And we'll see some of the other ones a bit later. So I mentioned earlier that the Kubernetes client go uses indirectly Kubernetes. The Kubernetes uses client go indirectly. And basically in reality it's all just a sim link and the vendor directory. As you can see here, all of these, the API server, the client go, they're all just sim links to the same staging area in their vendor directory. So it doesn't import in a way that we vendor if we use it from a developer point of view. So from a consumer point of view. So as I mentioned earlier, we'll have a look a bit. So the most one you use besides client go is API machinery. And it heavily relies on client go heavily relies on it and vice versa. So that is basically just it's shared dependencies for servers and clients to work with the Kubernetes API without actually using the direct type dependencies basically. And the consumers are Kubernetes itself, client go and also the API server. And now let's discuss a bit about the bad part or I like to call it frequent points of friction because I think like all of these things had a reason why they were done this way. And some of the maintainers are here and I don't want them to be angry at me. So yeah. So this is mainly when you first come across client go and when you first use it, these are the, I've noticed a couple of people had the same pain points. So in general, lots of people agree that it does a bit too much. So meaning that you end up importing the whole world when you just want to communicate with the Kubernetes API. So we'll see that in a second. And things that it does are a bit disconnected. So meaning that you have a lot of client go packages. And this is how it looks. So this is the minimal example we have that we have in our vendor directory. And this is how much packages we import just from client go, for example. So yeah, it's impressive, isn't it? And some of these packages, like I mentioned before, they do quite various things. So for example, you have things from you communicate, which is the purpose, right? But they're not that much related at first glance. So you have the work queue, which is just a queue implementation. That's in the package util work queue, then you have the tools cache, which is for writing controllers. So it's not really how you would expect from the client library. But once you get used to it, you understand. Another friction or another bad thing is the API versions. So this is a question one of my coworkers had, when he first started with it, is that you can get quite confused by what the different, what is alpha one version one, beta one, stable, and what are all these versions like this is not client goes fault as such, but you do have to actually use that. So basically, it comes down from Kubernetes, but you're still ending up with the different confusing names and different versions. So I'll try to explain a bit about the different versions. So there are the four types. So the first one is the development one. And it's not something many people actually come across because it's not actually committed or available in the releases. It's basically just for testing out new features and up and coming features and doing proof of concept. Then the next one, which I'm sure some of you have seen is the alpha level one, but it is in the release. But it's not actually being you have to enable it in your cluster to be able to actually consume it. And then there's the beta, which I'm sure most of you familiar like the deployments, etc. Sterling beta in the 1.8. And the difference between the next one, which is the stable one in the beta is that beta is actually recommended for short live testing clusters, so that you can actually test things thoroughly before they actually go into stable and improve things until they are. So like mentioned, there's the stable version, which is for example, version one, and that's enabled by default. And all users and it's considered stable. So this is the API changes in the 1.9 Kubernetes version. So as you see, there's not that many documentation. And I think that's where people find this very confusing. There's not that many documentation on which resource is in which version, in which Kubernetes or client go version. So that's one of the points where documentation would be very helpful. But it's really hard to do. So for example, one of the things that's surprising to lots of people is that the deployments are still in beta. And they have been so for, I think, since three minor versions. But in 1.9, they're going to actually graduate to this table. So that's good. But one of the problems with that is that you actually have to then update, but we'll come back to that. So the next one, the next chapter is the ugly or things that are not so nice. So basically the main problem that lots of people have who work on developer tools, and from a developer point of view, so let's say operators with different kind of controllers that you use, is that the Kubernetes releases happen every three months, right? And you have to then upgrade because there are things like auto updating clusters and everyone wants the latest release of and for the tool to work, right? But so for the 1.8 release, there was a bit of a delay with kind go. So that didn't quite work out very smoothly. So yeah. So actually updating your project, your project would only work as well for some versions. So as we've seen earlier, the current deployments are going to be in 1.9 stable. But if you want your cluster to work for 1.6 and 1.9, it's not really going to work that well. So that's one of the pain points. So RBAC is in beta, but you have to actually adapt things because only for, it's only supported for two versions, two consecutive versions, the API changes. So that's one of the pain points because when you have to actually upgrade your developer tools, you have to be very quick as three months is not that much before client go actually gets released before you can catch up and test everything. So that's one of the main pain points everyone has, I noticed. So and one of the other things is this matrix. So this is basically how the client go is compatible with the Kubernetes versions. And if you see the green lines, it's basically mainly compatible with the version. Everything else is either a breaking change or not that well compatible. And you have to, basically you have to support the latest version of Kubernetes or just support the earlier version, unless you want to do some magic there. Another point of friction I noticed is that you, so if we've seen earlier, this is how you list all the deployments. And if you notice, there's the in the red, this is not part of client go itself, but it's part of the API machinery. So if you just want to list deployment, which is the simplest thing, right, you have to actually import API machinery to be able to list. And then that tends to end up looking something like this. So this is actually from our habit on operator. And yeah, it's a bit of a mess to be able to import everything just to be doing the basic things. So let's do a bit of a demo. Hopefully this works. Can you see? Okay. So today we'll demo just a simple example of how you can actually extend and use the use client go to actually extend your Kubernetes experience. So where are we? So what we'll demo is just a simple deployment rollout. So yeah, I'm trying to better. Okay. So as we've seen earlier, you can hear we can repeat the steps. So basically, we're trying to get the client set. And what we're doing is getting the configs will be running outside of the cluster. So we'll be passing the kube config file. And after that, we'll be creating the client and passing it over to our package. So let's have a look at that. So what it does is it basically takes a deployment and it creates it first with instance one. And after it's been created, we scale up to 10. As simple as that. And what we do is we first create the deployment. Can you see that? And we pass into deployment, which looks like this. So the deployment representation. And after that, every five seconds, we basically roll out a new deployment and we do that by using the update. So hopefully this works. So and you can use this to extend things like you can do canary deployments and extend this even more. And it's quite cool and really simple. It's only a few lines of code that you use to be able to just make the experience much nicer. Let's see. Okay. So it works. Yeah. Okay. So basically we here created a new deployment and now every five seconds we're scaling up by one. Hopefully. We should be scaling. Yeah. Okay. So as you can see, you can do this whatever you want with a very simple amount of time. So it took me like, I don't know, five, ten minutes to do this. So it's not that. Just don't look at the code quality. So yeah. And after ten seconds, after ten instances, it will actually shut down and we will have ten deployment scale. So it should shut down and we'll have a look at the deployments using kubectl. So we see that we have ten and it was created 51 seconds ago. So that's the demo actually worked. So let's have a look at a bit more. So there are many different alternatives or different implementations of languages. So for example, there is another go implementation, the Kubernetes one by Eric. And it only brings two dependencies with it. So it's a nice alternative for something smaller and quicker to do. So for example, if you want to do a small project, but it's not full-featured yet from what I'm aware. But do check it out. There is also lots of different language implementations because this is the go implementation. So you have two Rust clients and Python, Java, C-Sharp. And there's many more in the Kubernetes client. If you're interested, you can have that look, have a look there. So a bit about the future. I was speaking to a few maintainers here of client go and other tools. So basically the future is quite bright. So I do want to leave on a positive note. As I, there was lots of discussions here as well at KubeCon about this. So they're in the upcoming. So for Kubernetes version 1.9, there will be client go 6.0. And that will be much easier to update. There will be no, at least no major breaking changes planned is what I was told. So hopefully there will be release tags. They're already introduced. So you can actually vendor things much nicer. There are release notes for developers so they know what actually breaks. So you can change it, you can plan things. And also there are nightly releases fixed for client go soon so that you can actually test things. And there is a new channel on the Kubernetes Slack channel. So it's called client go docs. And it's a place to improve on the documentation. So do you check it out if you want to contribute something, something you know. Please have a look. Everyone's really nice. It should be a community effort and we should all contribute some documentation to make lives easier for people and hopefully not need talks like this in the future. And this KubeCon, there was a bunch of discussions as well from different points of view. And on the future of actually of client go and other projects and their libraries. So yeah, so the future is bright. Just want to point that out. So yeah, that was my presentation. So if you have any questions, yeah go for it. Yeah, I know, I know, I know. Yeah, so that's a bit like you can do it but you need to really catch the correct versions right. So for example we were, we are currently still using the client go for and it works fine for us because we haven't switched to five but we will have to switch to six. So that will be hell. But yes, once things settle down and Kubernetes is not so changing I guess. Things will be a bit better but now with new releases and everything, it takes quite a while. So yeah, my answer is you just have to do the work. Yeah, sadly. Anyone else? Yeah, yeah, we used depth and so far it worked fine for us. So I'm a bit confused by everyone complains about it but we haven't switched yet. We're planning on switching to 1.9 so 5.0 because we haven't had many, we don't use our back so we don't need to switch that. So we didn't have to switch too much with this version. But yeah, come and ask me after we switch to 1.9. But yeah, so far depth works for us but there is glide apparently is also good. There is some documentation for that whereas there are some problems with GoDepps. Yeah, go for it. Exactly. Yeah, I'll hand it over to you. Yeah, but he has done some. Yeah. That made sense, yes. Yeah, anyone else? Yeah, go for it. Yeah, no, we're doing end-to-end tests mainly. So we focus on those heavily and yeah, we tried not to do that. We tried to isolate the functions but you can only go so far. Yeah, it depends on the use case. Yeah, go for it. Sorry. We're using depth. Yeah, it works fine for us and also in like the smaller projects is we're perfectly fine as long as you will see. I'll come back to you when we do when we switch to 6.0 but so far it worked fine from the 4.0 I think to the 5.0 switch. It worked fine. Cool, thank you. Do come to our booth.