So, now let us look at the cell design for the high short circuit current, fine. So, we have found the upper limit of parameters. Now, let us see what we need to do to actually what we need to do to get that particular parameter. So, we want high value of short circuit current and current is what? Number of electrons and number of electrons is what? Number of electrons is basically if you want high current, if you want high ISC value means if this is my solar cell, what you should do? Reflection should be low, transmission should be low, low transmission. So, every photon which is going in should give me one electron hole there and this electron hole should be. So, recombination should be low, low recombination. So, the design is the design of a solar cell to get higher value of short circuit current is nothing but minimize reflection, minimize transmission, get a minimize recombination. So, that is what? Short circuit current first of all it will depend on the area, larger the area of the solar cell, larger the short circuit current, it will depend on the number of photons basically spectrum which is not in our control, it will depend on the intensity of the light, it will depend on the what is the collection probability, what is optical property. Collection probability is how we are minimizing the recombination, we will discuss that. So, cell design motto as per the number of area is concerned, you basically have the larger area, larger area will have more light, more light means more photon, more photon means more electron, more electron is more current, very simple. So, large area should be giving me large current. What about the air mass? Air mass basically spectrum of the sun and we have discussed that air mass 1.5 g, g is strength of the global is the spectrum that we should be considering, but actually it means that different spectrum will have different composition and therefore, will have different types of photon and remember photon energy will affect because some of the photon, high energy photon will get close to the, absorbs close to the surface, some of the low energy photon will transmit. So, if your spectrum is changing, your behavior or the performance of solar cell will also change and mainly the current will also change. So, we will not discuss this in detail. Absorption coefficient we have discussed already in detail that high absorption coefficient you require, high absorption coefficient is good because you require thinner material because it gets absorbed very close to the surface and a penetration with absorption length is very large if absorption coefficient is low. As you have seen many times that also clear from this graph, this is the absorption coefficient for silicon that the low wavelength photon or high energy photons have the high absorption coefficient and therefore, we have seen that blue light gets absorbed very close to the surface, green light absorbed close to the surface and little deeper and red light absorbed close to the surface and almost everywhere in the solar cell. So, this is important to know right, this is very important to know. If I am talking about red light because your absorption coefficient is less, your absorption length is higher, so it requires thicker material. So, therefore, absorption will take place almost everywhere. So, this is very important to understand that blue light is absorbing very close to the surface from where light is entering. What does it mean that all the electron hole pair generated because of the blue light are getting generated close to the surface not deep. So, what does it mean? So, if I have a blue if I my junction is like this my junction is like this this my N and P if my light is coming here and if it is a blue light blue light means what high energy photon may be 3 electron rule photon. So, all the electron hole pair is generated very close to the surface very close to the surface this is a blue light that is what will happen. If I have my same P n junction if I have same P n junction if I have you know red light let us say energy of the red light it is just little above the band gap let us say 1.3 electron. Because it is a lower the red light will have the lower absorption coefficient and because higher absorption length and therefore, generation will occur here, here, here, here, here, here, here, here, here, till the absorption length this is the absorption length. And if I have even lower light then my absorption actually can go all the way through then. So, this is again important to understand that the blue light carriers are generated very close to the surface, but the higher wavelength light or lower energy light will result in little electron hole pair generated deeper and deeper. So, that is what is shown here the red light will do result in generation mainly. And if I look at the complete, if I look at the complete how many electron hole pair gets generated. So, it is given by this. So, if you look at this the generation rate in number per centimeter cube per second is typically for the air mass 1.5 spectrum is in the range of transform 21 photon transform 21 to transform 22 electron hole pairs at the surface huge number right transform 21 to transform 22 no per unit volume per unit time. But as you go deeper and deeper for that particular thickness it decreases. So, what does it tell you that lot of generation occurs, lot of generation occurs very close to the surface keep in mind lot of generation occurs very close to the surface. Because blue photon is giving generation here red photon is giving generation also close to the surface. So, lot of carriers are generated close to the surface with surface from where light is entering into the solar cell. So, if I am light is entering from this side this is my friend surface if light entering from that side this is my friend. So, therefore, now that question is if lot of generation takes place close to the surface where should be my junction. Now, what is the junction? Junction is a place where there is electric field right junction is a place where there is electric field. When there is electric field the chances of recombination is less by because under the electric field the electron hole pair you know for experience of force which can separate them immediately under the electric field there is a there is a force which can be separate. So, if my again p n junction I have drawn some many times now. So, in this electric field if electron hole pair is generated here this is a flat band flat band means what? Flat band means no electric field as I said earlier this is quasi electric field in this region quasi electric field, but here electric field is not equal to 0.  So, recombination is nearly 0 recombination is nearly 0 where in junction, but as you go away from the junction this carrier if it is not within the diffusion length if it is not within the diffusion length of electron l n then they may recombine. So, the chances of separation of carrier is highest in the junction, but as you go away from the junction the chances of separation decreases that is what is shown here. The collection probability of the carrier remember what are the thing that should happen charge absorption separation and collection. The separation probability this is more like a separation probability actually is highest in junction and as you go away from the junction your separation probability decreases fine. Now, I will come back to the there are three different curves and I will come back to the, but just keep that one point that collection or separation chances is highest in the junction as you go away from the junction suppress chances decreases which means recombination chances increases. So, this is my generation profile now most of the generation takes place close to the surface and this is my collection probability profile. So, where should be my junction now? As we have seen in the all throughout this course so far that normally I draw a p n junction like this p n n junction in the middle if I put light like this this if I somehow achieve this my solar cell will have very poor efficiencies why poor efficiencies in this case this will give me poor efficiency why because my generation is taking place here lot of generation is taking place here my junction is here. So, carrier will have to travel all the way near the junction to get separated and therefore, many of them will recombine in this process, but instead of that instead of that if I have my junction here. So, my very normally I have n here normally p here you can consider the same thing here also you can say this is p and this is your n it does not matter and if I light is coming like this now because my generation is happening close to this surface and therefore, this kind of arrangement will give me higher efficiency. So, here we will get high efficiency right and therefore, most of the time in commercial solar cell your n layer which is normally emitter and this is your base and this is your emitter normally your emitter is very very thin the junction is very close to the surface from where light is entering emitter and typically you know in the current case it is about 300 to 500 nanometer only 300 to 500 nanometer. So, what is the thing we are learning that junction the p n junction should be close to the surface from where light is entering p n junction should be the close to the surface from where light is entering because of this reason because of this reason that collection probability is higher at the junctions you should bring your junction where the generation is higher and generation is higher close to the surface. One last concept in this regard is basically how to find out how so each photon should give me one electron whole pair. How do we know each photon is giving one electron whole pair or not then the way to find out is by using what is called the quantum efficiency. What is the efficiency of each quantum? What is one quantum one photon? What is the efficiency of each photon? Photon has a wavelength. So, this quantum efficiency is plotted as a function of wavelength what is the efficiency of each quanta of energy that is what is the efficiency of each photon or basically can is each photon is giving me one electron in the external circuit or not. So, basically what you do you measure the short circuit current you measure your short circuit current per unit spectrum per unit flux of the photon that is your quantum efficiency of each photon. Now, one of the thing that we have shown here is one of the thing that we have shown here let me anyway discuss here is that in a p n junction. So, normally my as we discussed that my emitter is very thin typically light is falling from this side this is my n region this is my p region this is typically what you get and this is this is emitter which is very thin emitter and this is my base p is normally base n is emitter it can be opposite also. Now, my surfaces are very defective place. So, there is a lot of recombination that can take place at the surface there is a lot of recombination that can take place at the surface. So, surface recombination could be high could be high and that is why if you go back to this slide which I have shown you I will show you later this slide that there is a if your surface recombination is less your collection probability from the surface will also be some value, but if your surface is very poor then nothing will be collected from the surface anything that is generated close to the surface will become will recombine. So, therefore, surfaces are the one place in solar cell that must be well passivated or passivation means you have to minimize the recombination at the surface otherwise you will be in a problem your efficiency will be lower. Efficiency by the way the quantum efficiency one thing which is very nicely tells me what is happening about about each solar cell. So, look at this graph. So, this graph tells me that this is the quantum efficiency by the way quantum efficiency is maximum of course, 100 percent means one photon is giving you one electron at the surface quantum efficiencies are low why low because of the surface recombination I told you surface are very defective places in the solar cell and it is and it is a quantum efficiency is a function of wavelength right. So, short wavelength means high energy photons high energy photons absorbs very close to the surface right as your energy of the photon decreases they absorb deeper and deeper and deeper. So, therefore, by quantum efficiency I can find out which of the photons are efficiently working in a solar cell and which are the photons are not efficiently working right. So, if I if I look at the the the performance or the quantum efficiency for a 1000 nanometer 1000 nanometer is a low energy photon it will absorb almost everywhere. So, this if my efficiency are low which means what my 1000 this photon is getting absorbed almost everywhere long wavelength photon. So, this mainly will tell me that what is happening in my back side of the material rear side of the solar cell my high energy photons will tell me what is happening at the front side and my medium energy photons will tell me what is happening near the junction ok. So, by quantum efficiency I can actually probe the solar cell depth how the front surface is performing how the junction is performing how the bulk of the material is performing and how the rear side is performing ok. I I will tell you I will try to explain this with the with the on the whiteboard in the last slide ok. I told you that I told you that high energy photon or let us say blue photon where it will get absorbed here blue photon will give me electron here ok. So, if I am plotting the quantum efficiency quantum efficiency and if I am plotting the plot for 400 nanometer if this and this is my junction let us say this is my junction this is my if for 400 nanometer which have photons are electron hole pair are generating close to the surface if all this electrons are actually recombining then my efficiency that is the number of electron per photon number of electron per photon right that is my quantum efficiency will be low right. So, then my quantum efficiency low, but assume that all this photons which are generating all the electrons which are generating here is not recombining every all all electrons are actually separated then my quantum efficiency will be high my highest value of quantum efficiency will be 100 percent ok that is the blue photon and now let us say I have I am putting green photon.  If my junction is very good and no recombination is taking place at the junction then the quantum efficiency of green photon will be high ok. So, therefore, green photon will tell me what is happening at about 550 nanometer then I am putting the red photon red photon will have even lower energy and they will go deeper and will give me the generation here also, but they will give me generation here also ok. So, if my bulk of the material is very bad and lot of recombination is taking place the corresponding to 700 nanometer my efficiency quantum efficiency will be low, but if my material is very good quantum the crystal quality is very good less recombination is taking place in the bulk my efficiency will be high and therefore, I will get high efficiency here also. Now, I get a infrared photon infrared IR photon ok IR photon will have even lower energy and it will get generated here here here and it will also get generated close to the back surface also ok. Now, if the if my infrared if the back surface is also lot of recombination taking place at the back surface the efficiency of the let us say 1000 nanometer photon will be low quantum efficiency will be low, but if the back surface recombination is also low and therefore, all this carrier also contributing to the current then efficiency of 1000 nanometer photon will also be high quantum efficiency. And therefore, by the quantum efficiency I can find out what is happening at the front surface what is happening at the junction what is happening in the middle of the material and what is happening in the rear side. So, typically I would expect quantum efficiency graphs to be like this and beyond if my band gap is a if the if a photon of energy less than the band gap is coming it is not absorbing that the if quantum efficiency will become 0 ok. In this way my quantum efficiency is a very good tool quantum efficiency is a very good tool to probe the solar cell ok fine. So, let me stop here I am already crossed the limit already crossed the limit for this. So, let me stop. So, let me summarize before I stop that that first of all what are the upper limit of parameters upper limit of short circuit current depends on the band gap and spectrum upper limit of open circuit voltage depends on the band gap and recombination upper limit of field factor depends on the series resistance and the open circuit voltage and all this determines a bit band gap and combination of will this determine the what is the optimum band gap for the obtaining highest efficiency. Low band gap material will give me high short circuit current, but lower open circuit voltage high band gap material will give me higher open circuit voltage, but low short circuit current and therefore, I have to find out the optimum value and optimum value of the band gap is 1.45 electron volt. Then we started looking for how to design a solar cell for highest short circuit current. So, minimize reflection and most important thing is where to place your junction your junction should be very close to the surface from where light is entering because most of the generation takes place close to the surface and therefore, junction should be close to the surface and that is why today's commercial world your junction is located only about 300 to 500 nanometer from the top surface.  Then I most importantly we discussed the quantum efficiency. Quantum efficiency is efficiency of each quanta each photon. So, what how many electron is given by one photon typically one photon can give one electron. So, therefore, quantum efficiency can be 100 percent, but because of the recombination taking place at the surface at the junction and reflection taking place quantum efficiency is not always 100 percent especially close to the front surface because your surface can also recombine and the back surface quantum efficiency can be lower ok. So, let me stop here and I will take couple of questions we are getting late for the next lecture as always, but I know you are enjoying your lecture. So, you do not mind doing that ok. So, thank you let us start and question answers ok NIT Surat. Sir, I want to ask that solar cell we have seen in which p type material is below and n type material is on a top and light is falling on a just n type material. So, can we made a solar cell said that light is falling on a both p type and n type material means if we consider the solar cell as a cubic and solar cell we have discussed in this the light is falling on a just on a top. So, can you make a solar cell in a said that light is falling on a side. So, that light is falling on a both p type and n type. Yes, yes it is very much possible that you can make a solar cell that lights falls on a both p type n type typically standard solar cell is a cell where you mentioned correctly that light n layer light falls on the side of n layer and the p layer is at the bottom. You can actually make the other type of also solar cell you can make p layer on the top n layer on the bottom or you can make a solar cell where light falls from every direction. In fact, there are solar cell which is called bifacial solar cell which can actually accept the light from all the direction and can perform well. So, yes it is possible to make a solar cell, but making a cubic solar cell will be not a good idea right. Because on a front side your solar cell if you make your junction at one side then you are it is closer to where the maximum generation is taking place, but if a light is coming from the other side it is farthest from the place where maximum generation is taking place. Therefore, making a cubic solar cell is not a good idea. Tejpur University. Sir, when the band gap is reduced that means less band gap then open circuit voltage will less and the short circuit current will increase. So, why it is? Well, when the band gap is reduced open circuit voltage will be lower and short circuit current will be higher right. Now, because of the lower band gap more and more photon have enough energy to excite a electron. Remember, what is the requirement for electron excitation that the energy of the photon should be equal to or greater than the band gap. So, in the band gap is lower more and more photon have enough energy to excite a electron and therefore, if more electrons are excited more separation will occur and more current will flow. And then the open circuit voltage for the lower band gap material will be lower because your exciting electron to only smaller potential energy increase right. And potential energy means higher is the potential that you can get because your excitation is lower your voltage is lower. If you excite electron to higher potential energy you will get higher voltage. I want to ask one question what is the efficient what is the percentage how that we can obtain from silicon cell for band gap of 1.12 electron volt. What is the highest efficiency that can obtain say that 44 percent we can get from 1.45 electron volt. Yeah. So, basically this 29 percent efficiency number that is given is for the crystalline silicon of 1.12 electron volt. 29 percent is the ideally highest possible efficiency that you can get from crystalline silicon. You remember that graph that I have shown you it is actually close to that number only. So, if you look at that efficiency graph and maybe if I can go back to that same graph again. So, this is the band gap versus the efficiency you can see here crystalline silicon the possible efficiency is crystalline silicon is here 1 the 29 percent is about is for the 1.45 electron volt this is the ideal possible efficiencies crystalline silicon will have little lower efficiencies ideally possible ok. Manipal. This design and application of solar cell depends on many parameters for effective utilization and applications any standards are contemplated or available. No, there is no standard for design of solar cell because the design depends on so many different parameters. For example, if you are starting silicon substrate is of a different quality different lifetime ok or more defected then your design has to be different. If your material is amorphous silicon your design has to be different if your material is some other then your design has to be different. So, there is no standard available for design of solar cell you have to do it on your own. So, depending on the market constraint and availability users has to think and use. Well, I mean they are for a standard for example, when for a crystalline silicon solar cell when people are making solar cells in millions and millions in number and when your input wafer is fixed then of course, your design is standard, but if your your material itself is changing your design will also change. And especially when you are trying to get higher in higher efficiency people are looking for many alternative design to get more and more charge carrier absorption and separation. Baramati sir, why N type is placed in front of in front? Good question why? Why N type is on the top and B side? Why N type is on the top and B side is on the bottom? The reason is coming from the technological perspective for example, you know the front surface where lot of generation takes place there can also be lot of recombination ok. People have shown that it is possible to reduce the recombination of the N surface then the P surface ok. Therefore, it is easier for people to make top layer as a N layer and the bottom is the P layer. Other thing is in the P layer the minority carriers are electron and electron have higher mobility as compared to whole. And because your junction is closer to the top surface and your P layer thickness is 180 micron the minority electrons in the P layer will have to travel longer distances and the higher mobility helps to travel longer distances. And therefore, it is also good to have P layer as a base layer. Shivaji university? The red light generates EHP in the interior area and the blue light or low wavelength photon generates EHP close to the surface. Why it is so? Ok the blue light generates electron hole layer close to the surface and red light generates electron hole pair not in the interior it generates everywhere also close to the surface. Please make sure that you do not misunderstand this what I said that the blue light will generate a blue light will generate EHPs close to the surface ok. A green light green light will generate EHPs in this volume also close to the surface. What is this? This is absorption length and a red light will generate EHPs here, here, here, here and here and deeper also ok. Also close to the surface, but they also generate deeper. Why it happens? Because of the lower absorption coefficient red light will have lower absorption coefficient and therefore, they will actually generate here also here also here also here and infrared and infrared light infrared light will generate everywhere here also and some of them also transmit ok. So, it is like this is that clear please all the participant do not get confused that only red light generates in the middle it generates everywhere including the surface ok. Some question in the chat and we will run late on that again. What is the difference between solar cell and photo, photo detective device later? Next course is the edging effect of solar cell affect the efficiency also what is the average life of a P and N region. Edging effect can definitely affect the solar cell efficiency and as the as the time progresses when the modules are installed in the field solar cell efficiency keeps on decreasing ok. How much it decrease? People also guarantee that that first 15 years the efficiency will decrease only 10 percent of the initial efficiency first 15 years and in the next 10 years efficiency will decrease by another 10 percent. Now, this 10 percent are relative to the initial value ok. So, 10 percent 10 percent 20 percent. So, in the 25 years lifetime people guarantee that efficiency only decrease by 20 percent of the initial value. What does it mean? That even after 20 years your solar module will still perform 80 percent of its initial voltage or efficiency. So, as degradation occurs P and N region normally does not degrade which is a metal contact and the encapsulation and the inter reflective coating in all results in a degradation. We will discuss that in detail. Is there any possibility to minimize the thermal thermalization and transmission losses? Answer is yes. It is possible to minimize the thermalization and transmission losses. How to do that? You can do it by making a multi junction solar cell ok. By the way if I take a material of 1.1 electron ok. I let me anyway discuss it. We are running very very short of time, but I will spend less time later. So, if I have the. So, the question that I am trying to solve is how to minimize thermalization losses and transmission losses ok. So, if I have a if I have a photon of 2 electron old band gate and I have a material also 2 electron old band gate. What is the efficiency? 100 percent. If I have a photon of 1.5 electron old band gate sorry 1.5 electron old energy and my band gate is also 1.5 electron old. What is the transmission distribution and thermalization losses? 0. If I have photon of 1 electron old band gate sorry if I have photon of 1 electron energy. And my band gate is also 1 electron old. What is the thermalization and transmission losses? 0 right. So, whenever my energy of the photon is equal to the band gap of the photon of the material, then I do not lose. I do not lose in terms of the thermalization losses and I do not lose in terms of transmission losses. If my photon is 1.5 electron volt and if I have a band gap of 1.5 electron volt I do not lose anything. If I have photon of 1 electron volt and if I have band gap also 1 electron volt I do not lose anything. So, what I am trying to say if you match photon energy with your band gap for all the photons which means there are infinite photons and therefore, you should have the infinite band gaps. Infinite band gaps are not possible, but what you can do is if you can do the multiple junctions as I said. So, if you make a now you put 3 solar cells on together right. So, now you make sure that your light is coming from this direction. So, this is your cell number 1, this is your cell number 2 and this is your cell number 3. If your light is coming 2 electron volt and above light will get absorbed here and then the rest of the light will get passed 1.5 electron volt and above light will absorb here and then remaining will be passed. So, now in this way by matching your photon energy close to the band gap energy bringing down you are bringing down the thermalization losses and you are reducing the transmission losses. So, by going from a single junction to multiple junction you can minimize the losses in your solar cell thermalization losses and both transmission losses. Last question multi multi junction solar cell design. How many junctions can we create within a low production cost? Very good question. If you can create two junctions with a using the cost of one single solar cell, I will guarantee you that you will get a noble price. I will guarantee the noble price to you. So, anybody everybody is trying to do that they are trying to make more junctions at the lower cost are trying to make a higher cell efficiency without increasing the cost. Anybody who can do that will get a noble price or in fact anybody who can make a solar cell with a low very low thermalization losses and very low transmission losses and not adding too much of the cost can actually get something like 10 noble prices because the whole world want solar cell at very very low cost in high efficiency. So, there is lot of potential to get many many noble prices get ready for that and let us stop here.


Welcome back folks. If you enjoy that opening animation, make sure to head on over to the Tiberius Maximus YouTube channel and subscribe He does some really high quality political cartoons that are worth checking out If you'd like me to give your channel or website a shout-out simply make a purchase on ribtea.com 4 slash drone tech and make sure to use the promo code drone tech to save 20% off most items send me the proof of purchase And I'll give you a shout-out. Thanks as much as I would love to move on from this unmonetizable topic I couldn't pass this up CNN hosted a panel of Republican women to try and pressure them to call Trump's tweets the big R word But things didn't go quite as they had planned. How many of you don't think what the president said was racist raise your hand These eight Republican women from Dallas don't see anything wrong with President Trump telling four Democratic Congresswomen To go back where they came from. Let me just share with you the definition of racism from Marion Webster dictionary A belief that race is the primary determinant of human traits and capacities in that racial differences produce an inherent superiority of a particular race Based on that definition. Do you not think what the president has been saying? I love how she reads off the definition of racism and exposes that it has nothing to do with what Trump said Yet carries on like it perfectly describes exactly what he did Racism is the belief that your skin color makes you superior or other groups inferior Trump told a bunch of extreme left-wing Congresswomen that if they didn't like this country They were free to go to another one He never said go back where you came from like the CNN host claims But rather just if you don't like it here, you can go somewhere else while you could argue that it was xenophobic or bigoted It simply doesn't fit the definition of racism and quite frankly. I'm tired of all the labels It seems like the left comes up short when it comes to convincing arguments But boy do they have a long list of labels that they'll attach to you and an attempt to invalidate your convincing arguments That is in fact a big part of what's going on here The left and their media have been using these labels to such a degree that they've completely lost their meaning anybody Who's in opposition to the left or the Democrats knows that they'll be held to different standards for the purposes of political Expediency by the DNC media for a long time We played along because we're the good guys and we just assumed that we all had the same goals and aspirations for this country But it turns out that there's two very different Americas forming and playing along with their games is only hurting our side A great example of these double standards being used as a political weapon by the Democrats and their media are the detention centers and deportations right now in the media Reports of deportations are covered as if brown shirts are rounding people up and putting them into Nazi camps However, all of these same things were going on under Obama and actually in much greater numbers But without any of this hysteria these congressmen these congressmen who said they ran for Congress ran for office because they Explicitly love this country. You're saying that's a lot What a surprise the DNC operative pretending to be a reporter is defending the Democrats While there's plenty of material to go after the so-called squad with CNN prefers to just bury that and focus all Attention on attacking their political opposition and Donald Trump and the GOP Notice how these women simply aren't buying it and this CNN host just keeps trying to make the sale Instead of just dealing with the facts at hand one of the most glaring facts being that Trump's tweet simply doesn't meet the definition of racism I haven't seen CNN or any other media outlet call Kamala Harris a racist for telling Trump to go back where he came from because of course as We know it's always different when Democrats do it like when AOC called Nancy Pelosi a racist CNN and the other media outlets certainly weren't out there agreeing with AOC and attaching the label of racist to Nancy Pelosi And if you remember Trump was actually out there defending Nancy Pelosi against the charge I'm not accusing I'm asking you what Do you think it's just a coincidence that these four congressmen that the president is going after none of them are white Perhaps it has something to do with inciting terrorist attacks on ICE facilities and then refusing to denounce it and Tifa firebombed a Facility in Tacoma over the weekend. It's an ICE facility. Will you condemn them for that? Should more people do it It's easy to say no will you condemn and Tifa for the attack in Washington? It's easy to condemn a terrorist attack. Do you condemn and Tifa for their violent actions against American law enforcement? Just look at how completely rude they are to this reporter who's asking them some tough questions because They're simply not used to that and what they are used to is the media coddling them and attacking anybody who's critical of them Just look at that face. It's the face of partisan hatred and anger that her tactics were just exposed These women rightly called out CNN's attempt to paint all Trump supporters as racist by pressuring them to accept CNN's deceptive narrative This is the result of using the r-word far too much and far too often as a political weapon I've often equated the way the left uses the r-word to what happened during the Salem witch trials They've accused so many people of being witches at this point that it's just become unbelievable I wish that there was a white one that they they um, why are they not racist? How come they haven't befriended one of their white female congresswoman colleagues and Her joy because they won't a good point. They don't like white people Now that was a damn good point a point that went completely unanswered by this democrat operative host Who suddenly lost the urge to defend her favorite anti-american squad? Imagine for a minute that the squad consisted of white republican women There's no doubt that CNN would be asking them Where are all the women of color? But of course this standard is only applied one way when it comes to skin color and again This is why this tactic isn't working anymore on the left and in the democrat party They don't expect a group like this to include white women because white people aren't popular in the democrat party The bedrock of the modern democrat party is that white people are the source of all that is gross and evil in this world And my job is to shut other white people down when they want to interrupt My job is to shut other white people down When they want to say oh, no, I'm not prejudiced I'm seriously amazed that CNN even allowed this to air although I suppose they'll just use it to continue saying that republicans are racist Let them they've been doing it for years anyway I'm betting that a growing majority of americans simply aren't playing this game anymore And this entire episode is gonna backfire really badly on the democrats and their media Who knows maybe trump really is playing interdimensional 4d chess. That's all I got for you today Make sure to drop a flying elbow right onto that like button and the notification bell while my channel has been re-monetized They're still demonetizing every video I upload if you enjoy my content and you agree with my mission Please consider subscribing to me on patreon or subscribe star You can also send me a donation on paypal and I appreciate it keep coming back folks I have something really big planned for august the first that I think you're gonna like You


Hi, everyone. Joe for Jaspy's casebrakes.com. Happy Thursday. Coming at you with 2122 Panini Mosaic Road to FIFA World Cup Soccer, a three box random team break with an early bird giveaway. This is break number one. You can see the next one's already in the store. If you are one of the first 12 spots purchased, you can see that circled right there, you get a chance to win an extra spot. The early bird gets the worm. So here's the first 12 right here. And name on top after eight. Three out of five, eight times, we'll get the extra spot. One, two, three, four, five, six, seven, and eight. Simon, congrats to you. After eight times, you were the early bird that gets the delicious, delicious worm. All right, now, 17 spot break. Let's grab everybody's names again. There's all the countries right there. Some of them combo it up. Let's roll it. Let's randomize names and countries. Five out of five, 10 the hard way. One, two, three, four, five, six, seven, eight, nine, and 10, five out of five, 10 the hard way. Chase down a chase. Five out of five, 10 times for the countries. One, two, three, four, five, six, seven, eight, nine, and good luck, 10th and final time. After 10, we've got the United States on top down to Belgium on the bottom. So there you go, Chad with the United States. Simon with Brazil. Josh with Uruguay, Peru, and Ecuador. Robert with the three lines. England, James with Italy and Austria. Kevin with Mexico and Chile. Mark with Germany. Todd with Norway. Simon with your early bird spot, the Netherlands-Australia combo. Chase with Denmark, Croatia, Switzerland. Brian with Spain. Chase with Argentina. Bernard with Poland, Colombia, and Qatar. Chase with Portugal. Brian with the blue, France. Thomas with Wales, Sweden, Venezuela. And Chase with Belgium. All right, so let's alphabetize by country right here, and we're gonna pause the video. When we come back, we're gonna see if there's any trades, and then we'll have that three box break. Stick around, we'll be right back. All right, welcome back, everybody. So no deals were done, so that list right here remains the same. Here on Thursday, the 6th, October, the 6th, October already? This is three box, random team number one, the next three box, random team break in the store right now. I believe all card ship in this, yeah, all card ship, and it's from a fresh case. Boxes, we're gonna do. All right, so let's, here's how we'll do it here. We'll do those three will be one, those three will be two. That's three, and that's four on the dice roll. If I roll a five or a six, I'll just roll again. So upper left, one, upper right, two, three, four. That's easy. One, so these three boxes up here. So let me put the die right on top of there, so these will be, so we're working from the same case. All right, RT for random team on here. We may just grab three random boxes from the, just from the stack. Or maybe we'll do a dice roll, I don't know, just depends on, depends on how we feel. Great, and once again, the next three boxes are in the store now, looking for ultra rare stained glass and overdrive inserts. One autograph per box, that's what we're looking for here. We're on the road to the World Cup. All right, box one, good luck. As I've been saying in the previous videos, for the soccer, always worth a, you know, all card ship, but when you get those rookie cards, it's always worth taking a look at those rookies and seeing if they're, do a little research, see if they can end up on a starting lineup in the starting 11 for their respective teams. That's right, on the road to the World Cup. Keep your eye on the road to the World Cup. This guy's on Liverpool, he's been fun to watch Luis Diaz. Lewandowski, Jofilich, and all card ship, of course. Yeah, so like, look at this guy. You know, see where he's at on the squad. You know, they could do something pretty special in the World Cup, that might be great. Here's Lionel Messi, probably his last World Cup, right? Did he officially announce that? I think it might be his last World Cup. Could go out with a bang. Could he go out with the Jules Ramay that goes to Chase in Argentina? It's possible. I think it's not, it's not a long shot. I think they do have some pretty decent odds to do it. People have a lot of this World Cup-related product being released this year. So it'll be a good time to kind of get into a little bit of soccer, diversify your hobby portfolio. And we've got some Scripps Autographs, Sergei Nabri. Scripps Auto for Mark N. Germany. Nice. Jordan Shaqiri. There's an Erlen Ha, unfortunately, Norway not in the World Cup. They were on the road to the World Cup. Kind of stumbled a little bit, but I want to say they're expanding the number of teams in the World Cup when it's here in North America four years from now. So there'll be a chance to see guys like him, Erlen Ha, for Norway, both of those going to Todd. I got randomized Norway in this one. All right, second of three boxes, another three box random team break in the store. Check it out. Right next to me on my phone, we've got Thursday Night Football on. Broncos up three zero on Amazon Prime. This break brought to you by Amazon Prime. For the last World Cup was Prism the only card release. You know, I don't remember. That was a long time ago. Dennis, what's the best soccer prox to buy tops or a Panini? It depends on what you're chasing. Both of those companies have different licenses. So I want to say Panini has the FIFA license. In fact, they've been around, they're an Italian company. They've been around for a little while doing World Cup sticker books. Oh, there's Javi Alonso, nice one. Nice autograph for Brian and Spain. Pretty good, great midfielder. So if you're looking for like these guys in their country uniforms, their shirts, then Panini generally has those. And I think tops will have some of the big leagues. I think they have the UEFA Champions League, but I guess Panini has La Liga, then the EPL as well. I think tops has a UEFA Champions League license, so yeah, it just depends on what you're looking for. I think just in general, there's not a lot of soccer. There's more than before, but not a lot of soccer is printed on a yearly basis. So, and obviously these World Cupsets don't come around every year. This is a good time to get into any kind of soccer. Cristiano Ronaldo for Portugal, that's probably his last World Cup too. That'll be for Chase. Let's see if we can find maybe something a little more especial for those players here. Nice Bucaio soccer right here too. You might be one of the big names for England in this World Cup. That's our second box, third box coming up. I believe it, Dennis. Yeah, Dennis was told that soccer products will probably be going up. Yeah, I believe it. And Mr. Flyer-Hawk saying what, these box are already 50% more expensive on eBay? I believe it. With a World Cup in what, 45 days or so? I think each day that goes by as we get closer and closer, there'll be more and more demand for these.  If you were sharp, if you were really sharp, you would have joined all of our soccer breaks over the spring and the summer. But now I think people are getting wise to it. But still, better to get in earlier rather than later. Especially at a premium cost. We keep checking Jaspy's casebreaks.com for all the new soccer releases throughout the rest of this year and beyond. I think with the way the World Cup schedule is, we were taking a glance at this the other day, yesterday and we'll probably keep talking about it. But I don't think that there'll be a time where we will be watching soccer together, World Cup stuff together at the same time. All the matches will be kind of overnight when we're off air. But, well plenty to discuss though. Plenty to recap during the soccer breaks. Yeah, Dennis, I just imagined when the World Cup starts up, how much there'll be, a lot. And even beyond the World Cup as well, once it's done and depending on who wins, those teams might, maybe the final four teams or whatever will still probably be pretty desirable. Especially if there's some surprises. I mean, I always look at the groups and it always seems like it's gonna go chalk, right? But it's never like that. There'll be a few groups where there'll be some surprises. There'll be a big club that doesn't make it out of the group. There's always some kind of drama that happens with these national teams sometimes on the way to the World Cup. And the third and final auto of the break is, is a midfielder for Spain, Yettermi Pino. That goes to Brian Croft in Spain. Last spot Mojo strikes again, 70% of the time. Last spot Mojo hits 100% of the time. Allegedly, that's what they say anyway. I guess that's what people say. I guess that's what people say.  Nice little break there. I'm Joe for jaspyscasebreaks.com. I'll see you next time for the next one. Bye bye.


All right, good morning, everybody. Thank you very much for attending. I think I've succeeded into tricking you guys to come here with a fancy title. So hopefully, it's worth it. So Alice in Wonderland, networking in DevOps with a splash of OpenStack. I think you'll get the picture here in a little bit. My name is John Willis. I am a VP of Customer Enablement at a startup called Stateless Networks. Botchakaloop is probably the best way to find me. You can attend to just be on Twitter all the time, right? So that's my kind of portal to life these days. And then I try to put, there's a lot of references. I'm going to talk about books. People get really annoyed at me because, like, John, every time you give a presentation, I have to add seven more books to my reading list. So anyway, I put a little bitly there that it's basically just a bunch of presentations, references, and stuff. And I'll add some more, because I usually pretty dynamic here. I'll think of other things along the way, and then talk about some book I didn't even put there. So the overview is we're going to introduction who I am, why am I qualified or not to be here to talk to you guys about something. SDN opportunities, yeah. We'll go around that. We'll kind of talk about what does DevOps really mean and what's driving it, possibly, for the network. And then I'm going to take a little history lesson on DevOps, because one of the things you'll find out I've been doing this thing called DevOps for quite a while. And everybody says that, but I've actually been doing DevOps for quite a while. I was at the first DevOps days in Ghent. And that was only five years ago, but I was playing around with Puppet seven years ago. So you'll get the picture shortly. And then I'll talk about, like, what's the possibilities of networking in DevOps? And hopefully, that will be the real exciting part of this presentation. And so just one quick, I don't do product presentations. I do when I'm with a customer. When I give presentations, I like to talk about information and kind of try to get people thinking deeply. So this is really the only slide I'm going to talk about the company I work for. We stateless networks. We're a web scale for networking. If you think about what Chef and Puppet have done for compute, we're trying to do something very similar for networking. It's a very interesting model. If you want to learn more about it, please ping me. And I'll give you a demo or whatever you want to know about it. We'll have lots of fun there. So who am I? I'm an old dude. I'm actually 55 years old.  And I do cursal periodically too. So if that offends you, I'll try to do really bad curse words on this one. DevOps days, we curse like this no tomorrow. We're drunken sellers at DevOps days. But I'll try to curl it down here. So I realized I've been doing this like four decades. And I've actually had four careers in the four decades, which is kind of cool. I started out as an IBM mainframe guy. As you wrote a sembler code, if anybody's old enough to remember companies like Candle and Landmark Systems. And then I became a Tivoli guy.  And I still have scars on my body from working with it. But it was fun. And then I got out of the Tivoli business and really started doing, really focusing on the kind of open source version of that, which were originally things like Nagios and stuff like that. But it drove me right into Puppet Chef. And I actually was the ninth person hired in at Ops Code. I think on my resume, John Ospar says, or there's a guy out there that says, he's the guy who didn't hire John Ospar. Mine is going to be, I'm the guy who hired Matt Ray. Where are you Matt? So there you go. That's my claim to fame. So I did a lot of cloud. I actually recently worked for a company called Stratius, which was sold to Dell. It was a CMP cloud management platform. And today I work for Stateless. Network's focusing on the network. It's kind of my fourth career, which is networking.  And so if you don't, these pictures are actually from a Salvador Adali collection, which Alice in Wonderland. And actually I own a couple of these prints. So I wanted to tell you kind of a story. And I'm writing a book for O'Reilly called Network Operations. And this is kind of a short, short version of the first chapter. In 2007, I'm at Oskon, and a friend of mine introduces me to Luke Kniece. Luke Kniece, founder of Puppet Labs, has given a presentation. And I just finished doing configuration management for some of the largest companies on the planet. And it was a really bad form of configuration management. But I sit in his presentation. I see this young kid, and I'm thinking, what is this kid going to tell me about? I just got back from B of A. And I've been doing it. And five minutes into it, I'm that annoying student like, Luke, one more question. And I got my pad out. And I realized it was a life-changing event for me, honestly, because I realized everything I had been doing for 10 years prior was wrong. And I realized that this was a generational change in the way we did configuration management, and IT management. I think most of the people in this room probably realized that. And it changed my life. And I worked with Puppet for a while. But my real breakthrough was I got to meet Adam Jacob. He hired me. I was the ninth person in Ops Code. He hadn't had a real blast. But one of the things about, the minute I saw Puppet, I got it. I was totally in the subtraction, infrastructure as code. It all made sense to me immediately. But I sat down with Luke, and we had a cup of coffee. And he was explaining his vision for this. And I was like, Luke, you've got a great practice. Great, this is going to be able to do it. He was like, well, John, let me tell you the real vision. He says, operations is going to become like software engineers. And I'm like, if you have office space as a lumber, I'm like, yeah, I don't think that's going to happen. And he talks about how operations are going to start writing code that they're going to store in source control. And I was like, yeah, I don't see it, Luke. And it took me about a year to actually, it wasn't to a year later, at a velocity conference where Adam Schaefer gave a presentation about agile infrastructure. And I realized, oh my god. I knew he was right about Puppet. I didn't believe he was right about operations becoming more like software engineers. And so that really started me on this journey of what really, I think DevOps is about. It's about collaboration and engineering and software. I've got this kind of elephant in the room thing. So the discussion of SDN, this isn't really about SDN. I think SDN is this overload. I mean, SDN is awesome. Control plane, disaggregation of switches, moving to control plane, all that's cool stuff. But there are a lot of forces in play that I think are driving this opportunity to allow the network engineer to start thinking, going through that transformation that I went, when I sat down with Luke and thought Luke was out of his mind, I think my quote was, that's going to go down like a lead zeppelin. And I think that resource of some shifts, kind of tectonic triffs, shifts that change things for compute and just admins. And I think SDN is the buzzword for that. But this is the blind man in the elephant parable. But what are the shifts? It is SDN, but it's also open stack. Open stack is putting enormous pressure on classic legacy network engineering. Is there anybody in the room that disagrees with that? Network functions, virtualization, open flow, the virtual switching overlays. These are all things that are just kind of driving. We've got to have to move fast and faster in all areas. We can't have these three areas be extremely fast in this area be really slow. Because everything slows down. It's the bottleneck. But what's even more interesting to me, and what was interesting to me seven or eight years ago when I started working in Puppet and in Chef, is the underlay. So we tend to forget the underlay. We say SDN and everything's great. But there's really cool stuff going on with the Linux-based network OSes. Like Arista, I've had this great opportunity to play with Arista in the last six months. And the programmability of that machine is insane. And then you look at what Cisco has done with the new 9K. And you can run all those containers on these things. You're in KVM on Arista. You start putting other things in there. And then you get down to something like Cumulus Networks, which is the complete disaggregation of the software. It's identical to what happened with Sun and AIX, Solaris and AIX. And we went into Linux. Then they started just buying different hardware and different software. And Cumulus Networks is kind of a disrupter for that. They sell you the Switch software. And they give you a list of hardware vendors that you can go to and use. And then you kind of move on. Big Switch, bare metal switching. They were down in the booth. Had a booth the other day. So I think the meta point is our switches are starting to look more like servers. And how we treat servers probably or how we treat switches should actually be the way we treat servers. And I'll give you some data points. So seven to 10 years ago, I used to ask the question of every enterprise I went into is, what is your sysadmin to server ratio? And it's not a great number. And it doesn't tell you everything you need to know. But 95% of the people that I asked, and I got to visit some really big companies, the number was like 1 to 50, maybe 1 to 100. Today in a kind of a company that's adopted DevOps principles, large enterprises that have adopted, it's 1 to 10,000, 1 to 20,000. And I heard a story of a company, a well-known company that is in a classic legacy that's basically about 120,000 to 1 ratio. Now seven or eight years ago, if you want to, I didn't ask this question seven or eight years ago, what the ratio was to network operations or engineers to switches, I know what the number was. It was probably about 1 to 50. And it's kind of interesting enough right now as I talk to people now, if you're not web scale, if you're not a unicorn shop or you really haven't adopted DevOps in networking, you kind of forgot about those people, it's about 1 to 50. In fact, there's a large bank I just recently talked to told me that they have two people managing 40,000 servers, but their switch ratio is still 1 to 50, right? So, I mean, that should just scream at somebody who's in charge of an infrastructure, right? So in summary, you know, in summary, basically, SDN is definitely driving a lot of this stuff. And you know, I'm not down on SDN, I just think the programmability from a guts and underlay and somebody who likes to like really fix the infrastructure, it's not there yet, right? Like there's a really lot of smart people are figuring out how to put abstractions on open flow and flow tables and there's projects called Frenetic and really cool stuff. And at some point for dummies like me, I can go in and have a lot of blast, but right now the underlay is really a lot of fun and what's driving a lot of that is, again, network, open networking, it seems to be the norm that open source is part of, I mean, it's always kind of been part of networking, but now it's in your face, open. Things like cumulus networks. Obviously, network virtualization is changing everything. Everything moves around, nothing static. Clusters become, you know, we get our service chaining as part of the clusters as they move dynamically. And then open stack, right? So, I promised you a history review. The thing is right now, I think Michael, anybody see Michael Cote's presentation yesterday? Two people, yeah, he's pretty awesome. Michael works for a 51 group. So they've recently done a survey on DevOps and I used to say about three years ago that I used to try to convince people to go to DevOps in the enterprise to say there was this 3% club and 97% of people in IT infrastructure are not in this club.  And I think the number now is like more close to the 20% and Michael said they did a survey for 51. They believe that it's about 20% of the people are adopting some form of DevOps. The good news on DevOps, like my work is done because like the memo's out, everybody knows about it. Everybody's gonna be talking about it for compute, right? When I know that the evangelism job for me is done. When I go down the exhibit hall and every vendor says they're a DevOps vendor, right? Score, done. But here's the thing, like seven years ago, like we think, oh, that was easy. No, it was hard.  And I'm like, I know exactly what they're gonna say. Like, yeah, but you don't know. I'm like, do you think those CIS admins and legacy were like really kind to me? When I walked into their office and told them that they had to do this subtractions code and they probably should store stuff and get and maybe thought about behavior. Wait a minute, that sounds like those developers.  And like we won that war, but it wasn't easy. So all along the way, I like to make fun of things. And so I make fun of those old legacy CIS admins and I have an archetype, he's called Bob. You gotta have a Bob in every story, right? So Bob is great. Like Bob's got a Bob directory. And there's Bob scripts. And if digital properties could have coffee stains, they'd be on Bob scripts, right? And, oh, that one was funny. Come on guys, all right, all right. So the thing is that, and Bob kept that really tight. And it literally looked, it was like hard code to read too. There was some purpose in that, right? And I would say when Bob dies, everything gets screwed. And Bob was a big parallel SSH, right? And Adam Jacob used to joke, he's like, how many people used to do it, do it five? And everybody chuckles, right? And you know, and then you try to talk to Bob. All right, Bob, I got this idea about how you can change things and it's a chess match. And the first thing he says, well, John, this sounds all sounds good, but I don't trust it. You know, this thing that's gonna go magically do stuff and it might do stuff that I don't want it to do. And oh my God, like, calm down, Bob, really. Like you're gonna tell it what to do. Like there is some DSL and it's not gonna go off and do crazy things that you don't want it to do. And he gets past that and then he goes into the snowflake argument. Well, you just don't understand my application. It's special, right? And then you're like, okay, let me see it, Bob. I'm like, Bob, the last 10 places I've been doing exactly what we do. He's like, no, look at this. Like, that's my sequel, dude. Like, okay, and then you finally get past that and then you get to the, well, all that could be true, but it can never, ever, ever, ever break. My system can never, ever, ever, ever break. Like, okay, let's talk about failure modes. Let's talk about anti-fragile. Let's try to go that route. And in the end of the day, it took about four runs to get, Bob, we used to joke at Ops code that if we walked out with a non-success, we'd be like, they're gonna call us back in a year, because they'll get it. But the end of the day, it was about change. It was about the fear of losing a job. All that good stuff that we all fight for everything we try to do when we try to apply innovation. But what forced Bob to change was, there was this tectonics that just basically came in and changed their life, right? Like, the disaggregation of operating systems like AIX and Solaris, right? You know, Linux became pervasive. And that was one shift, but the second shift was even more important was really ephemeral infrastructure. And that was anywhere from cloud to just self-service on steroids or even virtualization with real high-quality self-service. I mean, the idea that people could go from six weeks to six minutes to get resources. And if Bob's job was, in the six-week scenario, it took Bob two days to do what he had to do to get it done, that was okay, because who cared? But when it turned into six minutes, Bob had to go down to two minutes. Or he was out of a job, or he just, it didn't work, right? So that world changed for Bob. So early observations in the network world, so about six months, I've had this passion of trying to do this evangelism in the network space. I knew I was in the right space when the first five people that I talked to said, you'll never change a network engineer. Never happened. I'm like, okay, I heard that one before, right? And so Brent Salisbury, if you don't know him, you should definitely know him. He has this great side, you know, still being used 15 years, the trombone, right? So what are my early observations of these network folks?  All right. The archetype here is Bill, okay? And Bill runs accept scripts, tickle, maybe some pearl. Lot of spreadsheets, actually by the way, there was a lot of spreadsheets for Bob too. He did a lot of cutting and pasting. He just kind of didn't let everybody know. Seems like the network, in my first observation, the network engineers are not ashamed of doing cutting and pasting. The Bob's way, they were like, they hid it like, oh no, I don't have, I don't have Excel up. No, no, no. But Bill has got the same argument. I don't trust this thing, John. And then you don't understand my network. And then, you know, and then the ever, ever, ever break, and I get the break thing, right? I do. Like, you know, router protocols, I've learned a lot in six months, right? Okay, I don't just walk in and say, oh, change this. And you know, this is complicated stuff, no doubt. But I am going to mark my words, be in jail because I'm gonna murder somebody. The next time I hear them say, well John, if you bring down a server, it's no big deal. But you bring down a switch and I say, have you ever heard of Knight Capital? Right? And if you haven't heard of Knight Capital, Knight Capital is a poorly configured server, bad hygiene, no DevOps, that accompanied it in three to $400 million in three hours and was out of business in 24 hours because a server went south. So again, I understand the complexity of networking, but don't, like, the problems we're solving, that Knight Capital, if you read the SEC filing on it, could, in fact, I've talked to friends at work in high trade in those type of businesses and there were all sorts of things that they were doing in quote unquote DevOps that might not have stopped it, but they wouldn't have went out of business. They would have quoted it in 10 minutes. They might, that server might have been rebuilt as an ephemeral infrastructure and it wouldn't have had that bad hygiene that it had. There's three people I want to thank in my last six months for really just being people that have helped me understand a lot and just incredible people. And I'm pointing them out both for you and me. If you don't know Brent Salisbury, he works on ODL for Red Hat. He's just, you know, he's a brilliant young man and just very open for sharing and just, you know, and the thing about these three guys is they really want to drive DevOps in networking. I mean, they're looking for guys like me. They haven't figured out yet that I'm not that smart, so don't tell them, but they're looking for the DevOps folk that the people that have been doing this because they're like, come here, help us understand what you guys did, right? And then Jeremy Shulman over at Juniper, Jeremy wrote the first puppet. He wrote the NetDev Ruby Jam for puppet on Juniper. And by the way, every time a new vendor comes out with their kind of NetDev, they don't even change the name of the VLANs that Jeremy wrote, like the Ansible one, the Chef one. Like they just say, I laugh. I'm like, oh yeah, there's Jeremy's stuff again. And then we've got Colin in the room. Colin is to me an encyclopedia of network knowledge. I mean, when I get to sit down with him and have coffee or a beer, I literally feel like I should be taping him. He gives me so much knowledge. So enough of that. Before we get into the DevOps and networking, if you like anything I'm saying, I got some pointers to all the presentations. Over the last two years, I spent a lot of time talking about culture. I'm a big believer in this man, Edward Deming. I believe Edward Deming created Lean in Japan. Lean became Lean IT. Lean kind of became Agile. You can point right from Deming to DevOps. In fact, I have an article out there called Deming to DevOps. And so the core of what that comes out to is, me and a friend of mine, David Edwards, we created this acronym called CAMS. It's reasonably sticky in the DevOps world. Culture, Automation, Measurement, and Sharing is how we can put somewhat of loose taxonomy around what DevOps is. And what you'll hear most people say, if you don't get the culture right, everything else is just useless or nonsense. And it really is true. I mean, you can't just take great technologies in cloning. I mean, you have to break the bone from the way people think and how you can't just put puppet in front of a network engineer or tell a network engineer to go learn Python and all will be well. It starts with some type of, of cultural behavior shift. And so when I went back and I said, okay, what, if I could come up with one word over the last 10 years, that has, you know, that really kind of manifests what has been the most success in DevOps for compute, if we'll just say it that way. And it's the power of pull. And if you think about pull, there's two modes. There's the pull for change, and there's the pull for flow. And if you talk about pull for change, what are we talking about? We're talking about Git. And Git probably, I think Git might be, when we look back in the next 10 years, more innovation was probably caused because of Git and the concept of the workflow behind Git. And you think about how people collaborate in that model. I mean, right now it's the only game in town.  And you used to go in somebody else's home and I'm like, no, no, you can't teach Chef. You can teach people, and now I realize I was stupid arguing against that, right? There's such a power in that workflow and when you see it and you get it. And then the other pull is really the core of this continuous delivery thing that we've got going here. Right, it's that flow. It's a pull going into, you know, I wanna get something into production. What's the classic chain is something like an SVN or it should be SVN, Git or GitHub, and it goes into some Jenkins process or some CI process. Then it goes into some behavior-driven test development. Then it goes into production, maybe driven by something like Chef and Papa or CF Engine, right? So those are the two things that, you know, like I think a lot about like, how can I try to break the bone to heal the second time, knowing what I know now, right? And so I'm working on a book with Gene Kim, Gene Kim, The Phoenix Project. We've got another book that's like ridiculously late, so please don't ask me when it's coming out. It's called The DevOps Cookbook. And so we've compiled a lot of things and hacks and, you know, I think Colin, you know, it's fun for me when I first met Colin, you know, like, even in the DevOps world, a lot of people don't know this is fabulous tool called Value Stream Mapping. It's an amazing tool. It comes out of Lean. ThoughtWorks is a company that really, that's where I learned it from those guys. It really is a flow. If you want to learn more about it, there's a book called Learning to See. Infrastructure is code. I think you, if you understand Puppet and Chef or CF Engine, you should get that.  Continuous delivery, there is the hot button for everybody in application flow. You know, how do I get things from an idea into production and how do I make that bulletproof and, you know, you hear the 100 deploys a day, 1,000 deploys a day. There was an Amazon presentation, if you hadn't heard this a couple of years ago, where I think they were talking about 1,000 deploys in one hour to production. Now Amazon's a weird beast, right? You know, so it's Google, like, so that's not an number you should, like, oh my God, I'm not doing 1,000 deploys an hour, right? But in the production world, people are, like, achieving spectacular things in terms of how they get things in front of customers. And if you read Eric Reese's Lean startup book, right, Eric Reese was originally somebody who was kind of invented the end per deploys per day at a software company, right? And they got famous, wrote a book, now he gets $8,000,000 to speak, right? So another, one of the chapters that I'm working on is this embedded engineer thing, right? So this worked really well in the DevOps transformation from SysAdmins and Dev versus Ops, where the idea was you took somebody from the Ops team and you actually put them their responsibility to live in the Devs team, six months a year or maybe permanent. And it crushed, in case this great situation where there was a change of culture, there were behaviors, there were things that the Devs would say, oh, we're gonna do this and the Ops guy would say, oh, no, no, no, no, don't do that, you know, and they were like, oh, why? And he's like, well, because when you do that, and it really worked well, and I have a whole chapter about this and it will work. So I'm wondering if that's gonna work in the network space, right? Is there this idea of a shift around, and I'm getting an odd from Colin? Yes, a Kanban. Kanban is a fabulous tool for operations or organizations that are interrupt driven. So, and again, Kanban is really another thing that comes right out of lean. Somebody told me the other day, and I was like, oops, I forgot that one. Somebody gave a presentation yesterday when talking about how the network engine is pure. Darn, I should have thought of that one. Right, of course. I'm gonna make some config changes. Hey Joe, what's your schedule? Let's go ahead and peer on these changes. I mean, it's another reason why I like the Git model, because basically a pull request is a collaborative change, right?  So if you're not inviting the network engineers to your hackathons, oh, first off, if you're not running hackathons, you probably should be internal hackathons. And if you're not running an engineer, or better yet, your network engineers are having their own hackathons and they're inviting the ops people. And at the end of the day, it's about having fun, right? Like, you know, you've got to break the bone. There's gotta be a sense of, I remember about a year and a half ago, I went into this large credit card company, and it was like just, you know, classically old, you expected the worst. And we got into the war room where all these, the DevOps group worked. There were Nerf pistols all over the place. There were, you know, the soda machines. There was a foosball table. I was like, my heart was like, because you only only see that stuff in the Silicon Valley and startups, right? And I'm thinking like, okay, if you were at an artwork group that's on the fifth floor and a bunch of dirty old cubicles, why don't we put them up on the sixth floor in a war room and put Nerf pistols and see what happens. Maybe somebody at two and a half that you get pissed off about shooting everybody with Nerf pistols, right? And like, it's about having fun. So what are the opportunities in this new world? I mean, there's a debate now. I have this argument, Jeremy Shulman, a lot about do network engineers need to become programmers? You know, I don't know. I've heard some really incredible people over the last five years, six years, that each one of them would tell you they're not programmers. I would probably say they're lying, but the point is they're really not programmers. I had a guy, John Vincent Lucis, I hired him, right?  You know, so what I would say this is, I don't know where the argument feels. I do know, I think that the analogy is like languages. If you're a world traveler and you know, you may not have to be fluent in like all the countries that you travel to, but you better have enough language knowledge to ask like how much something costs or where the restrooms are, right? You know, and I think that's my theory on polygons, which is learning multiple languages. There are some purists that would say you should never do operations unless you know five languages and you should be a programmer. I don't agree with that, but I do think you, I think everybody, you know, what is it? Mark Andreessen said software's eating the world, right? And he didn't just mean applications. Like software is a reality in everything we do. It's network security, operations. So we really need to be part of that. And so we might not all have to be programmers, but we probably need to be adaptable enough to know to ask where the restroom is, right? Or how much it costs. So abstraction, so how do you start thinking about flow? Maybe you keep stored configs in GitHub, right?  Maybe you do some form of unit testing if that's available. You do some type of behavior-driven test. I'm gonna show you something I tried to do at Hackathon where I tried to use this whole flow for stored configs on Arista. Or actually use Cucumber on the back end to do behavior-driven development. Low-hanging fruit in this space. Again, early observations. You know, a lot of stuff on the VLAN stuff.  VLAN creation, VLAN port mapping, link aggregation. Easy kill. If that's something that's like happening a lot in your shop, then you totally miss the SDN thing. But besides that, you probably should be thinking about automating that, right? Like if there's three people creating VLANs like eight, nine, 10 hours a week, whatever. Like there's really easy ways to fix this. And some of the ways, our stateless, we fixed this.  Chef has a NetDev module. We have a Ruby abstraction module to do things like that, to do. Now you can get into more high-order stuff, like for example, like automated bills. Martin Fowler, who was one of the original Agile manifesto authors wrote an article a while back called Immutable Servers. And I was feeling like I'm gonna get punched in the throat when I say immutable switches, but we used to joke in the Dev Ops world, like can your server pass the throw it out to six-floor test? In other words, if you threw the server out, could it go back to the same state? And the truth is, with our products, some other products, you're able to do that now with switches. Like if it's a leaf and a leaf spine, then you can actually field replace it and put it back. And it go back to the state that it is. So we're there, in an hour, not everybody's doing it, rolling software upgrades in that work. So how do I hit a whole bunch of top-of-rack switches? It's the same start of how we did cluster updates. Like we can do blue-green deploys for switches. Like, and if you don't know about blue-green deploys, read Jez Humboldt's continuous delivery book. It's awesome. You know, automation compliance. And here's the one, this is the hard one, right? So there's a company called Etsy, and they used to put these shirts like MTTR is cool, right? And so if you know what MTTR is, it's being time to repair. And one of the things that we learned really hard, and still for it, if there's 20% get Dev Ops, there's probably still 10% to get this concept I'm about to tell you, is that failure is awesome. The more you fail, the more awesome it is.  I'm glad everybody got that. He's not the only one he called a shithead on Twitter. Raise your hand if the nice of Talib has basically called you and ended it on Twitter. Come on, please. Oh, come on. I know 15 people that had Dev Ops shop. He's done that. So that's a badge on him, by the way. But meantime to repair, right? It's like, it's not like trying to figure out meantime between failure and trying to figure out how to stop the black swan and how are we gonna, like that's not the world we're going into or we live in.  And when it breaks, it's an opportunity. In fact, there's a great story, I'm totally gonna run out of time, but there's a great story with Facebook says that, so they give the story like all these badge on and Dev Ops come and say, our developers pushed the production on the first day of work.  And I remember one time somebody raised their hand, like, yeah, yeah, but what if they break the system? And it was like so canned for the guy from Facebook, he said, that's awesome. They actually get like a bonus. Because if they can on the first day break our infrastructure, that we've got 30,000 people or whatever, the smartest people on the planet are built. And this guy figured out how to break it. That's awesome. Good job, well done, right? So, I mean, again, that's gonna be a hard sell in the network space. Wham! I wish I could say I planned that, but no. So what else?    But like, you know, if you look at the stuff that's going on, open flow, OVSDB, you know, the open daylight, I mean, I think that's gonna happen. I was at one of the early open daylight summits and I was at the first open stacks on it. And to me, the attitudes and the hype and all, and a hype in a positive way, it was identical. It smelled to me like, this is what open stacks gonna look like in a couple of years. So quickly, some case studies. The first one is just an interesting one. It has tones of DevOps all through it. It's a telco that recently worked out. They use a Rista, Leaf Spine Network. They're using Stateless Networks. They use some Puppet Razor, Piston for OpenStack and Cloud Foundry, Service Mesh Boundary, Pum Grade, okay? But here's something that's cool about it, right? So it is really, we're following it on this model, but one of the things that's cool about it is they're kind of doing this two-stage build of these. They're planning big. Like they're expecting that they're gonna basically do lots of clouds. And then what's even cooler is not that they're gonna build lots of clouds for lots of people, but they're gonna actually clouds, instead of just virtual instances being ephemeral, the clouds themselves might be ephemeral. So in other words, they're asking for requests to have a deep provision of cloud. Like this cloud, this one cloud of the many clouds that we have may only exist for a month. And so what's cool is that, so one of the things we're getting involved is, I mean, literally you're rolling a rack. So imagine a world where they got all these things and they've got some trigger at 70% capacity, they roll in more racks. And then the racks get like rolled in, power gets turned on, and they get configured to a network state. And they call it the razor state, right? So which is the, because they're using razor, but basically it's got this base, like I'm available and ready to be used rack. It's done through attestation. It's got, everything's biosting. We kick off the, so Rista has a zero touch provisioning, which is kind of a pixie boot, which then we drive puppet, which then does razor and everything's like ready for the, ready to go, hot available racks for use. And then somebody comes along through an API Crest and says, oh, I wanna turn those four racks into an open stack. And I need the first rack to be the cloud control and the other three to be the compute nodes. And then I need this to be, these three to be a Hadoop cluster. And then I need these. And then, oh, by the way, I want to deprovision that one back to razor state. So I thought that was really interesting and again, really thinking about how kind of ephemeral and thinking beyond just we're building open stack and we've been doing it for four years and we got our first WordPress app up. So that one was funny, right? And then this is the one I did a couple of weeks ago at a hackathon. So I set up this hackathon. It was an SDN hackathon. I volunteered to run it. I wanted to do a dev ops thing. Only about 10 people showed up. There were all a bunch of college kids from Cornell and of course they wanted to work on the control plane and do SDN for WAN. So I had to do it all by myself. So I didn't get to complete it. But the idea was this kind of flow that I've been talking about. And I've gotten this idea for a couple of customers. I can't share what the customers are giving me. But literally they're starting to stir configs using either Ruby templating or Ginger, which is a Python templating mode. And then they're actually storing them in GitHub. When they do the pull request, they're actually running them through kind of a Jenkins build. They're using Vagrant to set up mock environments. If it's just like some of the open stack stuff, MiniNet, but if it's like Juniper or it's Arista, there are virtual appliances. Arista has this VEOS. So imagine a scenario where you're configured an MLag pair with a fake spinus three VEOS's and you made the change in the config in GitHub, you made the pull request, it got built, the images got started, it got configured, and then you ran Cucumber to go ahead and ask a question, is my MLag pair up, right? I mean, that's pretty cool, right? So that's about all I have. Couple of things, I would say Cam's not Am's, right? Don't forget the culture. It's always about the flow. People ask me who this picture is. Since I read the shirt, you know, but it's Edward Deming. I think if you really want to know all the answers, start with Deming, honestly. It all starts to make sense when you go through and you understand everything that's happened from Lean to Agile to...    And I always say that, you know, don't let your enthusiasm look like arrogance. You know, you gotta be real careful there.  You know, you could be doing that all with configs. Like, well, no, I guess I'm really complex for auto protocol definitions. You know, make sure they understand that. Anyway, I'm done. Thank you very, very much. Thank you.