Deputy Director of the Monashi Research Center, and Blair is here with me. We're going to share this talk Go half and half. Hopefully it won't be too much disruption changing over Okay, hi all welcome My name is Steve Quinnette Deputy Director of the Monashi Research Center and Blair and I Who's also part of my team. We're going to give this talk today We're talking about our view on how We help researchers using the cloud HPC and all these things put together we're going to use slightly different words and I'm going to spend the first ten minutes of this tour actually explaining what those words mean to us and That framework of thinking and how that drives what we do and how we do it There's a third member to this team Vojtek who is not here today with us And we'll look you'll see his bits influence in this work as well So our equipment and our work everything we do is full of HPC like things It's got RDMA. We've got GPUs got lots of cores Parallel fast systems and all these sorts of things But I don't think what we do is HPC And I say that painting you know with a lot of pain because I come from a HPC background Right and you know part of this thing is how do we start thinking about it in a slightly different way that? Let's just really move forward and influence the world But to begin with I'll start off with how we used to talk about this five years ago because we've even changed since then and We used to five years ago and there's two points here We used to talk about the peak in Longtown We used to sort of say the peak with a HPC guys and the Longtown with the guys doing stuff for window shares Right and you usually supported one or two camps and as a result There is this pit in the middle of un a people who weren't serviced at all right There's sort of the guys missing in the middle But if we're kind of looking at today what we kind of see we understand and you'll see this will come through in this talk is that the peak are more like the Leading researchers and they build the tools that other researchers use right they get they get proliferated right But then there's another conundrum there because the peak researchers in that tool set that they create are using Tools but other researchers used right so even the peak are kind of long tail Right, so we don't really talk about peak and long tail so much anymore And we definitely don't associate peak with the idea of traditional HPC The other thing we did is we used to talk about when we were engaging with researchers And how we do our infrastructure In the way that Gartner used to talk about that the hype cycle so in the early phase It's all it's all iterative and all experimental and at the very end of the phase It's this discipline engine room which you give to the IT guys and we tried that we actually tried really hard to Kind of make this spectrum work and think that we could hand it over to IT guys or even HPC sensors for that matter And expect that they could do the right things What was really interesting in the keynotes we had on Monday morning from Gartner itself? Despite five years going on they are still using This sort of framework of thinking and they call you know the early part now this mode one I guess business people don't like all extra words and so they went with something simple mode one And and the discipline engine room. Oh, sorry the other way around mode one is the discipline engine room The stuff we give to IT people and and the highly experimental part, which is a result of The use of the clouds and things today As as mode as as the mode two But even still in that presentation they recognize there's this third layer in between and it's more like a spectrum How you move in between you know and and even more so she made the point of saying that actually our IT infrastructure across the board is Is moving towards? Like more cloud style of things All right So today what we say instead and this is how we think and communicate and what we do We actually say that researchers build and use 21st century microscopes and I'm going to just explain to you what that means So if we think of the humble microscope It kind of came into being around 200 odd years ago at that point we as in mankind Learned how to machine brass really well. We learned how to machine Lenses really well and reliably and someone had the insight I guess he was sick of getting a microscope and trying to get their distance, right? Sorry, I'm a little Yeah Hand how one and And so we built a little machine that join it together using brass, right? This was this created the biology biology discipline and research and there's a Boom of scientific outputs that result of that as a result as a result of that You know a microscope has a light source, which then a lady put some sample in and we have knobs and filters We're light through passes through this thing and through the knobs and filters. We're able to tune The device to help us see things that we couldn't see before Right, and we have a lens obviously by which we can see Drive that process now I want to relate this to Tony Hayes for paradigm sort of speak and I'm going to map it to a slightly mathematical viewpoint because once again computational science HPC Whatever else I really struggle on subjective Conversations, right? So the microscope back then really produced just outputs. They were wise there were observations Right and the boom of research we had or the first paradigm came from those microscopes Around the same time we had a boom of theoretical models in this case We had F's, you know the models were the bits that where we're having these innovations We actually worked out that Statistics and normals are actually a model and by that we can make various predictions and everything else We have new to we have everything else, right? so I want to come back to this in a tick but One of the questions we're gonna ask ourselves then is is discovery leading technology or is it the other way around that? Technology is leaving discovery or is it the perpetual cycle between the two and where are we and how do we use this to drive us? And if we ask that question then It becomes very useful to ask ourselves how and what technologies have been driving mankind, right? So we know that one of the greatest technology Evolutions we had was the industrial revolution where we basically over a hundred year period we started to produce more food than Then we had humans to consume right was the first time in mankind. We actually had more food than So we stopped controlling our population growth by starvation essentially, right? And that was a 5% growth compounded over every year compared over 10 about a hundred years. I haven't left and put that in this graph, but I've taken electronic ones out here The real interesting one is the red line, which is the speed at which we traveled across the Atlantic Right, and we went from steamliners to basically bowings with jet things in the 1950s, right and during that, you know, sort of 40 50 period of that innovation boom and We have flight was Air flight was was was special You know it was all this, you know, there was this boom of culture around air flight and everything else and a lot of industry Was bought but we never we didn't we hit 1950 and we actually stopped going across the Atlantic any faster at about 500 Kilometers now or whatever it is You look at the what's happened 40 years after that The US government had to help its airlines because the innovation was lost and the business models around everything had changed, right? So it's interesting to see these things Now forever in this room. We all know what this blue line is going to be about me having to say it, right? It's essentially Moore's law, right? It is nothing is Nothing else is like it in mankind's history and it's 50% compounded growth over a 50 year period Sure, it's sort of maybe stagnated a little bit now But it's not clear that something like it won't continue for a period of time yet The real interesting question actually is how is that influenced what we do in science and research? if We take our fourth paradigm model what it really means is at some point We actually could start using computers to deal with the fact that our f's our models are big and complicated Much bigger than what the human mind could do as a result of this we have in engineering We have CFD's predictions and all these things that we do through and all these discoveries We've made through if you like the third paradigm of computing or simulation, right? I can add to the graph and say well the green line is essentially the Size of the most expensive hard disk you can buy so it's like the peak of hard disks and the little green Yellow line is the growth of our sensory sensor capabilities Now these two together you can then argue have driven the fourth paradigm, which is around data in this case Data the why is really really big Right, and that's so as that's the idea But the fourth paradigm is really you could probably break it down into three different ways It's data mining and in which case The big why what we're trying to do is actually find what the f and x are we're trying to find what the knowledge is There is no we don't give it any prior knowledge in a Models right and there's data assimilation where we already have big and complicated models and we have the big data We've observed we're trying to marry or work out some equivalents between the two Visualization is still immensely Relevant because if it was true that you could data mine everything then we wouldn't need to do research whatsoever right and The best lens we can actually have is going to be environments They give us let us see the most and we have a facility in particular that The amount of pixels and the brightness of those pixels we can see in these facilities allow us Researchers to help discover things that they then put into models or help condition data mining from that point on And I've added this because it's really relevant to this meeting And we've heard a lot about the Internet of Things and I'm sort of sort of suggesting here that maybe there is a fifth paradigm Perhaps because I don't think it's really about the fourth and we're seeing it in how big businesses are thinking about where the future is And that is that this orange line is the number of devices on the internet or the internet of things And it's predicted to be the only thing that will continue at something that looks like Moore's law Right now the real question is how is that influencing how business works? Well think about ten years ago five years ago even you went on a Windows machine You had your email pop up and it was made by your institution, right now your email is probably done by Google your Verizon or something might be who provides your Telecommunications and there's there's several companies involved in part and doing the thing that you used to do by yourself before So because of these curves we can kind of see that the world is changing changing and to win for our researchers We need to think about what is that workshop and one of the materials that allows them to Play in the space and win So we say that the 21st century microscope looks more like Something that ties together the big instruments and all the things that produce this for our data The supercomputers and cloud infrastructures and the softwares on them that are the filters and allows to tune to see the things We couldn't see before and rather than light going up this thing It's data and it transforms as it goes up through this thing And then lens then is really the environment we interact with they are now desktops and other things like that So our facility Ames to create that environment where we can the it becomes the brass or the ability to make and tune that brass We use open stack and stuff and and and Blair will continue talking about these bits in a little bit And it has a lot of it was always from day one part of a federation to share and collaborate across Australia the nectar research Cloud we have Lyle in the room here and it was always from day one about specialist equipment We had no intent of trying to compete with Amazon if you like if it was just about dollars per core or Cloud bursting right the intent here was bringing the right equipment for our researchers To do what they need to do So we had rocky SSDs high memory all these things from day one The graph on the right is the number of core hours allocated per month and and it's been a literally a sort of Exponential kind of curve and had it how it's grown over the since we started which is not that long ago Which brings us on to what is HPC as a service for us or what is HPC and the cloud if Rackmon is the bit that lets us orchestrate our 21st century microscopes then the HPC part is really just another flavor It's just another part a component that other people connect into the bigger things. They're doing Right, so we're not really HPC first. We don't think in a HPC first type of way and so And the point here is then that actually what we're focusing on is the environment so as researchers are trying to connect everything with And I'm going to give you two in members as two examples and one is we had Australian's banks are actually quite powerful. They're really well well with our brand renown businesses I guess it means they rip or suffer a lot. I don't know The and and we did some world-first research were basically the bank and the and the researchers said that they want to do some data mining on some real F-post data electronic transfer data So it's it's highly confidential highly sensitive. They were trying to discover or think about whether they were categorizing Their marketplace well, right? The data mining required machinery which was not normal We were able to very quickly create a virtual environment and It's its own microscope. We were able to destroy that environment after it's do all the secure stuff Yes, we didn't have software defined networking doing for doing for us like at that time But we weren't that far right so that the concept is there is that hates PC Whatever it is. It was really really important They were able to publicly say that this was a world-first and they knew that only in the entire world only two US Banks we're going to be even close to be able to do something similar I don't know if they have by yet, but I imagine they probably have Which is quite significant, right? But maybe something that's a bit more normal The study of perforin is a protein that is used to that's in your cells That actually allows things to come in your cells they open and close and form whatever else And it's one of those tricky things. I was talking to Paul about this yesterday It's one of those tricky ones where like most of these Things we try to understand where we can't crystallize it easily So we can't just throw them in a synchrotron really easy and we need to see things on the scale which are beyond What we can do with the synchrotron so there's new equipments coming about new microscopes being built or instruments for those microscopes and They require computation to get us to the point of being able to see things Right it very much is that data assimilation problem And so the environment looks a little bit like this We've got some instruments has to go to HPC and it has to be shared and stuff for later use for come common things And everything in this circle is about how to produce an accelerated reproducible environment for Making this happen and what they're trying to do and this is out of the directly out of their nature paper Is this is the statement around the set of tools they use and how the pipeline of work So this is the bit that we need to reproduce for other people for the proliferation part But it's also the bit we need to make easy for them to make for the you know in the in the first part So we created this thing called the characterization virtual laboratory It's essentially a managed desktop environment. It's VDI, right? But it's already connected to all the HPC Equipment and all the data sources in the secure or appropriate ways if you like And it's also this sort of mass customization thing where we have a core way that we do it And there are certain flavors of these for the various disciplines that are pushing the boundaries We have four major ones in Australia. These are national projects and and Now listed the listed here Now why is this important because if I go back to that very first graph it tackles that middle gap and Now usage pattern for this is an exponential curve These are the number of people who actively use it So they're not accounts. They're actually active users on the right hand side is The number of times those are subset of those people are using it And you'll you'll see there They're 60 people who have used it more than a hundred times have actively used the sessions or whatever more than a hundred times Which is kind of scary when you think about the stats of and how we try and measure stats of HPC facilities nowadays, right? Well one last part about this is We give the researchers a little little app Which gives them a one-click to get them on to the virtual laboratory and the virtual laboratory really takes a form of a bunch of GPU enabled, you know VDI's Which is amazingly managed through slurm, you know So we use a HPC style Q managed to manage that resource And everything then happens through the web even the VDI connections So that's for the pattern My by the last thing I'll say before I hand over the Blair is we want to join those two paradigms together What we're doing with a characterization virtual lab in accelerating the peak researchers of the proliferation of those that sort of work with Security and this is important to us because we have a lot of medical Applications coming to be so if we apply the same problem the imaging to matching that to phenotype data Or if it's genomics matching to phenotype data We have a problem where we can't take the data off that environment until the governance of that project or the data says it's okay, and so we're We're we're in this phase where we stand I have to marry these sorts of things And with that I'll hand over to Blair Thanks, Steve Okay, so I thought I'd talk a little bit about I guess what makes that that engine room of the virtual microscope tick and Some of the prehistory there with the Nectar research crowd program because that's really worth mentioning Nectar was a you know pretty pioneering program at the time So that was established by the federal government and super science initiative In 2011 there was a small technical committee set up to advise on what cloud middleware We should use in the research club. I was fortunate to be on that committee Only by mistake really I'd been doing a bit of stuff on Amazon and not many people had at the time really I was working in a research group and sort of got pulled out of that and everything snowballed from there Tom Firefield who a few people may recognize his name Now Tom at OpenStack.org He acted as a consultant Into that group and did an evaluation of feature set and stuff across the different options at the time And keep in mind that that was approximately the Bexar timeframe for OpenStack So, you know, one of the highlights in the release notes for Swift in that release was experimental s3 support API support But the decision that we ended up making or recommending in that committee was actually largely Not to do with tech at all. It was more about the community process and the governance structure that was starting to spring up around OpenStack It looked very promising And you know ultimately I think we made a good decision So then so University of Melbourne also in Melbourne as Monash's Was the lead agent or is the lead agent for the Nectar program They established the first node the pilot node for Nectar Which opened up to to users in January 2012 So I guess that would have been deployed on DA blow. I think Monash our node we eventually joined following in early 2013 And we've sort of had this just in time features coming into Nova to actually allow our architecture there for the Nectar research cloud So we were one of the first Nova set like first major Nova sales deployments outside of rack space And now there's eight nodes across Australia with over 10 data centers and 30,000 cores And those 30,000 cores actually are that's just the the cores that the Nectar program itself funded to be built for public access It's worth noting that many of the nodes now including Monash Are adding a bunch of capacity and they're leveraging that infrastructure But for their own institutional investment or their members The other the other thing to point out is about the cells infrastructure because that's sort of that's kind of a new thing And open stack for many people now Whereas we've been doing it for a long time And I was actually I was kind of skeptical about that to begin with I have to admit because having been a user of amazon I was used to the region's idea and I had done you know programmed against that and I thought well that seems fine But actually it really significantly makes things easier for the end user You know they have At the time there was no support for regions and horizon Um the way we have things set up users just come to the one dashboard. They have the same identity everywhere And you know, we don't have issues of trying to sink keystone and this sort of thing They just have a drop-down list of azis that they can use And they don't even have to pick one if they don't want to The other big advantage is that we have a core services group that look after All the user-facing stuff the api's and all of that and the core that core infrastructure And down at the nodes we worry about the compute infrastructure and that sort of thing So we kind of have a smaller management footprint so Rackmon, which is sort of this funny abbreviation mix of it's just research cloud monash Is now about 210 compute nodes across two data centers About six and a half thousand cpu cores 45 terabytes of ram about 150 gpu's and volume CIF and a bit of luster as well is maybe about 1.5 petabytes of that is luster the rest is cif All integrated into the cloud infrastructure So hpc at monash we've had a hpc resource for quite a while It started out as the the monash sun grid i think and then sort of became the monash campus cluster It's a typical institutional hpc services everybody and everything phd students high end star researchers that sort of thing For a long while we've had a sort of a partnership model where those people that Have gotten grants to buy infrastructure We'll take that bring it in manage it through the cluster And then also monash will provide some of the operational expense there too And that's that's really good because i mean i talked to people in hpc forums and the problem of you know little departmental clusters everywhere and I talked to one guy last week who was managing 17 clusters amazing And then and so that's now called we recently changed the name of that when we sort of move things onto the cloud So that's now called monak And monak sort of if you like the one maybe one step ahead of massive which is the next resource Where monak we maybe in it we're innovating a little bit more at the middle layer And then massive is coming along and taking that and doing that at a larger scale as well So massive is is actually another federally funded project. It's Australia has national computational infrastructure It's a shoulder shoulder facility of that infrastructure specializing in characterization. So imaging and visualization And with a number of external partners and affiliates as well For example, the Australian synchrotron, which is co-located with my ash in melton So monak now is run almost entirely on open stack So all of our compute infrastructure there is running In a hypervisor of onto kvm What we did initially was actually just take an existing oversell that we had for the nectar research cloud and add to it build it out And just use host aggregates to control things so that the the cluster project could get to those nodes We also Went into luster for the first time previously We just had sort of nfs filers and this sort of thing attached to hsm And we had all sorts of nasty things happening like users trying to run hbc jobs on a Hierarchical storage file system and wondering why things were getting pushed out to tape That that resource is just all dual socket has well gear a mix of high core and high speed stuff for various workloads By and large though We see in terms of job numbers probably still over 80 percent single threaded workload I don't I don't know off the top of my head what that looks like in terms of the actual cpu time spent on the resource But we are starting now to see Compared to say five years ago an increase in the number of parallel jobs and people doing Sort of a bit of starting to dabble an open mp and this sort of thing just within a node or hybrid stuff Where they're going across two to eight nodes this sort of thing And initially because we built this as part of the nectar research cloud one of our architectural constraints there was To fit within the framework the open stack framework that we were using at the time And we were still on over network then this was a year ago, I guess And using multi host flat dhcp, but we wanted to integrate with luster so that that Proved to be a small challenge However, not entirely impossible to overcome So I guess People sort of want to know why why do hbc on open stack Well for us it was about Consolidation on on the one hand Our hbc team then becomes I guess sort of a customer of my team And those guys also can Really focus just on their operations. They're not too worried about hardware anymore. In fact, we're not really that worried about hardware either in my team Flexibility of course is another big one lots of people that are running standard hbc facilities especially with centos and that sort of thing they Typically say they've got bioinformaticians who want Ubuntu Seems to be a common pattern And we get windows users coming along as well various software requirements And we had some confidence there too because From the very beginning when we started running in the nectar research cloud The hbc team, you know, they already had a resource of a whole lot of Mixed and old hardware running on bare metal And at that point they started Spreading out onto our local cloud resource as well And so, you know, we already had a fair bit of confidence that that was actually going to work and be suitable for our workloads And so why not bare metal or ironic? Well, so sort of like i'm saying the performance for us was good enough So we didn't really feel like it was worth trying to learn how to do ironic as well when we already had this big file of kvm infrastructure and I mean i'm sort of basically the only open stack architect in the team and I haven't really gotten confident enough yet that with ironic you can achieve the Like the provisioning network isolation and that sort of thing to get secure multi-tenancy and and that That secure multi-tenancy is something that we're that we really are after because Whilst we tend to build these hbc facilities as something that's going to be a managed service at the end of the day for the user We still want their flexibility there to be able to to be able to hand a chunk off to a user if they really need it So and we're also worth mentioning that bare metal was one of the one of the big Topics that the science working group Folks identified as wanting more information about and some work on sorry. How are we doing time? So Now we've got like five minutes, have we is that yeah, okay Okay, so this is like a little basic diagram of how monarch is run on open stack Above the line Is open stack below the lines bare metal so luster is the only bare metal piece in there With nova network we solved the problem of integrating with luster there by simply using PCI pass-through So we we use malnox gear there their nicks Fortunately allow you to do some funky things with PCI virtual functions So you can do things like define virtual functions that are already tied to a vlan this sort of thing So then when a when an instance starts up on one of these nodes It's got whatever the nova network interface was so it has say a public ip or a private ip depending on how you set up That's provided by nova network in dhcp And then they actually go and configure their layer three services using the layer two device that we've given them So they set up their own private subnet Obviously so they can talk to luster as well Um, so that's been monarch has now been in production for six months Um, they started from scratch there. So it was entirely new cluster didn't bring the other users across So in six months there's 150 total users 50 active And they've done about 800 000 jobs in that time Uh, a number of different different types of workload And domains you can see probably probably resonates with people who have institutional facilities Um So some of the some of the issues with virtualized hpc. Um, I mean it's it's not all beer and skittles There are some points of confusion, I guess with regard to performance tuning and so forth CERN have been a big community player that have done a lot of work and shared really well in this space Um, and if you want to know like get into details about this stuff I'm not going to go into low level here because well one thing we don't have time and this is a beginner talk, but Really go and have a look at their blog um Hypervisor features are one of the issues I mean, there's a bunch of features that are great for general virtualization workloads that this is basically stuff that linux does So say kernel same page merging Can save your memory footprint, but it's not so good when you've got a hpc workload Linux natively has a new more auto balance Facility in it as well since about 3.8 um That's interesting because Livevert and kvm actually allow you to do some numer tuning as well So there's some potential for some interesting interaction there, which we're doing some testing on at the moment um huge pages is another one and um EPT is a feature that CERN mentioned in their blog and then recently They published some new information saying that when they had actually rolled out turning off EPT Based on micro benchmark results They realized that they had a problem To say the least because they're rolling out across a hypervisor fleet of about 160,000 cores. I think um So that's our benchmarks at the moment Uh, we're just using linpack and that is a micro benchmark So there's a big caveat on that But benchmarks are quite hard to do in the real world, right? And that's something that maybe I think the scientific working group might be able to help with in terms of common codes and and that sort of thing The other thing to To I guess know about is cpu capabilities that provides a really big boost If you're not passing through the host model of the cpu to the guest, then you're probably missing out on at least 10% performance And sometimes that means you're needing your cpu kvm as well For example, we were running on trusty, but trusty cpu kvm didn't know about Haswell yet. That sort of thing cpu pinning is another one that gets you another five plus percent And numer memory allocation policy I'll talk a little bit more about this here. So Here's some numbers that we got running on trusty. So this is a trusty hypervisor running ascentos 7 guest Because our hbc facility actually runs a sentos os at the moment On an adela 632 socket machine 2e5 2680 v3s So the bare metal performance up the top there. There's a couple of lines We did the bare metal on both sentos and trusty and you can see they're quite closely grouped Then The lines very close together up there are various kvm performances Very various kvm configurations rather and so you get 97 to 98 percent Which is pretty good those 86 percent numbers there are Configurations where we have no pinning or anything like that The only thing that's been done is passing the cpu host model through to the guest One interesting thing to note on that graph is that one of the best numbers there was actually obtained just using numerd Not specifying any strict cpu topology or mapping into the guest And that's quite neat because it means we didn't have to we you don't have to muck around too much with a big set of flavors To get all these different configurations. You just let numerd decide what to do And so we're now moving on to testing that in zennial because we'll be upgrading there quite soon I didn't include any results there yet because we've encountered some interesting issues that look like bugs For one thing numerd is now packaged in zennial, but libvert's not built with support for it So the other major thing I guess for hbc is is network io and SROV as I mentioned earlier with the way we integrated luster Solves that to a major extent um And co-processes co-processes gpg for use that sort of thing also sri ov Don't need to explain what single root io virtualization is hopefully but It's there if you need to look it up. There's plenty of information out there Just a final word on on how we manage cluster deployment. So, you know, we we're running a managed hbc Facility on the cloud. So this is not about giving users star cluster or something like this because At least in my experience We have maybe two people in our university that could go off and use that well for themselves And even then i'm not sure it's really the best use of their time We have a managed hbc facility with you know software specialists look after all of that stuff So it's probably a more efficient thing to do there So the guys that actually run that hbc facility gave me some notes Here so they use heat initially for cluster deployment Had had some rough edges with auto scaling and that sort of thing and also just frequent updates to the cluster at scale That might just be a maturity issue that will eventually See improves Slurm is really happy Running in this environment. That's one of the problems with things like sge and why people are I guess maybe why slurm is Becoming so popular now as well in this space And of course images aren't a substitute for configuration management And global file systems are quite hard obviously And the best ones or the most performant ones don't do encryption and then this sort of thing as well So they want a strong relationship with their infrastructure as a service provider, which is us And that was a quick tour of how we're doing hbc And those are our partners I guess questions got any time left for questions If anybody's got a burning question Take it outside On the pipeline development to like make it match your system like what sort of feedback loop do you have there? Um So we have I mean the the hbc Team sits just across the hallway from us. So they work directly with users. They have I mean, they're very focused on engagement actually And so generally if there are any issues that may be infrastructure related we hear about it pretty quickly But we typically don't need to get too involved in that stuff. No Usually hear about patterns and things that we might need to support going forward So you essentially um run all of your hpc workloads inside of your vm environment and only come out to to luster via your Backend networking Yeah, so we're actually we're actually not using infinity band. We're using ethernet. So we use rdma of ethernet One of the kind of maybe interesting architectural decisions that we made there Was not to build two separate fabrics for for this environment And instead build single resilient fabric. So all hosts are bonded and so forth In in the cluster that we're just finalizing the build off at the moment, which is a new part of the massive environment That's a hundred gig spectrum gear and you know, so we have multiple different speeds coming out of the guests and They can do npi over over that network as well as rdma to luster And we I mean we designed this thing So that our largest say npi job is the size of a rack switch pair Because we don't I mean that's already about Well over 1100 cores or so, which is well big enough for our users. Yeah Okay. Thank you guys


Hi everybody, Joe for jashby'scasebreaks.com coming at you with 2021 Panini Impeccable Football 3 box That's a full case pick your team number 6. This is a Saint Nick promo So if you bought a full spot Per the Saint Nick rules which you can see on jashby'scasebreaks.com if you bought a full spot You'll be eligible for that randomizer at the end There's the full case right there and here are the people who bought their spot straight up. Thank you We'll be randomizing your names later And the top two will be guaranteed a prize in our Saint Nick promo one of you I'm gonna get the grand prize Which is pretty nice details are on jashby'scasebreaks.com All right, there is the four team a random number block results right here, which we did in a separate video You guys unfortunately are not part of the randomizer at the end of this break But you're still part of a really nice break. So hopefully some nice hits for this group right here for those teams Traditionally it is Carl. I just haven't I personally haven't opened any yet. So let's let's fill that up So we can pop that open Nice box looks looks like Jaguars some Jaguars teal going on here. That is the That's the case hit that has the metal piece in there. We'll do that last I think there's one base card on the bottom. The rest should be hits. All right Good luck Away we go First off is 16 out of 75 DK Metcalf That'll be for the Seahawks David B with the Hawks of the sea Cam Newton 42 out of 50 Patriots Edition That's gonna go to Sean M and New England We've got Christian Barmore 45 out of 49 more for the Pats Sean M Gardner Minshew 5 out of 35 Jaguars edition indelible ink auto Goes to Sean M and Jacksonville We got Tiki barber on card autograph indelible ink 25 out of 35 Sometimes when I'm getting ready for work. I can catch a little bit of Tiki and Tierney New York Sports Talk radio show, which is not not too bad David B with the New York football Giants Next up is rookie autograph Micah Parsons 3 out of 99 That's for the Dallas number block Dallas doing a little bit of a ding in the bottom right That corner lifting a little bit, which is unfortunate, but That'll go to Dallas 3 Jeff Hen and the last one here is Devonta Smith nice patch nice auto 22 out of 25 and That'll be for the Eagles the Eagles were a number block team. So that it goes to Eagles to Mark Rao with Eagles to nice first box in the books Next box the blank cars Me to do lawn our shipping team uses them mostly, but I like to keep them around doodle for extra glue on that part There we go Is that a play thing? I saw a plate in there. I see two redemptions in here. They got two redemptions The plate what's going on here? All right, I don't know who that was on the bottom that looked important Let's see. Maybe I just overhyped myself. We'll find out 70 out of 75 Michael Vic Falcons that's gonna be for Brody the ATL We got Josh Allen 44 out of 50 quarterback Josh Allen Buffalo David B with the Buffalo Bills The plate is a one-of-one Adam feeling Feeling good Minnesota Jerry and the Vikings were on TV right now Has is stealing in the game. What has he done in the game? Thought he might have been banged up a little bit Let's see what he's doing box score Adam feeling No, no no targets yet. Is he injured? I thought he was injured. Maybe I'm wrong. I don't know anyway Nice Adam feeling one-of-one printing plate and all aboard the big-head Express Feelings out just Jared. All right, that's why that's why I thought I heard that somewhere These plates are actually a nice spot to get to get autographed. I feel it We got quitty pay 22 out of 60 for the Colts red foil autograph Kurt with the Colts We got more Vikings. We got indelible ink Robert Smith Two out of ten Big Robert Smith another one for Jerry and Minnesota We're up seven nothing already and in the red zone again All right two redemptions. I feel like that's Probably it might be a mistake. It's a bank error in our favor first one is Rondale more elegance rookie dual NFL logo autos. That's a one-of-one, right? It's got to be It's got to be going to cardboard connection com checklist We're going to elegance We're going to elegance rookie helmet and patch dual NFL logo It's a one of One for the Arizona football Cardinals Nick Nick L with the Arizona football Cardinals and All aboard the Big Head Express That's nice No, it's just for those four teams Adam. I feel like Rondale more Definitely has some upside. I think he Definitely has some upside and now that Deandre Hopkins being out For the remainder of the regular season and probably through the playoffs It's my this guy might see his stock increase. This could be a bonus Redemption and it's gonna be Elegance rookie helmet and nameplate auto Josh Palmer I think he's a ram Charger sorry different Los Angeles team and the helmet and nameplate is out of 35 That's pretty nice Rams that'll be for Terry and the Rams and a free top loader for both of you for both of you Nick and for Terry, sorry. I'm losing my mind here For Sean that is chargers My apologies Terry. I meant chargers Sean Matic and the chargers There you go. Yes, Tyler. I did the train whistle for Nick Did I not am I I'm losing my mind or is Tyler lagging? I'm looking at the I'm rewinding the tape. There's my face There's the there's the thing ding ding All aboard the Big Express and I do the train whistle right there boom Tyler's lagging someone tell Tyler to hit the live button Derek Henry Wow One out of ten Little bit of a issue on the edge right there, but Derek Henry out of ten autograph Yeah, I can't I'm definitely not gonna do it twice Jared. I don't want to cancel the first one Titans Patrick Davis there you go Patrick and the one down here is a buccaneer. It's Kyle Trask Look at that Three out of 15 Helmet and glove I want to say does this fit into a 180 top loader. I think it does three out of 15 Kyle Trask Sean Matic buccaneers Could look good if you marinate behind Brady That's what some people have argued have marinated behind Tom Brady for a for a couple seasons or so However, Tom have a long Tom Brady wants to play and then emerges Kyle Trask perhaps Kyle Trask may be taking over for Brady after that performance last night. Yeah, Tom Brady's done, right? Redemption on the bottom 64 is 75 Barry Sanders Detroit that'll be for Jared Cooper Cup 43 out of 50 That'll be for Terry and the Rams 8 out of 10 Ryan Tannehill Patrick and the Titans and Eric Stokes 56 out of 60 remember I don't think any real any relation remember I think JJ Stokes Guys remember him Hans with the Green Bay Packers and we've got 35 out of 35 Jacob Harris Dual relic and autograph for the Rams. There's your Ram Terry first of many Jared Kay Still got a few left. I hope But we got Terry on the board with a ram Got a few more to go here. There's Josh shaking for my Raiders Indelible ink on card autograph one out of 25 Raiders pulling off the win in Cleveland that's for Chris who has my Raiders We got Thurman Thomas for the Bills nice indelible ink That is six out of 25 David B and Buffalo Buffalo It's a really good-looking cards here and the redemption is Gonna be is gonna be Justin Fields Rookie patch autos gold. What is the gold number two boys and girls? I do have the checklist still open gold is out of ten He made a nice pass right here. Let's go Get some points on the board and the Bears are a number block team So that goes to Adam who has number zero And Adam even more importantly Adam Justin Fields is okay more importantly free top-loader. All right now. Let's see what's in here silver But it's a silver dangerous Russell Wilson nice 15 out of 20 and some fine fine silver That is fine That'll be for David B and the Seattle Seahawks With the Russell Wilson here. This is what the back looks like in case you're wondering It's got some copy back there as well, and it's awesome We'll put that into that slider box right there as well. What a break ladies and gentlemen We've got another case of impeccable in the store. Check it out. Jasper's case brace calm Now let's flip back to this screen here and let's see who's gonna win those those two st. Nick spots So let's actually copy all the names Here the number block spots don't count There are the four right there. Let's gather everybody's names new list new dice and Let's clear out the the blank spots here All right, so slightly better odds For this st. Nick promo. Let's roll it randomize that list five and a four nine times top two after nine Your winners. Good luck one two three four five six seven eight And good luck ninth and final time top two after nine There's nine There you go five and four. There's nine and nine now a lot of sad faces here But we do have some more opportunities you to get into that promo the saddest face I hate this part Jeremy very close no cigar, but I appreciate you try and appreciate you getting in. Thanks everybody for giving this shot top two You're in the st. Nick promo randomize you're guaranteed a random something that random something could be $12,000 a break credit prize list on Jasper's case breaks calm. Congrats to Sean Maddock and Jared Kay Congrats to you. You are automatically in the promo. You're guaranteed something a random something, but you're guaranteed a prize Thanks for joining the break. Thanks for getting to st. Nick promo. Congrats for getting into the st. Nick promo I'm Joe for Jasper's case breaks calm, and I'll see you next time for the next break. Bye. Bye


Hi guys, my name is Amanda Chang and I'm going to talk quickly about what I've learned about life through teaching adults to code. So the other day I was going through some old blog posts and I found this one from that I wrote when I was 23, which contrary to popular belief was three years ago, not five years in the future. And at this time I was teaching at a coding boot camp, which I am a big proponent of coding boot camps. And I think in order to understand why these lessons were so important to me, I'm going to take a tangent and or go on a tangent and talk about what I was doing before and then come back to these lessons, which I'm sure you guys are all anxiously awaiting. So unlike many of you guys, I was not a computer science major. I was a theater major, which is close. That blob on the right is me. It's a really low quality photo. And after college, I pursued lighting design for theater. So my first job was working at a summer camp. And the director of the camp every year had some counselor who for no particular reason she just didn't like and made their life very difficult. Luckily for me, that was me. I'm still not sure why she didn't like me. I think it had something to do with unrealistic expectations on her end. But five weeks in, I woke up after just being completely exhausted, having pulled some all-nighters, and realized I couldn't do another seven weeks. And I had to leave. So I told the director of the camp that I was leaving. And she said something to me that I will never forget. She said, I want you to know that I think you will never have a career. Because if you're the type of person who leaves when things get hard, nobody will ever want to work with you. Which is a really hard thing to hear as a 22-year-old from a 40-year-old. So next, I went down to Florida for an internship. And five weeks in, I got fired. So yeah, it was a great time. I didn't work a lot that next year. I was freelancing. And I started to believe a little bit that I actually wasn't going to have that career. Until one day, I woke up and something had to change. I read an article about coding boot camps. Enter the Flatiron School in New York City, which some of you may have heard of. At that time, I had a year of college computer science under my belt. I had started college as a computer science major. But I had no idea how to use that practically. None of it had stuck. And for the first time, I really had the opportunity to challenge myself intellectually again. I learned that code is creative. And I drank the Flatiron School Kool-Aid 100% and ended up teaching there after I graduated, which takes us back to the article. So what did I learn about life through teaching adults to code? First of all, I learned that being a beginner takes courage. I taught almost 100 students in a range of people who left their jobs. And every day was a reminder that the best things in life come from hard work and struggle. If you're not struggling, you're actually not learning. But there was another thing, and there's another thing that is really great for your mental health about being a beginner. And that's that this idea of being good. We really like being good as adults. But when we're a beginner, we don't have to think about being good because as a beginner, nobody is good. And also, nobody is bad, right? When you start something, you can't just say, like, oh, I took my first dance class and I'm really bad at dance. No, you took your first dance class and you are a beginner at dance. You have not had the time to figure out whether you are good or bad yet. And realizing this allowed me to start playing Ultimate Frisbee after I started teaching. So outside of code as well, that mindset allowed me to go and do something that I was not good at. And let me tell you, I was terrible. There is a picture of me there dropping a disc. And I've been playing for like two and a half years now, and I'm still not good. But it was that beginner period that made me realize that, despite not being very good at it, it's something that I love to do. So I really encourage taking advantage of that beginner mindset. The next thing I learned about life is that a positive or negative attitude is contagious. So I have a little anecdote from my time teaching, which is that I had a student named Seiji. And you guys have heard of Project Euler? Yeah, raise your hand if you've heard of Project Euler. OK, for those of you who haven't, for those of you who haven't, then Seiji set up a club called Club Euler to meet at 8.30 every morning to do puzzles. So not only were they learning from 9 to 6, they were also meeting half an hour early. Most of the class chose to attend it twice a week because he was so positive about it. It works negatively as well. In the theater, you work with a lot of jaded people, and the cycle just continues. How this applies to working in development, at my current job, I'm lucky to not be stressed out a lot of the time. But one week was just a really hard week. I was on call the same week as doing feature work. And one of my coworkers came in and offered to take my on-call shift from me. And I was like, you're the best person ever. This is great. And a few weeks later, he needed me to work late to get to deploy out. And it was easy to agree to do that because he did something positive for me. And the last lesson here is that there's always more to learn. When I was working in theater, a more experienced designer gave me some advice, which is to be a sponge. And in development, you can learn anything. You don't need anybody else to be there, right? In theater, I couldn't make a new theater unless I had a team, unless I got hired. In development, you can learn a new language just from your computer whenever you want. I recently started playing with processing. It's really fun. I can make the bunny move from the bottom of the screen to the top of the screen. And it makes me feel really accomplished. So in conclusion, this is a quote from the original blog post from 2014. All in all, I'm thrilled that my first full-time job demonstrates how important it is to strive for happiness, your own, and that of the people around you. So everything that I said today, these are all things that I knew. None of these are big life lessons, where I was like, this is crazy. I was so much wiser three years ago. But it was a good reminder for me, and I hope you all enjoyed it. I'm Dave Rupert. You might remember me from the internet. I am here to tell you. Oh, she just had slides here. So I made a slide deck in PowerPoint, and it's called, Hey, did you know Ruby kind of actually works on Windows now? Yeah. You maybe didn't know that, unless you're Yuhuda Cats. I wanted to tell you a little bit of the story. I do a podcast with Chris Coyer from CSS Tricks. Who likes CSS? Not, wow. OK, not many hands. That's actually really surprising. I usually hang out in the CSS crowd and y'all are different. So do a podcast about front-end web design and development. And we were looking at our stats for this podcast. It's like 16,000 listeners. And I went to the website, did the Google Analytics, and I was like, who does what? And I was surprised to see the demographic between Windows and Mac was 50-50. And I was just like, oh, wow, that's unexpected, because when I come to things like this, Macintosh, like everywhere, just a sea of glowing apples. And that's OK. That's fine. But we're an advice podcast, which isn't, I don't know, advice. Anyway, those are so dangerous, especially with two-wide dudes. So we're an advice podcast, but people would be like, right in and be like, I want to, how do I do this? My designers want me to do this thing in Sketch. And our advice was always kind of like, well, buy a Mac. And that's good advice. It's good business advice, probably, if you're doing a lot of Sketch work. But it's bad advice if, I don't know, you live in a country where that is 12 months of working to save up $3,000 for an aluminum laptop when you can get a Windows laptop for $200. Anyway, so I did a stunt on the podcast where I switched to Windows for a year. And it was like, whoa, what did I get myself into? Ray Bingo from Microsoft sent me out a laptop, a Surface. And he was like, here, try this out for a whole year. And I was like, all right, let's go. And I install, I got it. I install, set it up. And then I was like, doing a website and Ruby Rails project. And I went to do the Rails project and nothing. Didn't work at all. The Noko Geary gem had been broken since January. And it was like September. And in fact, one guy in Germany patched it, but no one merged the PR. Because no one had a Windows machine. Yikes.   And you're like, ah, that's probably why. That was my great DHH impression. Is he still around? I don't know. All right. So it was really bad. And I even got on Skype calls with Scott Hanselman. He's a very popular .NET open source developer. And we just sat there and gem-installed things and watched it break for two hours. We were just like, gem-installed this.  All right, let's try it again and compile the MRI ourselves and stuff like that. And it just didn't work. And then three, fourish months later, I'm not saying it's because of me, per se. But Microsoft made a very exciting announcement that they are now offering Linux, a Linux subsystem on Windows. Has anyone played with this? Is this? All right, yes. OK, it's very exciting. And at first you're like, yeah, that's fake, right? Like, there's a Linux on the Windows. And it's true. They actually hired Canonical, who's like a they make Ubuntu. And Canonical came in and somehow patched this system into native window functions and things like that. And it works. And I use it every day. And it's awesome. And I'm here to show you how that kind of works. Is that OK? You guys want to see how it works? All right, one minute. Holy god, let's go. So you go to the Microsoft Store. And then you type Ubuntu. OK, no one knows how to spell it.  You can get the app. And then you just install whatever flavor of Linux you want. And then you get an app on your thing. And then you type bash. And then you get bash. And then it runs. And now I have a bash prompt. And you can do anything you do on your Mac or on your Linux machine inside this window. All right, great. Hi, I'm Jordan. Can you see this? Can you see this thing up on here? This arcane syntax on the top, on the left side of the screen. Yes? Great. OK, how many of you in here are Rails developers? Makes kind of sense. How many of you here do front end development at all? How many do React, Redux, cool stuff? How many love ES6, ES7, Babble, Webpack, whatever, whatever, whatever? So JavaScript, yeah. For those of you who don't do that, I recently started doing it maybe like six, seven months ago. And I'll say that the JavaScript ecosystem is great. It's very enthusiastic. It's fast-paced. And I'll say that about the JavaScript ecosystem. But of course, everything changes really quickly. And if you're not on React, 0.15, or is it version 15? I don't know. If you're not on React, 0.15, you have to be on 0.16. And PropTypes has to be moved out of the pack. It's all very difficult to keep up with. And I find it really difficult myself because I come from the Ruby world. I actually come from the Perl world where things move even slower. But in Ruby, you can just say gem install, whatever. Rails is pretty stable. Rails has a lot of convention. And Rails is easy for the easy stuff. The hard stuff is still hard, but the easy stuff is really easy. And JavaScript is not the case. So I went running away from JavaScript. And I found a programming language called Elm. Brad, is that your name? You talked about it a little bit. It's a cool language. And I don't pretend to know a lot about it, but I like it a lot. How many have heard of it? Show of hands? Oh, wow. So next year at ElixirCon for something, you're going to go to all the Elm talks. What is Elm? Elm is a functional programming language that compiles to the browser environment of JavaScript. It doesn't do the server-side stuff yet. And it's designed to replace everything that you do on the front end. It will replace everything you do on the front end. And it's very cool. So it's a functional language. So you have purity, meaning side effects are data. And all of your functions have inputs and outputs and no side effects, like console logging. It's not a thing you can do it. But you don't do it as console logging in Elm. And it went away. It's going to come back. OK. Wallet's coming back. One of the great things about Elm is that it's a programming language, yes, but it's also this whole design pattern as well that ships with the language. And you can't really choose to not use that design pattern to write your applications. And if you ever use React and Redux, it will feel very familiar to you because React and Redux took a lot of their inspiration, especially Redux, from the Elm architecture. And that constraint helps a lot. But we know that when we design by constraint, the more constraints we have, the finer it gained our design in, the more concrete things are, and the easier it is to do certain things in those constraints. It turns out that Elm picks a bunch of really cool constraints to make it easier to do one thing, and that is write single page web applications. And that's it. So this is the basic version of an Elm program. The real version is not too different. But we have here, I've never one-handed vimmed before. We'll see how this works out. So we have three functions that make up an Elm application. The model, which is the state of the application, is kind of like the Redux store. The view, which is kind of maybe your React JSX. And the update, which is maybe your reducer, if you've ever heard of Redux reducers. And all the application is you start with a state. In this case, this is like the Hello World Elm app from the Elm documentation site. I'm not going to type, so it's good. Yeah, I don't do live coding. This is, it never works out well. So thank you, though. This is the Hello World application. It's a counter. And we can click it, and it goes up, and it goes down. And that's kind of it. So instead of having event handlers, like we would do in JavaScript, in Elm, we have, well, this is kind of, this is our view. This is like equivalent to writing JSX. Maybe I will type something. OK, so let's say I'm writing JavaScript instead. And to do that, I'm just going to open a multi-line Elm comment, because Elm format would do bad stuff if I didn't. OK, so let's say we want it to make div, and we put inside of it a button that's our click handler. And we would have some text for minus. And we have another div. Oh, I'm so sorry. I can definitely do that. That happens everywhere. We'll have another div, and we'll have whatever the model is. And we'll have another button here. Buttons have opening and closing tags, right? I think so. Yeah, that goes to show how great of a JavaScript developer I am. And you can point out mistakes to me, as I'm typing, if you'd like to. Like, I think I just switched increment and decrement. Increment, sure, that'll work. OK, so this is kind of the equivalent JSX you would write. And the decrement function would be some function that would take the model and just decrement the state, just like we're doing here. And the increment function would do the same thing for the plus. The cool part about Elm is that you get, so it goes, you start with the model. You start with the model. And in this case, the model starts out as being the number zero. And then you render a view, which is this tree of HTML. And inside this tree of HTML is a bunch of event handlers that can get dispatched to the Elm runtime. And when you click on either of these buttons, Elm will dispatch a message. You see that type message? And it will go into the magical Elm runtime. It'll handle all the side effects. And Elm will invoke the update function that you provided with the message itself. In this case, if we click decrement, it'll pass in decrement to that lowercase m message. And model will be, well, the current state is zero. Well, the current state here is negative 3, but the current state is zero. And when I say decrement, it will invoke update with decrement and zero. And then we go into this case statement and we pattern match on decrement. And then we return a new version of the model. We don't mutate the model. We return a new version of it because in functional programming languages, you have immutable data. And it just returns the model, whatever it was, subtracted one from it. And then that gets invoked with your view function, or your view function is invoked with that new model again, and you get your new state. So it's all one directional. Of course, we've gone from the Polymer 1 and Angular 1 land of two-way data binding, and everyone realized that one-way data binding was better. But anyway, that's an overview of Elm. It's great. Elm-ling.org. That's it. Thank you. Thank you. Hey, so my name is Nick, and I like to give disaster talks. So this, of course, is one of those. I'm going to tell you about Cockroft's Folly, which is my favorite British nuclear disaster because it's the only one, really. So after World War II, this guy, Sir Winston Churchill, decided that the UK needed to be a nuclear power. They needed a nuclear weapon to remain relevant on the stage of World Affairs. And the United States was only willing to share nuclear technology with nations that had already developed a bomb on their own. The reason for this is the US wanted to prevent proliferation. You see how well that's worked out. Despite British scientists being part of the Manhattan Project and actually working to develop a nuclear weapon in the United States, the US still wouldn't share intelligence with them. So Churchill and other people in the British government gathered British scientists together who had been part of the Manhattan Project and asked them to build a bomb. Well, to build a nuclear weapon, you needed fizzle material. And so they decided to skip uranium and go straight to plutonium. And in order to get plutonium, they had to build a nuclear reactor. So their scientists, having been exposed to the Hanford B nuclear reactor in Hanford, Washington, or in Richland, Washington, excuse me, decided to build a reactor based on that. And that reactor is actually one that produced a lot of the plutonium the US used during the Manhattan Project. There's one key difference, though. Hanford B was a water-cooled reactor. Now the challenge with that is if you lost electric power, you lost your water cooling, and the reactor explodes. Well, Hanford B had a 30-mile evacuation zone around it. The UK didn't have that kind of space. They're a tiny island. They don't have that much room to build a nuclear reactor. So they decided that they needed to make their reactor passively safe, something that would work even if the power failed. And so they built an air-cooled nuclear reactor. Seems like a great idea, right? You can see lots of little holes in the picture. That's actually where they would put nuclear fuel into the face of the reactor. They would load it with uranium. And the way it worked is you would put these canisters in the face, push it through the core over a period of time, like a month, two months. And as these fuel cylinders passed through the core, they would become more and more a higher and higher percentage of plutonium. Eventually, they'd get pushed off the back of the reactor in this channel of water and flow out the other end to a plant that would extract the plutonium out of them and send it on into the weapons program. And to cool the reactor, there was air forced through it by these big fans. And if the big fans failed, the genius of this design, at least in the scientist eyes, is that it would still cool itself by convection. There would be hot air still rising up this chimney that would pull air into the reactor and keep it cool. There is a slight problem with that, though. Terrence Price, one of the physicists on the project, theorized that a fuel canister could theoretically fall out the back face of this reactor, crack open, and release all sorts of nasty stuff into the atmosphere. And if that happened, it would pollute a large portion of the British countryside, along with the Irish Sea. So he brought this up in a planning meeting and said, we should really do something about this. We should put a filter at the top of our chimney. But the general consensus was, well, this is not really that a real risk. We're not going to miss the channel that often. We don't really need a filter. And what's more, if we try to do this, it's so horrendously expensive that we can't afford to build this reactor. And that's where they left it. It was considered so expensive it didn't even get recorded in the notes from the meeting that he brought it up in. It was so unrealistic. And that's where things stood until this gentleman, Sir John Cockcroft, the director of the program, heard about the situation. Now, he fully understood the risks that Terrence Price raised. And he personally insisted that they install a high performance filter at the top of their chimney. And those filters became known throughout the project as Cockcroft's folly, because everybody knew they weren't going to need these filters. That's foreshadowing. Now, the interesting thing about this reactor is it used graphite as a moderator. Now, when I say moderator, the way nuclear chain reactions work is they throw neutrons around. And neutrons fly into other uranium atoms. And that causes more neutrons to be released. And it's a self-sustaining cycle that releases heat. Well, the problem is those neutrons fly off so fast that unless you slow them down, they're not going to hit anything. They're just going to fly off into space and not cause a chain reaction. So you layer the uranium in there with graphite, which slows the neutrons down. And that allows the chain reaction to sustain itself. There's one problem with using graphite as a moderator, though. When you bombard it with neutrons over a long period of time, eventually the crystalline structure of graphite gets all out of whack. And it builds up what's called Wigner energy. Wigner energy is huge potential energy that will eventually release itself as a burst of heat. Well, the way that you combat this in a nuclear reactor is you have to heat the graphite up enough that it becomes plastic. And this crystalline structure will snap back into place. And so they had done this several times. It was a routine part of operating this particular reactor. So on October 7, 1957, when they noticed that the reactor about six years in was running hotter than they expected it to, it was just a sign that there was Wigner energy built up. And so they needed to do an annealing cycle to get the graphite to snap back into its lattice structure. As they heated the pile, though, they noticed that the temperature of the pile began falling everywhere, except for fuel channel 2053, not the even heating that they would have expected during an annealing cycle. So at the end of the cycle, once the reactor cooled back off, they came to the conclusion that, oh, well, the reactor hasn't actually annealed, we need to do another annealing cycle. And so they started to back up. This time, the temperature rose across the pile exactly as they expected, but then at the end of the annealing cycle, the temperature kept on rising. Well, they needed to cool the core down, so they turned the ventilation fans up to full and started blowing as much air through this reactor as they could. Well, about that time, the radiation alarms in the chimney started going off. The team assumed it was just a burst fuel cartridge, no big deal, had happened before. They tried to scan the core of the reactor with a remote probe, but it was stuck. So Tom Hughes, the assistant reactor operator, convinced the team that they needed to go to the reactor face and pull out an observation port and look and see what was going on. To his horror, the fuel inside was glowing bright cherry red. So at this time, Tom Toohey, the director of the reactor, climbs up to the top of the pile, looks over the back, and can clearly see fire coming out the back of the reactor core, not a good situation. It turned out that the anomalous heating that they saw in fuel channel 2053 wasn't annealing after all, it was a burst fuel cartridge that had caught on fire and was burning hot enough to ignite the normally-inflammable graphite moderator. It turns out when they had turned up the fan to cool down the core, all they had done was fed this fire and allowed it to really catch. It was burning really good at this point. And so they had to try to figure out how to get this fire out. Luckily for them, there was a shipment of liquid carbon dioxide for a gas-cooled reactor on site. They tried to pump the carbon dioxide into the reactor core, no fact. They attempted to use water, which is a really terrible idea on a nuclear reactor, because when it's burning that hot, the fire actually strips the oxygen out of the water and you run the risk of a hydrogen explosion. That still didn't get the fire put out. So finally, after the core had been burning literally for four days, they evacuated everybody from the site, except for the fire chief and the site manager, and they turn off these big fans. They turn off the only means they have of cooling up down this reactor core. Slowly but surely, the core temperature begins to drop. They go out to the reactor face and try to pull the viewport out, and they can't, because the fire is trying to get oxygen from wherever it can, so it's sucking that viewport seal in tightly. They finally started decommissioning this reactor last summer. This is one of the fuel cartridges, and you can see that telltale yellow at the top. That is uranium oxide. So there were fuel cells like this throughout the reactor that are bursting. Ruptured, melted, all the way through the core. Had it not been for John Kotcroft and his folly, the stuff that burned out of those fuel canisters would have been scattered throughout the English countryside. Instead, it's all entombed inside this reactor. It was so toxic, they literally let it sit 60 years before they started trying to clean it up. Building software, especially something brand new, is a lot like how these early nuclear reactors were built. They needed plutonium and they needed it now, just like you need to ship software and you need to ship software right now. I've noticed in my time in software that software engineers fall into two buckets, pragmatists and idealists. The pragmatists are wired to get the job done. They're almost always comfortable taking on technical debt to get the job done faster and get working software out the door. Idealists, on the other hand, want to build properly engineered systems. They're the ones that will fight for more time to build it right. And guess what? They're both right. Every team needs a mix of idealists and pragmatists. Had the windscale team not had a couple of idealists in Terence Price and John Kotcroft, the reactor would have gone online without a filter at the top of the chimney and it would have radiated a big chunk of the British countryside. The rest of the team was of a pragmatic bent. Completely ignoring Terence Price's concerns is too expensive to solve and just trying to get the reactor online, which they did. They produced plutonium about a year after they went live. The trick to getting this balance is to make deliberate choices together as a team and you can't do this unless you have both idealists and pragmatists on your team and you have these discussions on a regular basis. So learn to make the deliberate choices as a team. Find the balance between idealism and pragmatism and write great software. Thanks.


An Indonesian man who was having a lot of death and tried to escape from it. He decided to fake his own death but was viral on social media when he was captured waking up inside his open casket. The man was found by one of the mourners as he lay in the coffin but suddenly people were all struck as he appeared to wake from the dead. The man and his wife paid a van with a casket telling the driver they need to pick up a body of a deceased family member. The driver said the couple looked in good health when they entered the van. The couple asked for a brief stop at a highway resting area during which the husband jumped into the casket. The driver noticed that the husband was gone when they resumed their trip on the way to a clinic with the wife, presumably to help the man, pronounced dead. The man was found waking up, not realizing what the chaos of his actions would cause. The Pennsylvania couple accused of faking the birth and death of their baby to scam their family and friends into giving them more than $600 USD in donations and gifts. Casey and Joffre Land were both charged with theft by deception. Casey documented her fake pregnancy on Facebook, posting her growing baby bomb and revealed she and her husband were having a boy. Friends hosted a baby shower for the couple and they were given a number of gifts before Casey claimed she needed to be in bed rest for the final two months of her pregnancy. The couple revealed to family and friends that their son, Easton Walt Lang, had been born and they even posted the photo on Facebook of the baby. But Casey and Joffre revealed soon after that their baby boy had tragically died in the hours after the birth due to respiratory distress syndrome. The couple then created a GoFundMe page to raise funds for the son's funeral and a memorial service was held after the couple said they had committed their son. But one of Casey's friends was suspicious of their story and called the funeral home. When she was told there was no account matching the name of Easton Lang, she contacted police. The police investigation revealed the photos that were posted online were not of a dead child. The baby and the photos matched the appearance of a newborn lookalike doll. This husband, Joffre Lang, then started to shout out on Facebook saying, we didn't fake anything and that multiple people have seen my wife pregnant and grow old into nine months. If the cops were smart, they would look at the security cameras at the hospital to show we were there. But police found no record of Casey Lang or Easton Lang at the hospital, coroner's office or memorial or even in the OBGYN clinic, pleaded guilty to stealing £40,000 from his elderly neighbor and pretending to be in a coma for two years to avoid charges. Night was living on benefits at his home in Swansea, South Wales after claiming he had suffered a massive neck injury. His wife Helen claimed she had to care for her husband who had snapped his neck after falling backwards as he pulled down a garage door. But the whole time he was carrying out an elaborate fraud. He was spotted walking to shop. Night, picture arriving at court, finally admitted 19 charges of thief and forgery and has now been jailed. An Indonesian woman named Maya Gunawan shared the horrors she experienced online to a person who she believed was a friend in need of her health. The incident happened when she met the woman named Lisa in a Facebook group that gathered and pulled money together to help each other. Lisa asked to borrow an amount of $300 from her. Maya never met Lisa in person so she went to her Facebook profile and they didn't have any suspicion about her background that it seems she is a good person with good friends and relatives. Maya and Lisa's daughter even became friends so without any doubt she was convinced giving her money to a stranger confidently believed she will give them back. Mind passed, Maya was excited to get her money back as the time Lisa was promised to pay. But things getting unclear when Lisa asked her to extend the due since she don't have any amount to give her yet. Maya was convinced again and asked her to pay the next month Lisa agreed and have a promising statement. The next month Maya logged into her Facebook and watched her act to discover Lisa's daughter's pose. That Lisa had died in an accident happened on a bridge near her home and that her burial will be in the province of Asi. Picture of her corpse was wrapped in a sheet together with a fold over body bag being weld on the hospital that appears to have been taken from a TV show. Here no stuff with tissues making it even more convincing. Learning that it seemed there's no way to get her money back, Maya was initially sad to learn of Lisa's untimely death. However, her suspicions arose when she read that Lisa's burial will be in Asi which was distanced away from where she lived. In her use, she inspected the photos of deceased Lisa closer and realized they didn't resemble dad of a corpse. Her suspicions were confirmed when she recalled the image of a trolley wielding a body. She then confronted the daughter of Lisa. The girl denied participating the wrong date of her mother.  Speaking with the local media, Maya Gunawan said that she's waiting for Lisa to pay back her money and has not gone to the police. She added that she is out of reach. Netizens are furious at a Thai man and his wife after the fake his own death on Facebook in a bid to scan family members for non-existing funeral costs.  The wife captioned the post, Love you, she wrote while telling concerned friends that her husband died of both cancer and asthma. When people began asking why he had not previously showed signs of wellness, she replied he pretended he was okay all along. She didn't call her husband's mother, who lives in Lampang Province, demanding a cash. The mother-in-law sent right away an amount of 600 US dollar to pay for a coffin and vehicle to take her son's body back to his hometown. The family began making funeral arrangements in preparation for the arrival of the body. However, it never arrived, they decided to call the dead man's phone. Surprisingly, someone answered but quickly hung up. The family raised suspicion because the voice sounds familiar. The family had to cancel the funeral service after paying an allegedly unrefundable 60,000 Thai baht or 1,800 US dollar. Although most of the family was furious, the mother didn't hold a grudge towards her son. However, the couple's friends were less forgiving, pointing out the man's alleged long history of lying and deceit. A Honduran man working in the United States, pretended to be dead so his wife back home would stop asking him for money. Danny Gonzalez took photos of himself with cotton wool stuffed into his nostrils and a white sheet of raised body as if he were lying in a mort. He then sent them to his wife of two years living in Sabah, Honduras, along with a picture of a coffin in the funeral parlor and a message telling her he died from cancer. However, the scheme backfired after local media in his hometown started to report his sudden death and the news reached his shock friends and elderly parents. But it didn't take relatives long to realize Gonzalez appeared to be grinning in one of his photos. Others noticed that he appeared to be lying in double bed and the white sheet of raised body was actually a pillow cover. When local media found him alive, he admitted the hoax was a ploy to make his wife believe he passed away. He told the news media that his wife would call every week just to us to send more money. That every Saturday she would call telling him he should send money. In fact, he had sent her so much already, but the wife insisted for more. He added that the rest of the week, not even a message, his wife would never send photos or ask him anything else. One time his wife called him that the money he sent was stolen and he must send more. But a relative told the media that the news of his death had been a terrible blow for his parents. Other family members slammed him as a grateful son, criticized Gonzalez, who had been working in the US for years.


The FACO-NIRU-HEA catalyst was found to be highly efficient at both HER and OER, while maintaining long-term stability. This was due to the formation of a spinel oxide layer which preserved the active sites inherited from the HEA's intrinsic structure. This work provides a pathway for the design and manufacture of other metallic electro-catalysts, as well as a benchmark for assessing the efficiency-stability relationship. This article was authored by Kong Wang, Zhou Yanxia, Yulu, and others.


Today we're conducting a rail exercise to head back to Camp Lejeune. It's for retrograde purposes to get our equipment from WTI-216 back home. Combat with just battalion doesn't normally conduct rail back from Yuma. This is the first time they've done it in about a decade. Normally we would go back and track their trailer, but what we've done here today is save 2,500 approximately $170,000 in transportation costs. The personnel that are needed to conduct this are mainly landing support Marines, 0481s, embarkation Marines, 0431s, motor T operators, heavy equipment operators, and using an embarkation officer and an 0402 logistics officer. You have the motor T drivers obviously so they can drive the vehicles up onto the deck. You have the AT operators in case you need them. We'll have a crane here later today that will crane off some of the containers that we mobile loaded to put onto the appropriate cars.