What's good y'all Chris from jasseskatesbreaks.com doing our six box pick skin football mixer random team number two So we got a few randomizers to do first off near the boxes some fun stuff in here 2022 spectrum 2021 one football 2021 mosaic hobby 2021 playbook 2022 Phoenix and 2022 Xenia football So our first randomizer we're gonna be giving away two spots to the people who bought a full spot Which would be this dice and this randomizer chat with the last spot mojo Nicole up there at the tippy tippy top We're gonna do this dice first and then after that we'll do our fresh dice with all 32 of our names To go with our 32 teams, and then we'll do the break itself All right, so it's rolled this one for the two free full spots. Good luck everyone. Thanks again for getting it Five and one six times. So one two three four five and six six then final time Top two only get those free spots still in the break obviously, but David and Kyle David and Kyle getting in those two free full spots So if you got the arrow character Next to your name, you mean you won those spots in that giveaway, but now let's grab all 32 Of our teams right here So there's one filler with the mosaic to Kyle and David with the filler or the free full spots And then our 30 to full names with our full slots. All right Fresh dice to go with our teams. Good luck. This dice roll one five six times six time once again Good luck everyone one two three four five and six six then final time Right there So Thomas down to Tristan and six times for our teams. Good luck one two three four five and six six then final time boom Gonna be the Buffalo Bills down to the Atlanta Falcons. Let's grab our friends here So it's our first half right here Thomas with the Bills Raymond with the 49ers Steve with the Jets Aaron with the Texans Chris T with the Raiders Mark with the Cardinals Chad C with the Dolphins Nicole with the Ravens Raymond with the Bengals Stephen with the Bucks Chris with the Giants Joseph with the Saints Connor with the Chiefs Kyle with that free spot.  All right Let's do it I'm gonna do a little trade chatter here to see if there's any discussion if if not, I'll let you know But we're gonna get to Breaksville right after six box football mixer be right back All right, so we're back. No trade chatter. So we're just gonna rock and roll a couple things booked up after this So let's just get right to it. No better. No better time than the present Hey, Jaspie's six box pigskin football mixer random team to mark with the Cardinals All the way down To Nancy and the Commanders All right some fun stuff in here. Let's get some of the hobby stuff out of the way first Let's start with our most recent school with Phoenix football Also, I want to mention that we have four box case four box one-fourth case break of Phoenix on the site right now as a team random Given only two spots as well Yeah, it's on Fox Sports to yeah, but I don't know what channel that is for direct TV on Fox Sports one They're showing up show a NASCAR. They've got Marquette and butler on Fox got NASCAR showing for awesome I think the end of a race or something Just saying gotcha. Thank you, sir. I don't think they have them. They don't have the money for Then you know what? They want the kid from Doesn't even Robinson. I know he's small, but I like Bryce young or Bryce love All right, let's do it one box of 2022 Phoenix football to start us off Taekwondo and green Patriots Mark Russo 16 out of 250 I agree though. I thought that was such a good deal for the Bears Speaking of the Panthers there's Matt Corral purple contour rookie 65 out of 125 first auto gonna be Nick Chubb Monster season for the Cleveland Browns and Kyle from the free spots silver Nick Chubb auto Non-numbered Nice name right there as a first auto of the break in a silver Kenny Pickett All the Kenny Pickett's going to Joseph and the Steelers Tyler Lockett Lava purple trail on Berks for the Titans Eric Yuzunakwa easy E in the pink easy E go into the Miami Dolphins and Chad out of 199 trail on Berks purple go into the Tennessee Titans and Joseph K out of 125 And the Tyler Lockett Lava go into the Seattle Seahawks and Barry So we had a 175 5 out of 149 jumbo material Breece Hall New York Jets and Steve Herrick I still think the most likely spot for Rogers, right? Breaks can be pretty Pretty gross next year for sure. Absolutely They love Richardson though. Yeah, they're they're big on on Richardson the Panthers Marvin Laial Little non-numbered Garrett Wilson your offensive rookie of the year green hot routes One more for Steve 150 I agree. I think it's a big question mark another easy E in the red this time Jahan Dotson RPA rising rookies orange go into Nancy and the Commanders His bulging patch right there looks like maybe glove cleats 20 out of 99 for the Jahan Dotson approved lifts and cleats for some players How would they go about doing that like regulating it like it's got to be You know can't be too high can't be too this can't be too that like how would they do it? You're going to measure them every single game. It'd be kind of funny James Cook contours numbered trying to bride pink And a flamethrower was Carson Wentz the Trent McDuffie going to the Kansas City Chiefs Going to Connor I'm around a 199 And the James Cook numbered to 99 Buffalo Bills and Thomas solid first box warm mixer going though But let's uh, let's do the zenith It's a quick and easy one. Let's see what we got here I think Stroud is so raw. I think his potential is crazy though All right, he's going to be a project obviously. I don't know how many teams are going to be Too happy about getting a guy that's going to take a while to figure it out But if he ever figures out boy, is he going to be good All right, starting off with our z-team tire re-kill Miami Dolphins and Chad Coleman. It's gonna be non numbered five out of ten Matt Stafford class president lions edition Right there on the back Detroit Lions five out of ten Nice low number going to the Detroit Lions and john JJ Watt non numbered Tonya Gibson non numbered first hit quick Christian Watson 140 169 out of 299 three color patch and rookie auto Green Bay Packers going to Chris T 189 out of 299 Christian Watson RPA And the wild card points because we a randomizer going to someone at the end of our break We're going to some fun stuff. So go to 2021 mosaic hobby 2021 mosaic hobby Some very nice stuff in here. Some of these names come up so much Trevor Lawrence obviously took a huge leap Michael Parsons took a huge leap defensively. I mean that kid is a stud for the Dallas Cowboys It'll be exciting to see who takes that leap next year, which rookie gets even better I think that's the best thing about the draft some some players Are obviously going to go to some teams like you know There's no need a QB for some teams like for the Steelers like we got Kenny Pickett I have been not been paying attention to anyone but quarterbacks Defensive and offensive linemen You better G. Love. We got to send you like a a jazzy's hat You got to be got to have you rocking some stuff here for us Where Fitzgerald mosaic man of the year kind of gain. Well, Cadarius Tony silver blue chips first auto marquise colston mosaic auto non-numbered for the New Orleans Saint It's going to be joseph marquise colston non-numbered our first auto from this box Should go on the piece patch of my home's mosaic Every pick like oh Oh, just you know really play it up. That'd be fun Devontae Smith blue chips Devontae Smith mosaic on the NFL debut as a trey lance trey lance going to the Niners and Raymond Devontae Smith's both going to the Eagles and frank See a few years from now I'm gonna give you It's crazy. Oh, no, it it'll you know, sometimes it it makes mixers like this multi years sometimes it can Turn them into just fillers golf seem if you hoko Nice center stage Dan fouts Jamar chase rookie Jamar chase and the bangles going to Raymond At a Dak press Scott blue Going to the Dallas Cowboys going to David One that free spot Find a straight-up spot 32 out of 99 on the Dak press Scott People were like people weren't happy right? as a mac jones Swagger on the kenny golliday Travis etn junior rookie. He had a nice rookie season as well Like really like we don't know what we're talking about us fans You know, we could have drafted the next tom radion and feel like Oh, who is this and just the the outrage from armchair gms It's always funny. It's always great job job red So I'm gonna be ronald jones of the second I'm gonna go to Tampa Bay The buccaneers and steven kahr insane, right that that rams trade and then the uh That's seahawks trade the rust trade Might have just bowled them for a long time But you know at least for nice chivalrous blue chips rookie Center stage drew breeze is going to be numbered The blue center stage 97 out of 99 One more for the saints Alex Smith I was never hot on alex smith I thought he was a fine qb like there has to be like, you know Middle of the middle of the weed tier kind of qbs and he was like the perfect fit Like if you were better than alex smith like you were a good qb There's nothing wrong with that Cal pits rookie Blue chips conarius tony overdrive on the chris carson non-numbered mac jones nfl debut jane waddle working looking I don't know. I think the niners are so good right now They're like we able to pay everyone obviously and they've got some stuff to figure out a qb But I don't know seahawks are looking pretty good. They had a really nice season They used to be qb too One more for the cowboys dion sanders 22 out of 49 on the purple One more for david great rossos silverwork Unifold debut Center stage kurt warner Those are mosaic Let's do our playbook Exactly like and there's nothing wrong with that I mean They almost they don't make what the niners with alex Smith almost made a super bowl. They get our game away, right? Or where they are? I don't remember 2021 playbook for auto or memorabilia It's gonna be a fun one here potentially booklet one booklet per hot routes deontay johnson 18 little number match out of 49 two-color patch for the steelers and joseph dj going to the steelers hot routes ron dale morn another three color two colors. Excuse me 44 out of 149 arizona cardinals mar grueso See what the cardinals decided to do here. I don't think We're gonna have that front of a season this year On do more though Signature routes a lot of your more rpa two-color patch and rookie auto There it is right there on the side six out of 25 Elijah more two-color patch and auto All right, and then the booklet good luck y'all Jaylin waddle 37 out of 99 Nice booklet, you know, iammy dolphins chad colman Very nice out of heck of the season dolphins picked up that uh Another option for two of us. So if you should be back, we will see we will see if he's coming back or not All right, let's do our spectra and then we'll end with our one football 2022 spectra Eight hits Four autos four men's We can get here for the kid man. He is He was struggling last year Who would have thought offensive line very important to go our parallels out of the way. So first Jamar chase second year for the bangles 21 out of 25 nice low one there for Raymond Dallas Goddard 30 out of 60 Fly eagles fly go in a frank Mike Vrabel old school patriot 41 out of 99 One more from mark And our die cut this little wine green jaylin hertz eight out of 30 For your mvp runner up a little more here rookie spectra First That was jones jr. Chicago bears and something 42 out of 50 first up monumental memorabilia two color patch Damian pierce Houston texans Going to erin. Oh nice here four out of four. Who we have jones buccaneers edition on the auto Nice little number there for steven four out of four Very very nice Johnson joe borough silver jameson williams rookie first up max impact joe borough One more for the bangles and raman Nice one coming up here Moeke willis 51 out of 75 three color patch and rookie auto tennessee titans And joseph k Nice one joseph Nice rookie so far. That's the best thing about the multi years Different teams have chances to get something nice Nice malik willis out of 75 three color patch and rookie auto five out of eight javonte williams sunday spectacle denver broncos chad Last spot mojo there Next auto one more for the patch. He'll bear it You have a bay buccaneers, steven car grabs one more a stack james cook 54 out of 99 high voltage vikings Going to kyle and the last one from the spectra four out of 15 orange ink radiant kyle hamilton First round pick for the bolsomore ravens going to nicole Nice jumbo patch there at the orange ink Very nice four out of 15 All right, and then there was one Literally and figuratively 2021 one football one card Thanks again y'all good luck Let's grab a good one to end on davis mills houston texans 71 out of 99 two color patch and rookie auto houston Going to erin billingsley Nice one right there rpa to end it There we go. All right. That's a wrap y'all do a recap here just saw the davis mills, but some fun stuff regardless Thanks again y'all a little six box two-year mixer some fun stuff nice rookie screwouts You have some nice vets too our last one from the playbook jaywin waddle booklet RPA out of 99 Very nice. All right. Thanks again We got more football on the site right now pre-orders for prism football 2022 with the phoenix 2022 four box on the site right now jassescasebreaks.com. Thanks again. Bye.


The obvious question is, okay, so much for all the boys and their toys. I promise you that I didn't really care that much about technology. What I really care about is culture and values and who we are and what makes us tick and all that stuff. Well, so where does this, so the obvious question becomes, well, where does this all take us and when? And when you talk to people who are thinking about this, you get three scenarios for the future. Now, these are not predictions. I don't have a crystal ball, unfortunately. They are credible stories about how the world could turn out in the very near future, given what we know now. And these three scenarios are heaven, hell, and prevail. Now, in the heaven scenario, there are guys like Ray Kurzweil, for example, who has written a book called Singularity is Near, and he's a classic advocate of the heaven scenario. And what he sees is the possibility that you have all of these technologies taking off like this in our lifetimes.  Ray takes 250 pills a day, and he genuinely thinks he's immortal. He really thinks he's going to live for a very long time. And who knows? When you look at the implications of all of these technologies, it could happen. There are guys right now, very sober scientists, as is right, who are at the National Institutes of Health, the National Institute on Aging, and they've got this enormous bet going that the first person to robustly and youthfully live to the age of 150 is already alive today. And these are sober scientists. Are they right? Who knows? But, you know, you're already seeing little moments like two years ago, the absolute number of people dying in the United States went down for the first time. Maybe it's a statistical blip, but who knows? I mean, what it does reflect is how the big killers like cancer and stroke and heart disease are already being affected by all of these technologies. And it's already affected aging.  And you say, what's up with this? And they say, 80 is the new 60. And People Magazine just had a cover story with some major babe on the cover. And what was the deal? The deal is some desperate housewives. And the reason she was on the cover is that she was celebrating her 40th birthday. And you say, you know, didn't used to always be that way. You know, that 40-year-olds would end up on the cover of a magazine like that. I mean, already you're seeing that our sense of what aging is is already being changed. So the heaven scenario is credible. It could happen, but it's only one scenario. There's also the mirror image, which is the hell scenario. And in that world, they see the same kind of curve of exponential change, but they see it going straight down to either the destruction of the human race within the next 20 years. Well, that's the optimistic version. The pessimistic version is the one where you imagine the destruction of all of life on earth within the next 20 years. And the reason that's credible is because they say, well, you know, you look at the powers of these technologies and you say, well, suppose this gets into the hands of madmen or fools, you know, already. I mean, there was the Australian mouse pox incident, which was this classic example. It turns out that Australia is this isolated ecology that from time to time has introduced species that have no natural enemies, and they just run amok. And one of these examples is mice. Apparently, they are from time to time just overrun by mice, mice everywhere. So these Australian scientists were looking to create a mouse contraceptive, and instead they created a monster. They made one change in the genetic structure of a disease called mouse pox, a virus. And all of a sudden this virus became 100% fatal. Every single mouse died. And then they took what they learned and they put it on the internet where anybody can see it. Well, the people who worry about the health scenario, this just drives them nuts because mouse pox virus doesn't hurt humans, but it's a very close relative of smallpox, which obviously does.  Well, that just drives people nuts. One of the lessons here is that if you're dealing with self-replicating anything, whether it's viruses, biological viruses, or information viruses, or robots, or anything else, you better know where the off switch is on this stuff, because, you know, you can just imagine a circumstance in which, you know, this technology running amok in a self-replicating way could, in fact, make a very credible health scenario and could, you know, cause incalculable, unprecedented damage. But again, that's heaven and hell. And the trouble with those two scenarios, in my view, is that while they're entirely credible, they make perfect sense, they are technodeterministic, which means that these are ideas that believe that human history is basically driven by its technology. And that we're just along for the ride. Could be, maybe so, but there's at least one other possibility, and I call that prevail. And in the prevail scenario, the notion is that we humans are not just along for the ride, and we're not just the pawns of our technologies, that we can influence history, and we can make choices in an important way.  It would have reverses and loops and belches and snorts the way history usually looks like. And the core of the prevail scenario is the idea that maybe there's not one curve of change. Maybe there's two. The idea is, suppose you don't just have all of this change in technology. Suppose you've got a curve that's going right behind it and going up almost as fast, which is human response to this change in imaginative, unpredictable, bottom-up, leaderless way. And there's reasons for guarded optimism about this in history. For example, if you were looking out at the future of the human race from around 1200 AD in Europe, you'd be pretty pessimistic. I mean, you'd see marauding hordes and you'd be seeing plagues and, you know, things look pretty grim. It comes then around 1450, and all of a sudden you've got the printing press, which is a brand new way of storing and sharing and collecting information. And the effect is amazing. First, you know, you get the Renaissance, and then you get the Enlightenment, which produces science itself and democracy and the world we live in today, which is dramatically different, you know, from what you were worried about in the Middle Ages. And what's interesting about this is that it was all bottom-up. I mean, it wasn't, this was beyond the imagination of any one king or any one country or any one parliament. It was all people who were just doing the best they can. You know, the people of Venice got run off the land by the marauding hordes. They went out into the middle of the swamp and invented world trade. You know, I mean, it was all kind of ad hoc bottom-up, the classic human saga. You see, the same thing happened in 911. The fourth airplane, Flight 93, never makes it to its target. Why? Because the Air Force is so smart? No. Because the White House is so smart? Hell no.  Was it an ideal solution? No, of course not. They all died. But nonetheless, it was good enough. And that's at the heart of the question of whether or not you're seeing two curves rather than one. The test of the prevail scenario, it's basically a bet on humans being surprising. It's a bet on, it's a faith in humans coming together in unexpected ways, in an unprecedentedly clever ways, in a bottom-up way. And the question is, you know, do you see any evidence of that around you? And you say, well, how about eBay? That's not just the world's biggest flea market. That's hundreds of millions of people worldwide producing incredibly complicated behavior in a bottom-up way without leaders. What about YouTube? Same thing. And it's changing elections. It's changing how we think about power. You know, all of the social networking thing is allowing people to produce very complicated results without relying on, you know, they're not waiting around for some Senate Commerce Committee or something. They're not waiting for their leaders in a top-down way. They're coming up with solutions as best they can, as fast as they can. And that's crucial to the prevail scenario because if the change is coming at you ever faster, the solutions have got to come ever faster too. And that's the problem with top-down hierarchies. So the test would be, for it to prevail, would be the quantity, the quality, the variety, and the complexity of ways that humans find to connect. The test would be, you know, interesting group behavior, groups, not individuals. It'd be like watching a flock do amazing things. And the significance of this, it's occurred to me is that, you know, we've got a long way to go and not a whole lot of time to get there. I submit, you know, if you look at these trends. So it's occurred to me to wonder, you know, we can't find any other evidence of intelligent life in the universe. And I wondered about why that is.  And it occurred to me to wonder, well, maybe all intelligent species get to this point where they take control of their own evolution and take control of really who they are in a really basic way. Maybe this is the final exam. Maybe everybody else is flunked. That's not us flunk.


Thank you, Stefan, and thank you all for coming. Thank you for inviting me to speak here at your pofam. But before I get underway, I want to emphasise that this talk is largely not about my experience. So I am a Jupiter software developer, and I've done little bits of teaching for things like software carpentry. But in order to make this talk, I went to the Jupiter and Education mailing list and asked other people about their experience. And all of these wonderful people came back to me and told me about the courses that they've taught with notebooks and the advantages, the disadvantages, the things that they use, things like this. And so largely this talk is a condensation and a summary of the experience of a lot of these people who responded to my email. So I'm very grateful to them. So in the course of this talk, I'm going to be trying to answer these four questions from the perspective of somebody who's preparing to teach some sort of material and is thinking of using notebooks. So should I use notebooks? Are they the right thing for any particular course? What pitfalls are there? What should I avoid doing with notebooks? What other software tools are there that you can use along with the notebook to enhance the course? And should I host the notebooks on a server where my students can run them? Or should I encourage them to do local installations on their own machines? So I'm going to dive into the first question, have notes. Should I use notebooks? So no, you won't expect me to say that. There's a variety of technical issues, things like using notebooks in version control can be awkward. Projecting them if you've got low resolution projectors, which many places still do, can be difficult. And there are things like if some code produces a massive amount of output, then it can slow your browser down and lock it up and it can be a pain. And there's also pedagogical issues that people raised. A lot of them do with confusion with the unfamiliar notebook interface. In Southampton, where I'm based, they teach a first year computing course for engineering students. And they actually avoid using the notebook in the first section of that course. They introduce it later on because of the bit on the right. They want people to learn sort of common software engineering practices like running code from the command line and writing tests for your modules and things. And these are more difficult to do with the notebook. But on the other hand, on the left there, there's people saying that the notebook can cause them problems because it introduces an extra cognitive load on their students that they're having to learn to programme or learn markdown at the same time that they're trying to learn the subject matter. So there's kind of like two opposing ends of this argument. There's the people saying, you know, the bad thing is that the students have to know too much about the computers. And there's the people saying the bad thing is that the students don't have to know enough about the computers. So this is kind of a hint that maybe there's a niche in the middle that notebooks can fill. And indeed, there does seem to be. So this is Lorena Barber's CFD Python course, often called 12 Steps to Navier Stokes. So this is a fluid dynamics series of lectures. This is Andrew Dawes, who uses notebooks to teach quantum mechanics, in particular around this Python library called Q-Tip for doing quantum calculations. This is the UC Berkeley data rate course. So this is a data science module that they're now requiring all incoming undergraduates to take, regardless of what subject they're majoring in. This is Lex Naderbracht in Oslo, who I'm sure I've just pronounced his name wrong. He is going to start teaching a Python course for biologists this autumn, and he even gets to design a new classroom to teach it with, and he's going to use notebooks for it. This classroom, I should say, is not his classroom. This is one of the examples that he's looking at for inspiration. And a bit of a different example. This is Mike Bright, who has given a variety of container tutorials using Docker and Kubernetes and things using notebooks with the Bash kernel. So this is running Bash code in the notebook rather than Python code, and he delivers these tutorials at conferences like this one. In fact, I think he was at EuroPython last year doing one of these tutorials. So why do people use notebooks given all of the problems that we pointed out before? So the key value proposition, really, of a notebook interface is that you're combining computing and writing and mathematics. So you can combine explaining the steps that you have to do for something with illustrating those steps. And because increasingly just about every discipline involves some measure of computing, this is a very valuable format to describe the computing process. These are all reasons that people on the mailing list gave. I just wanted to pull out a couple of them particularly. So a couple of people said that using notebooks, I suppose, to teaching sort of with pen and paper, allows their students to tackle harder problems than they would writing things down with pen and paper. In particular, somebody who's teaching chemistry said that their students can tackle problems that don't have a straightforward analytical solution. So the textbooks for this subject often limit themselves to problems where you can use algebra to make a straightforward solution, but with a notebook you can go into more complicated problems. And somebody else suggested that when they do their exercises in notebooks, I suppose, to asking their students to submit plain Python code files, then because you have the markdown notes and you have the results that the student has saved in the notebook as they were executing it, you get a better idea of their thought process than you do just from the code that they've written by itself. And these were a couple of interesting things that I hadn't thought of. So to summarise kind of when are notebooks a good idea. So I think that notebooks are a good idea when you've got computational steps to a problem that you want to combine the explanation and the illustration of those steps. But if you're thinking about teaching with notebooks, then you should consider what it is that you want your students to learn. Like, do you want them to be more shielded from the computational stuff, the programming side of things? Do you want them to learn more of the sort of software engineering skills, like using the command line and writing tests and things? And you might decide to use notebooks for part of the course and use sort of regular coding in text files for other parts of the course. Moving on to the second question, what can go wrong with teaching in notebooks? So the big one is slow down. So it's really easy when you've got a notebook with lots of examples in there explaining all of your computational steps to go through going, and as you can see now, we do this, execute, and as you can see, we do this and this and this. And it's easy to go through it much quicker than the people watching that can take it in. So you have to, especially if you have all of the code already there in the notebook, you have to really force yourself to go through it at a measured pace so that people have a chance to pick up what you're doing with it. One way that you can do this is to leave blank bits that you have to fill in as you're talking. That's a very effective way of forcing yourself to slow down. You can also leave blanks if you're distributing these notebooks to the students, then the blanks are bits that they have to fill in. And this is sort of a standard part of teaching is that anything that involves people doing some sort of active process in their learning. So even if they just have to translate a formula into a bit of Python code, it's a much more, that sort of thing sticks in the mind much more effectively than just reading and watching passively. So you can consider doing this. And one thing that we do, for instance, in software carpentry is we leave blank bits for the exercises that students are expected to do. But then there is a solutions notebook in the same directory that they have. So if they're behind and need to catch up with the exercises, they can go and look at the solutions. That works for software carpentry because it's not assessed or anything that the students are just there to learn. So we trust them not to cheat because there's really no point in cheating. So moving on, again, extra software tools that you can use with the notebook. So this is NBGrader, which is a system for creating and using the notebook as assignments. So students have to fill it in and then there's a system for bringing it back and marking it. So this screencast here is illustrating the process of creating a notebook assignment. So you can see there's a sort of extra cell toolbar which is provided by a plug-in. And you can select these cells as being automatically graded answers or manually graded answers. And you give them IDs and you assign numbers of points for them. And it's pointing out that there's a total number of points up at the top. And then from the student's point of view, this is what they see. So there's another plug-in that you're running on the student's version of the notebooks. They get a list of assignments that they can go and download. And that assignment is now a collection of notebooks. And for each of those, the student has the option to run the automatic parts of the marking before they submit it. So they can see how many of the tests it passes or fails before they send it in to you. So in this case, the student hadn't done anything yet so when they clicked Validate, it failed. Now this example student is going to go and find the necessary bit of code and fill in the code to do it. And they'll save that and go back to the overview screen. And when they validate it again, then now it says this has passed. And then the student has a button that they compress to submit this whole assignment. So all of these notebooks. And then on the teachers or the markers point of view, NB grader can take care of the automatic part. So it runs the student's code. It runs the test cells. It automatically assigns marks if it passes the tests in those cells. And then there is an interface called form grader where the marker can go through and manually adjust those marks and add marks for written answers and things. So you're not limited to just questions that have an automatic mark, which is very important because you need to check that people actually understand things as well as that their code works. And NB grader also includes things for then collecting those marks and exporting them into different formats and for giving students feedback so you can make notes on their answer, tell them this is what you did wrong in this place. So it's not just about the score that they get. It's about how they can improve as well. Another tool for the same kind of thing is OK Pi. This is actually both of these auto grading systems were built at UC Berkeley. This is the one that they're using on the data science course that I showed before. This has, as you can see, a very slick web interface from the teacher's point of view here. It's not specific to notebooks, so I would guess that it doesn't have the same level of integration with the notebook interface for creating assignments and things that NB grader does. But if you want to mark notebooks and other kinds of code submissions, then this is a very neat interface. And at the moment I think they even provide this as a hosted service for free. I don't know how long that will last. So another group of tools here are for posting notebooks, which we're going to discuss whether or not that's a good idea in a couple of minutes. And there are two main options that people use here. So Jupitahub is our open source DIY solution. This is Python and JavaScript software that you can install on a server, either a server that your institution already maintains or a cloud server on Brackspace or Amazon or Google or Microsoft or whatever that you have. And Jupitahub, you can set up different sizes of things. So if your students need to solve problems that require a GPU, then you can ensure that this is running on computers that have access to the necessary GPU. And it can be integrated with different login options. So you can plug Jupitahub into your university's single sign-on system, or you can integrate it with GitHub logins using OAuth. Or if you don't want to do any of that, you can just use a standalone login and give students a new username and password to access it. The other main option is CoCalc, which was formerly SageMathCloud. This is what you do if you want somebody else to take care of it for you. The somebody else is William Stein from the University of Washington who is doing this as a startup. CoCalc costs between $4 and $20 per student, depending on how many students you have and how long you want the course to last for. So you can choose a four month course or a full year. And it has its own integrated set of course tools, which include some really fancy things like the instructor can even go in sort of live and remotely collaborate with a student and give them pointers as they're working on it. So before we come back to the posted or local install question, there's a handful of other tools that people said they were using. So one sort of family is for converting to and from notebooks. So NB Convert is a standard part of Jupiter for converting notebooks to other formats. But there are other tools that you can use. So some people like to write their notebooks in restructured text or in Markdown because they're a big fan of their editor. This is often people who are big into Emacs or Vi like to do this. And there are tools that you can do that and then convert it into a notebook file. There are also tools if you want to, for instance, have a collection of notebooks and then convert that whole collection to one big PDF handbook using latex. Then you can do that. There are ways to use notebooks as slideshow material. So NB Convert has an option to go to slides. There's also a plug-in called Rise for reveal IPython slideshow environment, which gives you very similar looking slides, but the code in those slides is still editable and runnable so you can be changing things on the fly while you're doing your slideshow. Finally, it's possible to programmatically generate notebooks. I don't have an example to point you to, but one of the people who responded said that he's randomising questions for assignments and the notebook file format and the NB format Python library make it quite easy to generate notebooks if that's what you want to do. Coming back to the hosted or local question, there's really a range of possibilities here. So going from on the left, CoCalc is in the cloud. Somebody else deals with all of the technical details. You just give them some money and put your students' email addresses in there and everything is set up for you. There's Jupyter Hub where you run the survey yourself, but the experience from the student's point of view is broadly the same. They just go to a URL and do everything in the browser. If your IT department is co-operative on this sort of thing, then you may be able to get it installed on the institution's managed desktop systems so you can go and do a computer lab with the students using the university computers, or you can get the students to install it themselves on their own computers. So if we simplify this to the two main possibilities of either it's done for the students or the students have to do things themselves, there are a few obvious advantages on either side. So with the hosted solution, there's nothing to install. Installation can often be a pain, so this is a big plus for a lot of people. Students can use it from their tablets. They don't have to have a laptop to set it up. Anecdotally, one of the people who does their course like this said they tell students they can bring a laptop or a tablet, and some of the students do bring a tablet. We suspect that if they told the students you need a laptop, then most of the students have probably got a laptop, but some students prefer to work on their tablet. On the other hand, installing it on students' computers is free, at least assuming that students already have computers, which I think in most western countries is probably the case, and you're not at the mercy of any part of the network connection, whether that's the network hardware on your laptop or the institutional Wi-Fi or the broadband backbone over to whatever server you're using. Any of that can go down and that can interrupt your use of a hosted service, and this is a problem that quite a few of the people who are using local installations pointed out. Anaconda, by Continuum, has made all of this stuff a lot easier to get set up, and I would say almost everybody is asking students to install it themselves, is asking them to use Anaconda, because it's made it so much simpler. There are a few people who disagree. These are a handful of perhaps less obvious things that you might want to consider, so most of the automatic assignment and grading tools only work or work best with hosted solutions. I believe work under way in NBGrader to integrate support for local installations as well, but it's also trickier because platform differences may mean that if somebody has got a slightly newer version of NumPy and they use a method that's only in their new version and not on your grading server, then it works for them, but when they submit it, then the tests fail, so there's problems like that to be aware of. People also suggested that there are equity issues, so using a local installation may privilege people who have nicer computers to do it on. It may privilege people who have already got the technical know-how to easily install it and need less help with that. On the other hand, the advantage of having a local install is that the software tools and the materials from the course are readily available after the course is finished. I should say that William Stein, who makes Co-Calc, vigorously disputes this and says that people are no more likely to keep using that on a local install than on a hosted installation. It's questionable whether, yeah, depends on how powerful the free tier of the hosted services and whether students are willing to continue paying for the non-free tier. They're students, so they're probably not going to pay unless they absolutely have to. My overview of this would be, are the computing skills a key part of what you want students to get from the course? If you see the computing skills as something incidental that the students just need to use a computer to learn about this really important material, then a hosted solution probably makes everybody's life easier. If you want them to come away with those computing skills, then doing a local installation is probably worth the trouble. There are people doing local installations for classes of up to 500 students and they say it is doable. It's also possible to combine these. Some people said that they do primary local installations but ask students to fall back to the cloud solution if that isn't working. Some people say that they have the cloud thing as a primary, but they encourage students to install it as well. I'd like to thank once again everybody from the Jupiter education mailing list and these three foundations, the Moore Foundation, the Sloan Foundation and the Helmsley Trust fund our work on Jupiter. I think we have a couple of minutes still for questions. Thank you. I don't know. Oh, we've got a microphone coming. Thanks. Thanks. That's really interesting. In your introduction, most of the examples you gave were of scientific kinds of teaching, but you also mentioned using containers and bash. How well adapted is this to that kind of work? I'd be really interested in knowing about the practicalities of it. From a technical point of view, Jupiter has first class support for the notion of plugging different kernels into Jupiter so you can have different languages running inside a notebook. It all came from Python, but then we generalised the idea to support other languages. The bash kernel is actually something that I made and it was initially supposed to be just an example of how to make a kernel for Jupiter. I didn't really think it would be something that anybody was interested in using. Then it turned out that people weren't interested in using it. It works pretty well from the point of view of using bash. What is tricky in all Jupiter kernels but becomes more of a problem in bash is that if a sub-process wants to do interactive input, so if you do condor install whatever, condor will say, these are the packages that I need. Do you want to continue? Yes, no. Jupiter and the kernel can't tell that a process is waiting for input, so you will see the output of that cell will say yes, no, but then there's no way to actually send the yes, no back to that process. That's kind of a limitation as you have to write all of the commands with the flag to say, don't prompt me please. I have been using Python in the notebooks only, but can you mix Python and bash in the same notebook? Yes, but it's not part of the Jupiter kernel system. Jupiter's conception of a notebook is that each notebook just has one language, but the ipython kernel for notebooks has some of its own support for different languages, so if you start a cell with %bash, then all of the rest of that cell will be sent to bash to run so you can mix languages like that. Okay, thank you. How much difficulties do we still manage a Jupiter hub for example on Ubuntu server? I would say probably Ubuntu server is probably the most common target platform just as a guess. We aim at sort of not technical novice, but like if your system administrator is that postdoc or PhD student in the group who's good with computers, then we aim that Jupiter hub should be practical for them to manage. It gets more complicated if the size of the class is large enough that you want to spread the users over multiple servers, but there are people who do that and I think there's pretty good documentation on how to do that, so it should be feasible for somebody who's sort of familiar with Python and Docker and things like this. Hi, sorry. I've used notebooks before while teaching at university, so I didn't know about the NB grader plug-in and that sounds quite interesting, but I found just using the vanilla without the plug-ins getting students to submit the notebooks is the file size, so we tried to tell them to clear all the outputs, but many of them didn't, so we get very, very, very large notebooks. Is there any automated script to kind of pull them out or is there any suggestions for that in the future? Yeah, there are some scripts that will clear the outputs of a notebook. They're primarily around version control because it's also a pain for that. I think one of them is called NB Strip Out if you search for that. Okay, thanks. Thank you for the wonderful talk. My apologies for not replying for your email on the thread, so I won't add a couple of points here. So one thing you mentioned that's slowing down, right? So that's one reason, I mean I do teach Python professionally. I use notebooks heavily, so one of the reasons I realise is, one of the things I realise is that using a prepopulated notebook makes me go faster, so what I usually do is try to do live coding in the class in the notebook and then share the notebook after the class. That gives a chance for people to go through the thinking process of how I'm approaching that solution, which is usually absent when you give a notebook where everything fell in. I think that's an interesting observation. I wanted to make it. The other one thing that I think that says the duration of the course when you're using notebooks, there are some things that depends on how long the course is. If you're doing for a month-long course and you're doing for a day or two-long course, there are things, for example, the installation and set-up and all that is fine to take long time if it's a one-month-long course, but if it's single-day course, you can't afford to do all those things. Also, I realised when you're using NBGrader that works well for long duration courses, whereas it becomes very tedious for teaching one-day or two-day courses. I don't know if you want to share something on that. I haven't used NBGrader myself. I could imagine that it's probably too much work to set up and get people familiar with for a short course. In terms of the installation, I've done software carpentry. That's typically a two-day workshop that's two days sort of intensive stuff. We get students set up with Anaconda and for Windows users and things like Git Bash on the morning of the first day before doing the teaching on the morning of the first day. I think it is practical even for short courses to get the stuff installed if that's what you think the students should be taking away from it, and for software carpentry it is. I think we're going for lunch now.


Now, a repolarization is when the influx of sodium into the cell stops and the potassium flows out. Remember, whenever something goes in, something else has to come out in order to maintain balance between the positively and negatively charged ions. And the membrane potential returns to a negative resting level, which is the polarization also known as that resting membrane potential. So there is no activity, then every then the sodium flows in, eventually potassium flows out and then we're back to square one until the next bead hits. Where repolarization on an EKG strip is represented by the T wave and that is ventricular repolarization and we'll go into that a little bit more when we look at the actual waveforms.


Stop scrolling. You need to hear this. If you want to look youthful and young and also have a biological age of 10 20 years younger then this video is for you. I'm David Wong and I am a walking proof that reverse aging is a thing and it works I've been mistaken countless times to be 27 or 32, but that's wrong I'm 43 years old these four longevity secrets I'm about to share are based on recent research and the last one is super important So make sure to watch till the end if you do not miss out first up It's all about what's on your plate eat a balanced diet loaded with protein veggies and fruits Stay away from processed foods and sugar take plenty of water to stay hydrated and flush out those toxins to Fitness work out regularly and incorporate a variety of exercises such as weightlifting Cardio and even yoga into your routine doing this not only keeps you physically fit But also helps to improve cardiovascular health and boost your metabolism


Hey welcome back everybody today I wanted to share this great compilation with you that was put together by a guy named Bill Dugastino From newsbusters.org he does great work and this one needs to be seen by as many people as possible You could find a link to the original video in the description or pin comment It's completely wrong. It did not it did not happen.  There was no spying. There was no spying. No spying. There was no spying There was no spying. There was no spying. There was no spying. There was no spying. There was no spying Wow, there was no spying of course There was no spying. There was no spying on the Trump campaign on the Trump campaign It's been a year and a half there was no spying on the Trump campaign of this crap no spying on the Trump campaign, which is a conspiracy theory no spying on the Trump campaign facts matter and Oh, by the way, no There was no there was no no no spying on the truck


Hi, I'm Kelly from the Drupal Association, where I'm the Director of Development. And I'm Nathan Roche, the Marketing Director at Accelerant. We're your hosts here for the new show. We're calling it Beyond the Build, Stories of Drupal Impact, where we're highlighting incredible Drupal use cases by ambitious site builders and end users. Very exciting. We're happy to have our guests on today. Who's joining, Kelly? For this first one, I'm really excited. We got a little backstage preview, and I said, oh my gosh, that's so fascinating. We have Canopy Studios and their client, The Exploratorium. Hi. Hi, folks. How are we doing? Good, either. Doing very well. Thanks for joining us on our inaugural episode. Happy to be here. One of the thousands to come. Oh, that's a lot. Well, let me ask, I'll have you all introduce yourselves. Jim, do you mind starting? How long have you been at Canopy? Tell us a little bit about your role there. Sure. Hi, everybody. My name is Jim Burch. I'm an engineering manager here at Canopy Studios. Been with the company for about five years and work on the build team, so which these days is migrating wonderful existing sites to Drupal 8, 9, and 10 websites. At Canopy, we try to make the internet better one site at a time, and we work with great clients that try to make a positive impact as well. Awesome.  How long have you been at Canopy? I have been at Canopy for five years as well. I think Jim and I started around the same time. And so just to introduce myself. So I'm Tim Tufts. I'm Canopy's director of project success. And what that means is I oversee all the builds here at Canopy. And I work very closely with Jim on many of those. So Jim oversees our Drupal projects, but we also have a number of WordPress projects as well. And I was also the project manager for the Exploratorium project. Thank you for joining us, Canopy, and George Perry from the Exploratorium. How are you doing today? Why don't you introduce yourself? I am doing wonderful today, Kelly. Thank you. My name is George Perry. I am the manager of the online media team, the online media group. We are part of the media studio department at the Exploratorium. I've been here for two years. I started during the pandemic and I have the pleasure of managing one of the oldest websites on the internet. What does that mean? Tell them what, that was the interesting factoid. Oh my gosh. So we were exploratorium.edu is a museum and we are one of the first 600 websites on the internet.  We have had so many iterations of content and we have a bounty, a wealth of pages from the past and present that we really care about maintaining. Yeah, it's a big challenge to manage all of that. I can say that the first webmaster is still involved with the exploratorium and a lot of the people that were there, some of the people that were there at the beginning, it's very impressive to be able to traverse the online legacy of the exploratorium and all the craft that we've built along the years and somehow kept around, which was a treasure trove of opportunity. Can you tell us a little bit, George, about the mission of the exploratorium? Okay, so how can I say? The exploratorium is a, how do we say, a public learning laboratory for exploring the world. There's science and art and human perception. And we really, it's actually right in front of me oddly enough, deal with creating inquiry-based experiences to transform the learning experience. How that drives traffic to the web is historically learning materials for teachers, for students, a fair amount of interactive. Long time ago, we invested heavily in flash of our actives. Now, what we have are still some of those around, which we kind of bootstrapped with some of the, one of the open source programs, Ruffle, that is making a flash interpreter and a lot of, you know, JS interactives. We really are all about inquiry, all about experiential learning and we love that we can embody that on the floor and in the website and things like science snacks, tinkering, a historic one, science of food. Yeah, and we have events and programming throughout the year. So it's not just a static once and done website, it's forever changing. People host events here. Wonderful place. Completely ever-changing. So then Tim, tell us about how, I mean, you didn't come in from the beginning, from the long time ago, about when did you all start your relationship with the Exploratorium? No, we did not start our relationship in the 90s. So it was a little over two years ago, the Exploratorium was looking for a partner to help them transition from Drupal 7 to Drupal 8 at the time. And the challenges that come along with that. So as George sort of alluded to, there was a lot of cruft that had occurred over the years. I'm sure we'll probably get into a little more detail as far as like some of the challenges and some of what that cruft looked like. But yeah, the Exploratorium was looking for a partner to help them create a blueprint and roadmap for transitioning to Drupal 8 at the time. And of course, we're now on Drupal 9. So big, big difference from when we started this project two and a half years ago. Great. And what before Drupal 7 was the site on Drupal 6 or a previous platform? We were static HTML. So it was created with, I mean, can I say, I'll say like random tools like front page and just, you know, hand coded. Initially the website was obviously hand coded because, you know, it's beginning of the internet. I didn't even think of IDs or anything like that. But it was pretty much hand coded until then. And one of our team members was part of the people that brought it into Drupal. And so they've shared a lot of history with us of it. And some of the cruft like, oh my God, this is a test page we created long ago. I'm like, wow, it's still published. Okay, we're gonna sunset this wonderful treasure. But it's such bitterness. It's endearing bitterness. Because like we have a lot of things where it is like, wow, what is this doing here? And you know, like practices. So it was one of those like, you know, pingable pages where it's like, ah, your site is up and it's like, okay, this is the ping test page that nobody ever knew existed. So it's a lot of like this wow discovery still, you know. Hidden treasures. Hidden treasures, exactly. So Jim, then you came on and you've been working with Exploratorium for two years as well, or when did you join the project? Yeah, so I helped co-developer Blanca Eskido work on the transition plan at the initial. So we basically looked at the Drupal 7 site and kind of did our technical planning from a high level, you know, in a small, you know, bite-sized project, you know, from that, you know, Exploratorium decided to work with us further to actually implement the plan. But, you know, we took a look at what they had, you know, from inside of Drupal 7 to the 300 micro sites or folders of the site that they had, you know, the static HTML sites and came up with a phase one, phase two, phase three approach.  You know, so we looked at 41 content types in Drupal 7 and figured out that maybe we don't need so many, you know, things like exhibits, exhibitions, galleries, things that have very minutia differences to the Exploratorium team, but to the outside world, we came up with the term experiences. So we kind of merged all these things into one experience that could be displayed at a calendar, whether that be an exhibit, not going exhibit or just a one-time event. So yeah, we were able to come up with a migration plan that was executed by my incredible co-workers Dan Bonham and Andy Sipple and George's amazing team of developers also. So, you know, Canopy and Exploratorium worked hand in hand with design and development. Coming up with an architecture, did the experiences section, the calendar section first and then move out to the rest of the migration? Can you tell us about the journey through those three phases? Were there any, you know, really significant challenges or things that sort of stick out for any of you when you're going on that journey? Can you tell us a little bit about some of those hiccups or some of those challenges or hills that you had to climb? I think if I can start it off, it's, you know, George and his team have a lot of different stakeholders. So, you know, he leads the online media group, but he has marketing, he has fundraising, he has, you know, the tinkering team, which makes these great tutorials for educators. Oh, I want to be on that team. Cool. Yeah, it's really cool. I mean, online and in person, you know, the Eclipse project where they partnered with NASA, you know, they were one of the first peoples to live stream on the internet. You know, it's just like the amount of stakeholders that, you know, the exploratorium had was, you know, very important to make sure that we satisfied all of them in a timeframe where we could. We actually ended up launching the site partially using some domain masking where the Eclipse project needed to launch before the full site was launched a couple of weeks ago. We actually, you know, sent part of the traffic to the Drupal 9 instance and the rest of the traffic to the Drupal 7 instance. So we could, you know, make the stakeholder goals in that project a reality while we're still working on the rest of the team too. That's pretty amazing. That sounds very, that sounds like a good solution. Sorry, George, were you gonna say something? Oh, yes, definitely it was for us too. Like there was just so much unknown and churn through our team. Like when I got here, there were, it was me and two other, two other people and somebody who was a contractor. And really that, and one of those people had was for a while was the only person on the team. And they were a designer and we were working through a lot of discovery of the unknown within our content. None of them really knew Drupal, not intimately, like knew how to use Drupal, but deep in the guts of it, there was reservation to get in there. I came in and I wanted to train people like, okay, we own this, we have to have the knowledge of the system, like develop that deep knowledge, not just so we can do it ourselves, but so we can make the decisions of what we can't do ourselves and no one to ask for advice. And in the hunt for a partner with that, like Canopy was definitely the best folks that we found. We learned a lot from them and it was a definitely a together journey. I think the hands probably the biggest challenge in summary is just like, there was just so much randomness to be found. And there were so many ways that with the limited knowledge we had, we, sometimes we got things right, sometimes we got things wrong. And with Drupal, there's a lot of ways to do things differently. So having expertise and experts to help us through that was like, okay. But Drupal pulled through to be a very handy tool for creating the products. And let's go into that because Kelly and I are super interested to understand why Drupal. We understand that you were on seven prior, but why does Drupal work for the Exploratorium? Okay, for us, we had like tens of thousands of web pages and we needed to be able to have multiple editors. So we had to be able to deal with role-based, multi-tenant, different experiences, as far as things like the Eclipse, as far as the main website, other projects as well. Drupal, your LAMP stack is a tried and true platform, when it's Apache, my SQL PHP, it's tried and true. I used to work at Yahoo when Yahoo was a thing. And they were LAMP stack and it's a very classic architecture with caching is scaled very well. The concerns were repressed with that volume of pages and their data model, we thought Drupal would be a lot better. We decided that sticking with Drupal, like primarily as not just the data layer, but as a front-end, who are trying to do the front-end and react or in Gatsby or anything like that, we found that this would be best for us to stick this route because of not just SEO, but editor knowledge and visibility into what the end product was. And Drupal is infinitely flexible. It's open source, I love open source for a long time. Yeah, it generally, I think was the best choice that we had. And you mentioned multiple stakeholders. Did you have to sell Drupal to these stakeholders as well? You mentioned marketing is in the mix. I'm not sure, maybe Canopy had to help you to do that. How do you get everybody on the same page before finding a solution, a capable solution partner like Canopy? So being already in Drupal, we had to sell them that, we did have to sell some folks that people were saying, a lot of folks were like, why don't you just change the WordPress? And then there were the folks like, well, this is a great technology. Why don't you just do it the old way? Do it in or do it in React. And we had some folks like static HTML and is King and I was like, well, that's not gonna work. So it was, some people it was a hard sell, but most part of it was the sell of like, what my content will look like, how will I be able to access it, you know? And also like, what content belongs on a website anymore? On this single website? Because we were all things to everything. We were an archive. We were a portal for selling tickets. We were a knowledge base. We were too many missions. So we had to, even with Drupal, we had to take some data and move it elsewhere between archive it and between a static HTML S3 bucket. So that's a, yeah, make some tough choices and have a lot of stakeholder conversations. So we tried to manage it through also from the top down. So kind of working up my like management ladder and then down the leadership ladder because creating, scoping this by just asking everybody what would you want? It was never going to work. We really need to approach it from this is what you need and go as database as possible. So we leverage tools like Google Tag Manager, Google Search Console, Heatmap Tracking. Like we use all that to justify what we wanted to do as opposed to the passion battle because the passion battle was never going to, it was just gonna be, it would never work out. Wow, that's amazing. Nice. So you had mentioned that you just a couple of weeks ago launched something on Drupal 9. Where is the rest? So you're still in the midst of this. This is an ongoing and there's still work to be done. We're all the way on Drupal 9 now. So as of 419, 420, we went fully into Drupal 9 and a couple of weeks before that we just had the eclipse in there. So it's been wonderful but there've been a couple challenges along the way but after cut over, but it's mostly little content stuff like dude, where's my page? So we just dealt with that and the feedback we've got has been very positive from this is amazing. I never thought this would happen. Oh my God, I can't believe it. It took a long time to get the project off the ground because of the pandemic. And so that was a major hurdle as well. But also just because we launched the site doesn't mean we're done. As things go in Drupal and the internet. So just today we've talked about scoping a plan to upgrade to Drupal 10 before. Talked about during the project, Georgia's team had to launch another site on a standalone Drupal 9 instance just because of scope and priorities there. We talked about rolling that in. So we don't like to launch, say goodbye, we wanna be partners with our clients in the exploratory and support them in their web journey. Yeah, I think an ongoing relationship is definitely gonna benefit us too. And hopefully I can get more of the team involved in the Drupal community. So I think that would benefit us and hopefully the community too. Speaking of teams, so Tim, you are managing the project, right? What's the team size that was currently working with the exploratorium from Canopy's side? Yeah, so on the Canopy side, we had about four developers, myself project manager, and then we had a designer who was also working on the project too. Great, excellent. And as Drupal 10, this is approaching, what are the conversations now about getting ready? I hopefully, I would imagine they're much easier to be had than the previous project, right? Which is the whole point. Yeah, the conversations we had today were, let's get it on the roadmap. Understand that George has a lot of, probably content commitments he needs to address first, but we run tests on our active developments. So we already know where deprecated code lives from Drupal 9 to Drupal 10. We know which modules will need to update ourselves or with help from the community. We'll know what content editors will look for with like the CK Editor 4 to CK Editor 5 upgrade. So we're looking to put it into our schedule this summer. Before we get near the end of life date for Drupal 9 and before the Exploratorium team gets into fundraising season and they're gonna be busy working and supporting those teams. Perfect, so you're definitely keeping your eye on how busy it gets at the Exploratorium. I understand fundraising season, so working with them on that, all of those deadlines. Yeah, it's a big grouping together of technology and real-world business needs. We try to find that place in the schedule for all of the things. Awesome. Yes, yes. All right. Great, great. I mean, I just had a couple more questions. If that's all right, I wanted to know about what makes a relationship work really well because we can tell that you all have like a lot of synergy. The relationship is really strong and you have a legacy of delivering value and investing in your platform. What makes all that work? Like, is it just the demonstrated trust from those three phases of the initial launch and now, George, you can rely on Canopy because you've seen them in action? Or is it something else? And this is open to anybody to answer just about how the customer and agency relationship, how it works and how it's working really well and the why behind that. Thank you for your stretch of your word. Go for it, go for it. I think what's been really great to see with our partnership with the Exploratorium is just that it's been a partnership. Not only has it just been the Canopy team doing the work, it's been the Canopy team and the Exploratorium team. So Jim mentioned earlier that there were developers on the Exploratorium team as well and we've really collaborated and worked really well together, I think, throughout the entire project. George's team might take on a couple of tickets just so they could learn more about Drupal and our team might have given them some support or some insights to sort of one up their Drupal experience or expertise. But then we were having weekly working sessions, meeting to discuss priorities or any sort of challenges or if there are any sort of sticky topics that we needed to work our way through. So there's a lot of transparency, a lot of collaboration and I think a lot of trust between our two teams throughout the entire project. Looks like the customer agrees, George. Definitely, I definitely agree. And I think like in that, even with Canopy, they're willingness to deal with when they got on, we were like, oh, we know we're gonna discover so many skeletons, these clauses. Like they're skeletons behind the skeletons, behind the skeletons. And it was a wonderful phase of discovery and collaboration and partnership. I think definitely the key word in being partnership for sure. And that they, we wanted somebody that was gonna be there to help us learn and work together and not just throwing requirements over the fence back and forth. I can't, having been in software for some time, like just throwing requirements back and forth over the fence just never works. It just makes for a painful process. And I've also done technology consulting before. And so I wanted somebody would help us to, not just be a hundred percent dependent, but to help us to understand, to help ourselves. We can help each other along the way. And I think that forms the best consulting relationships. From a droopal point of view, I think George and his team also had a very good understanding or learning of where all the skeletons in droopal are buried also. Oh my gosh. So, we came up with some very interesting bugs in core and contrib. And it's not just, here's another ticket. This is broken, fix it. But let's get to the root of the problem. Can we contribute code back to the community to help fix this at its root rather than just for us today? So that understanding is because they're a very technical team, even though they didn't all come from the droopal world, they really embraced understanding of droopal and we're trying to do very complex things. And sometimes all the little bits and pieces, all the little Legos don't fit together in the right the way they're supposed to in droopal. So, we work to try to make droopal better in addition to the website. Yes, thank you for that. That's amazing. That's the end game is contributing back and these partnerships make them successful and successful for the future of everybody using droopal. Awesome. Well, I mean, thanks everybody for joining. I know we're about 28 minutes in, so I hope that this was okay. It was our first time, Kelly and I, right? Thank you so much for that. You all really expanded and did more for us than Nathan and I could have done, the things you said. So thank you so much for all your expanding on everything. That's why we want to talk to the experts. I know, I'm so good. Thanks, folks. Thank you. Thank you, teams. It was so nice to meet you. Thank you for joining us on our first episode of Beyond the Build and if you have a droopal agency that you want to bring on with one of your amazing clients, please email me at partnerships at association.drupal.org. That's partnerships with an S at association.drupal.org and thanks a lot and we'll see you next time.


It is in the harsher weather that we tend to become more conscious of transport, buses, cars and of course taxis. I'm Cameron Buchanan, I'm a member of the Scottish Parliament and today I want to find out more about the use of taxis in Scotland. You don't drive do you? I don't drive. So therefore you find taxis are essential to get around? They are yeah, they're very helpful certainly. And you use black cabs rather than other means of transport? I do yeah, if I'm in Edinburgh I'll use the black cabs. So you take a taxi because you need it because of Joe here? I had to take a taxi up the town before because there wasn't enough room on the bus, at rush hour it's quite busy so there's no room on buses so I've had to jump on a taxi before yeah for that. So Margaret, you take taxis all the time? Yes, quite a lot. For what reason? Well when I've got loads of messages I take them home, that's one of the, you know taking taxis now because the bus service is quite slow in between and I prefer it because it's much easier. Why would you take a taxi then? If it was a case of going somewhere special and you know and you're all, you'd have to go somewhere and you'd not want to go into the rest of going out for an evening or something like that and see the point of getting into a taxi a few of you, that's all right. Within Scotland taxis are regulated differently by different authorities. For example some authorities stipulate that all taxis have to be equipped to deal with disabled passengers but other authorities don't impose these sorts of rules and there are differences in what's expected of cars and drivers depending on whether you're a public hire, a black cab driver or a private hire driver. Do you take a taxi because it's handy or because you need it? Because it's handy, yes. If I'm getting home late in the evening. And for safety sake? Yeah. Good. And the bad weather too. The only issue I have is with cost if there's five people in the company then it's a reasonable cost but if you're travelling alone or just two a year then it's too expensive. And you find them quite safe and easy to get into? It depends on the taxi driver really if they're willing to help you but sometimes they're a bit lazy to get out. It's not easy. And you find them reliable? Yes. The only time in Musselborough they're not reliable is between the school time four o'clock. Most of the taxis in Musselborough are school runs. So they're very difficult to get in at that time. In fact the whole taxi regime in Scotland is coming under official scrutiny. The Scottish government has proposed changes to the way taxis are regulated and my committee is examining those changes to see how they work. Well taxi licensing is only part of the bill. Cameron has taken a lead in this area. I think everybody has got an opinion about taxes. What we would like them to do is to share their opinions with us and let us know what they think about the provisions that are in this new bill. Obviously changes will always affect not only the tax drivers themselves but also members of the public. So we are very, very keen indeed to hear what they think. So here's what parliament wants your views on. Is there a consistency between black cab and private high licensing regimes? Are there enough taxis available? Are they accessible enough to impaired users? Do you think all drivers should have to meet the same standards, levels of knowledge and background checks? Please do let us know your views. You can get in touch with the local government and regeneration committee by writing to us or by email or telephone or through social media.


Hi, I'm Gabe. The feels a little bit funny coming here and telling you guys that Linux, an open source of the future of gaming, sort of like going to Rome and teaching Catholicism to the Pope. So bear with me. Valve is, we were founded in 1996. We have a mix of single player and multiplayer games, like Half-Life, Counter-Strike, and so on. We've shipped our games on a bunch of different systems, the PC most obviously, as well as Mac, Xbox, PlayStation, and other consoles. And we've also created a set of tools for software developers and for customers called Steam. Now, a lot of our decisions and our thinking about the future is based on what we see as structural changes that are the consequence of the ongoing improvements in performance and price performance and computing and networking. And I think that people always overestimate the effect of these things in the short run and underestimate them in the long run. One of the key decisions we made when we were first starting the company was the realization that as we continued to reap the benefits of those kinds of performance improvements, that the relative value of different line of business functions would change, that sales and marketing and distribution would be cheaper and easier. And that meant that the design and development of products were going to become more valuable. And a lot of times you'll see corporate structures that struggle to keep up with that pace of change. But it's not just in how corporations should be run that those changes end up being propagated. It has implications throughout my industry, throughout the gaming industry. You'll see it in things like the emergence of digital distribution platforms like our own Steam. But you'll also see it in ways that are kind of surprising. For example, we reached a point a couple of years ago where the marginal costs of having another player were less than the marginal community benefits of having somebody be in that audience or participating in that community. And that gave rise to what at first sounded a little bit perverse, the free to play style of games. And you also see other phenomena start to occur. So you'll see things like Twitch TV coming along or eSports where in order to have a model that encompasses the value that people get out of it, you have to think about the novel ways that content creators and experiences are going to be generated. And at the last tournament we held, we had over a million people watching it simultaneously. That was between a Swedish team and a Russian-Ukrainian team. Now these structural, just because of course right now Valve is fairly successful. So it would be nice if the world just stopped right here because this is a point in time when we're doing well. But the process is actually going to continue to go on. In the same way we've seen the center of gravity of gaming moving from console hardware platforms into developers and services. We think that process is going to continue. And it's really the users that are going to be the focus of optimal strategies, both from a technical point of view and from a market development perspective. And to sort of skip a four or five hour long presentation, the conclusion that we reached is that games are essentially going to be nodes in a connected economy where the vast majority of digital goods and services are going to be user created rather than created by companies. So let's take a step back and just talk about Valve's own experiences with Linux. In 1999 we shipped our first game server for Linux. And since then it's pretty much been the majority of the game servers that have been out there. And that means around the world there's actually probably over a million game servers out there right now running. We not only have used Linux in terms of deploying a service footprint, but we also just use it internally. So we've got all of our source code, all of our models, all of our animations, all of the assets are all being run on top of Linux. We go a year where we love the performance, we love the reliability and robustness of it. One thing that tends to shock people, sort of especially in the traditional media world, is just how big games have become. When we do a new update for something like Dota 2, nearest we can tell that we're generating about 2% to 3% of the worldwide mobile and land-based IP traffic. And that tends to startle people who don't realize what a large sea change has been going on. Now, our experiences we think are fairly typical of lots of people in the games industry. So if you go to Blizzard or Bungie or any of the other game companies, you're going to find that in terms of building out a service vision in terms of running their own operations, they're all super comfortable and have a lot of experience running with Linux. On the other hand, as we all know, the user experience of being a gamer trying to play on top of Linux has been pretty painful. Any metric that you use, if you're just looking at how many players there are, how much time they spend playing, how much revenue they're generating for game developers, it's very small, typically, like I say, under 1%. And that's way too small to ever get any attention in terms of making sure you're compatible with device drivers or distros or thinking about how to improve that experience and so on. However, what we became convinced of is that Linux really is the future of gaming. And what I'm going to do for the remainder of this presentation is talk about why we think that Linux is critical and what Valve is going to do to help make that happen. Several years ago, we got very concerned about directions that the PC industry was going. We thought, well, how to be polite about this. So we thought that there was, well, we thought there was some bad thinking. And that there were these new platforms that were starting to emerge. And they had this nice characteristic that you could control access to those platforms. If you didn't like competing with Google, you just didn't let them ship on your device. Or you could determine how often that they could update. You could have a lot of control over things like pricing and other characteristics. And that was a very seductive opportunity, which I think led to some poor decision making by some of the key actors in the PC space. I think that the way that they should have responded is very much the key off of the strength of the openness of the systems we had and to double down on that rather than going the other way. So jumping forward, what are we looking at now? We're looking at steady year-over-year unit declines in PC sales. And the people in the field sort of are dear in the headlights. They were like, we didn't have a model where this was occurring. We thought that people would always keep buying more and more PCs regardless of what we did and what sort of restrictions we imposed on them. And you see all these articles, PCs in decline. I think we'll see either significant restructurings or market exits by top five PC players. It's looking pretty grim. On the other hand, PC gaming seems to have been immune to this downturn. So in the past, back to the Nintendo Entertainment System days, gaming really was led by these proprietary hardware and software standards that also, if you wanted to get your cartridge made, you bought it, FOB in Tokyo. If you had a competitive product miraculously, your ROMs didn't show up until three months after the platform holder's product had entered market and stuff like that. Those really were sort of the dominant models for what was happening in gaming. But not too surprisingly, open systems were advancing much faster than the proprietary systems had. So there used to be these completely DeNovo graphic solutions for gaming consoles, and they've all been replaced by PC-derived hardware. The openness of the PC as a hardware standard meant that the rate of innovation was way faster. So even though you would think that the console guys would have a huge incentive to invest in it, they were unable to be competitive. There also used to be, almost nobody knows this, there used to be proprietary networks for gaming, and the internet was like, who needs that? And obviously, the internet was completely displaced any of those homegrown solutions for multiplayer gaming. So PC gaming is where innovation is occurring, and you'll see that in lots of ways. It's not on the consoles. It's not on any of the closed systems where the innovation is happening. It's happening to the extent to which openness is embraced by the underlying platform. So digital distribution came out like Steam. Social gaming occurred on the PC, free to play, MMOs, trading workshops. All of the most interesting topics in the game industry really are coming out of the open environment of the PC. So in spite of seeing year-over-year unit declines in PC sales on the gaming side, we're seeing huge increases. So the data I'm most familiar with is ours, but we're going up 76% year-over-year at the same time PC unit sales are getting double-digit declines. And I think that that's true for all of our partners in the PC space to varying degree, that the innovation and openness of the PC as a gaming platform have enabled us to be somewhat immunized against some of the broader structural decline of the PC. We also think that the rate of change is increasing, that we're not really going to be slowing down. And so that systems which are innovation-friendly, that are which is equivalent to openness, are going to have greater and greater competitive advantage to closed or tightly regulated systems. We actually think that we're going to see a significant sort of democratization in the content creation process. Users will be, the distinction between a content creator and a content consumer will get blurrier and blurrier. And just to be really concrete about that, so Valve, we're kind of a cocky company and we like to think we can compete with any company in the world, right? So if we sat down and said, oh, let's have a competition with Bungie or Epic or Blizzard, we're friends with all these guys, by the way, we'd feel like, oh, yeah, we can take them. We're good at what we do. But the one entity we wouldn't ever want to compete with is our own users, right? That they have already outstripped us spectacularly. You can't compete with them once you give them the tools that allow them to participate in the creation of the experiences that they find are valuable. And it's not by a little bit. It's like an order of magnitude more productive already. And we're only a couple of years into thinking about how to do that. It's like, you don't want to compete with your customers because they're going to be way better. You also don't want to compete with Reddit or 4chan, but the point is that the connected groups of users are going to be way more successful if they're properly enabled and supported than any of the individual game developers are going to be. But there's this huge tension between if that's the direction that gaming is going or if that's the direction content creation is going, these other systems actually put a tremendous number of roadblocks in the way of doing that. It takes several months to get through certification process for a single update, right? I mean, it took us six months to get one update through the Apple Store to ship an iPad update. And we have a lot of resources and have a huge commercial motivation. And no individual user, if they're the sort of the center of gravity for content production is going to have the wherewithal or the stubbornness to get through that. That's just one example of the many ways that the closed systems appeared us to be antithetical to our user-centric model of content production going forward. So in general, we've seen tremendous evolution and innovation in the open space. We've seen that we think that that process is gonna continue. And we think that we need to be knocking down as many barriers and reducing friction not going in the other direction. So what have, you know, okay, that's great. So what have we been doing? So several years ago, we actually were like, wow, this is where we think games are going. You know, there's a logical consequence to that, which is we need to be working pretty hard to make sure that Linux is a good solution for gamers and for game developers. And it was kind of distressing because there was just a lot of work that we would need to do in order to help address those issues. And it wasn't just that there was the work. You had to figure out how to stage it out, right?  So not only did we see ourselves needing to do a lot of work, but we also had to be think about what was the process of rolling that out with partners and with customers. So the first step was to get a game running on Linux. And we used that, you know, like developers do is kind of a sweater threat of issues. Like, so we're going through and it's like, oh my God, it's incredibly slow. And then we go and we talk to Nvidia and work with them to fix their drivers. And then we get it to the point where it's a lot faster than the Windows version. It's like, okay, that's great. And then you find, well, the user experience is impossible.  Well, you know, here's a super long, well, just compile it yourself. And you're like, oh, well, it's not a good solution for your average user. So it's just by, you know, going through that exercise of getting one game up, you know, you have to do a lot of different things.  And that definitely appears to have been true that if you get, you know, the kind of game that we produce all, you know, create a good user experience around that, that you probably, you know, we've definitely solved problems for, you know, the Call of Duty team or, you know, Unreal Tournament or whatever. It's, the games aren't that much different. The key thing is to get it all the way through to customers. So then this February this year, we shipped a Steam client for Linux. And as much as anything, that was a signal to our development partners that we really were serious about this Linux thing that we were talking with them about. And now today we have 198, at least when I got on the plane, we had 198 games that were running on Linux.  We have engineers who work on SDL, which was an open source project started by another Valve employee, Sam Leninga, or a contributing member of the Kronos Group. One thing I don't think we've talked about is we're actually developing, co-developing a Linux debugger. That's in addition to the work we've been doing with the LLVM people. So when we go out and talk to developers and say, okay, you know, if you can pick one thing for Valve to work on on the tools side to help make Linux a better development target for you, what would it be? And they always were coming back and telling us to work that we should build a debugger. So we're working with another company on building a Linux debugger. These are useful things to do to help move things forward on the developer side. Now I'm going to take a step back or so I can talk about the living room. You know, there's this notion that there's, there's kind of struggles I think you guys go through on the cloud side where you recognize sort of the implications for how you can abstract certain problems away from both developers and users where, you know, it doesn't really matter where you are. It's all, you just know that it's going to work. Those are exactly the kinds of problems that we think are important to attack on the gaming side. Right now, you know, you're sort of in this bizarre situation where as soon as you sit on your couch you're supposed to have lost connection with all of your other computing platforms.  So we thought that that was just, that was an incorrect way that really through design and through thinking hard about how to create appropriate abstractions for both users and developers you could build something that spanned, you know, like the desktop and the 10 foot living room experience. And it's one of those things where people sort of like, oh, people don't want PCs in their living room and you basically, there's no amount of arguing you can do with that person to convince them otherwise. Or they say, yes, this is trivial and obvious. And so one of the things that we had to do is we're staging out what we think is the different pieces necessary to make Linux the basis for the future of gaming. We need to build something which showed that, yes, in fact, you could take everything that you liked about your PC and get it to work in your living room. That's called Big Picture. Our next step, having done these other pieces, is now on the hardware side. We think especially, you know, there's sets of issues to making sure that whatever computing platform you have works well in a living room environment. There are thermal issues and sound issues, but there are also a bunch of input issues. So the next step in our contribution to this is to release some work we've done on the hardware side. Even more broadly in terms of sort of the grand unification, we really don't think that there's the fragmentation around the physical location or the input devices of computation is either necessary or desirable for software developers or for consumers.  There may be pluses and minuses to their specific environment, but nobody says, oh, I'm in an airplane now, I'm gonna use a completely different method of accessing data across the network. And we think that that should be more broadly true as well, that you don't think of touch input or game controllers or living rooms as being things which require a completely different way for users to interact. Or acquire assets or developers to program or distribute to those targets. Obviously, if that's the direction that you're going in, Linux is the most obvious basis for that and none of the proprietary closed platforms are gonna be able to provide that kind of grand unification between mobile, the living room, and the desktop. Actually, next week we're gonna be rolling out more information about how we get there and what are the hardware opportunities that we see for bringing Linux into the living room and potentially pointing further down the road to how we can get it even more unified in mobile.


Gold I believe is 101 is a 101 it's gonna be John Smoltz John Smoltz on they want to one for the Braves This would be a Braves case right here Smolty Vaughn Investigator Vaughn, what's that patch? Investigator Vaughn, what do we got there? postseason 8 15 postseason wins ranks third all time Very nice one there the 33 patch John Smoltz action there only 101 gold go great case so far Alexander


What's up everyone? It's your girl Kenzie here from Layton Sports Guards and I'm up in a personal for Dylan S. We've got a 2023 Top Star Wars Signature Series box. All right, best of luck Dylan. Thanks for hopping in. And thanks for being the first Star Wars. Again, this is just added recently as well as a couple others that are in stock. Yep, it's one encased autograph card per box. It is. Let me use one card per box. It's kind of like a archives feel to it, you know, one encased card. All right, let's see what we have. We have a Tuscan warrior, authentic autograph Tuscan warrior, the book of Boba Fett's Joanna Bennett as Tuscan warrior. Cool in there. Scary looking dude. All right, that'll do it for you Dylan. Thanks again for hopping in. Congrats and we'll get this right out to you.