Hey, Psych2Goers. Do you remember more of being scolded or being praised as a child? Which one stuck with you the longest? We often have the tendency to repeat negative and bad memories more often than the positive ones. These words carry weight, since there's a greater cellular activity in the brain when negative memories are formed. Because of this, it's important to be careful with the way you speak to your children as it can stick with them for a really long time. To learn more about this, here are six things parents should never say to a child. Number one. You can't do anything right. Were you ever told this when you did something wrong? Patience is a trait not everyone naturally possesses, but it's important for parents to cut down on these types of remarks whenever your child isn't performing up to caliber. It serves no purpose other than to belittle them, which can discourage and do more harm than good to their growth. This phrase can also lead them to set unrealistically high expectations for themselves that can lead to feelings of inadequacy and resentment later in life. Number two. I'm disappointed in you. This may be something you often say to your child when they've failed to meet your expectation or standard, but it can actually be quite damaging and harmful for them to hear it, especially for younger children. According to Dr. Lim Boom Leng from Psychological Wellness in Singapore, your children are more susceptible to their parents' moods than older ones. Thus, it's important to tone down your statements like this, since it can end up bruising your child's self-esteem and confidence. Number three. You should be like your brother or sister. Were you ever compared to your siblings before? It's crucial to recognize that children are individuals with their own personalities and traits that make them unique. Instead of telling your kid that they should be more like their sibling or classmate who may excel at a certain field or subject like sports, praise them for their strength in the things that they're good at, like literature or the arts instead. There's no one perfect role model, and needlessly comparing your child to someone else's or their sibling can make them feel inadequate. Number four. It's your fault that something bad happened. It's normal for every parent to feel upset, angry and frustrated at times at the things that their children do. However, it's very important to be careful with the words you use when you're feeling that way. Children, especially the younger ones, are not able to differentiate your anger as an expression of frustration from an attack on them and therefore their sense of self-worth. For example, if an emotionally taxing event like the death of a pet occurs because of your child's negligence, they can be a burden for everyone. But in moments like these, it's crucial to take the time to be compassionate and to educate them on how to deal with their sadness rather than assigning blame. This will help them understand how to navigate emotional turmoil, which is something they can carry for the rest of their lives. Number five. Don't cry. Do your parents get uncomfortable with emotional outbursts and tell you to stop?  This can make it more likely for them to develop mental health issues in both the short and long term. Similarly, phrases like don't be sad or calm down should be avoided. Research published in Washington State University shows that being able to openly acknowledge how you're feeling no matter how negative it is can help improve mental health for both parents and children. Number six. You're the best at everything you do. Remember that. While warranted praise is healthy, giving undue credit can actually be bad for them. Some children who are praised too frequently can develop a sense of entitlement and become overconfident in their abilities. At the same time, others who are praised a lot can end up feeling immense pressure from the expectations that their parents set on them. This may cause them to fail to act or become unwilling to try new things. The best approach is to give specific and honest feedback. For example, instead of saying your child is the best at soccer, be specific about their positive traits like how they're an excellent leader who motivates their teammates during games. Did you relate to any of these signs above? Let us know in the comments below. If you found this video helpful, be sure to like, subscribe, and share this video with those who might benefit from it. And don't forget to hit the notification bell icon to get notified whenever Psych2Go posts a new video. The references and studies used in this video as always are added in the description below. Thanks for watching and see you in our next video.


Hello and welcome to Chris's open-source TV show today, and today we're going to answer the age-old question Which Linux distro is the best and I've got the answer right here after all these years We're gonna find out the truth. Which Linux distro is the best the answer is Debian. Have a great day Doobie doobie theme music do do do do open source do do I mean free software? It's called free software do do do the technically two different things do do do no seriously though It's such a flawed question, which is the best what is your definition of best, you know It's like saying which car is the best are we talking about? acceleration top speed ability to tow something Fuel economy Electric versus gas it all depends on what you need and it's the same with links distributions now I can give Suggestions, but which is the best for me is not gonna be the best for you and your uses and lots of distros are our geared towards Something specific like I don't know if it still exists. There used to be one called scientific Linux Which had a lot of applications pre-installed for doing scientific calculations and math calculation stuff I don't know I never used it Another example is like Cali Linux Cali Linux is used for pen testing It's not meant to be your primary desktop. I mean you can use it as your primary desktop Operating system distribution whatever But it's not geared towards that. So here are my picks on different situations That I personally prefer but again, I'm not saying the other distributions are bad My first choice almost all the time is Debian I run Debian on my servers on my laptops on my desktops Debian is just it's very stable and easy to install and many many of the other distributions you're going to use are probably gonna be based on Debian And you know what it is okay when you first start using Linux To be distro hopping it is normal try this to restore try that distro my first two years of using Linux Like 15 years ago. I every month. I tried a different distro and you know, I'd liked features of this one I like features of this one. I like features of that one and You know when it came down to it almost all them were Debian based and I realized well if I just start with Debian I can add whatever the features I want from the other ones in most cases and that's just how I am I like to start with a somewhat minimal system And and build from there if you don't want to start with a minimal system here might maybe you especially if you're new to Linux You want something that already has all the basic stuff pre-installed office software music software all the drivers You might need in that case I personally my suggestion today and a year or two from now may vary but lately for that I would suggest MX Linux And that's MX. I'm assuming you pronounce it MX Linux And I that's actually my preferred Distribution for carrying on a keychain. I actually have a multi-boot keychain But it is just it has so many options for running as a live system off a USB drive To where you can save settings and have all these different configurations It's easy to load to RAM and it's just a nice Setup if you just want something out of the box again That's just my recommendation is not the only option out there If you have old hardware and you're looking for a live distro a lot of people would suggest tiny core I personally prefer slit as that's how I say it. It's probably pronounced wrong But slit as is an operating system. That's very lightweight used to only be about 30 megabytes compressed on a CD or flash drive I think it's closer to 40 or 50 megabytes now But super lightweight can load to RAM if the machine's really really old And you have like under 120 megabytes of RAM you can do a frugal boot where I think it's what it's called where it Instead of copying a whole thing around will actually run off your your drive or CD ROM And from as far as I'm concerned as far as live Distributions that are lightweight that is the best but again if I'm going to install something on an old machine And I don't mind taking the time to set up how I want I would still go with Debian But that's just again me so No arguing no fighting comment below. What is your current favorite distro for different situations again? Just like me I like actually on all my desktops and laptops. I read Debian Sid unstable I've been doing that for close to ten years now and have had very few problems, but on my servers I run Debian stable so In case you're unaware of this Debian usually comes in three Varieties you have Sid which is always called Sid and it's unstable Then you have testing and then testing eventually becomes stable and for servers usually want stable You don't care if the software is a little old as long as it's locked down and and stable for my desktop if something breaks I can you know uninstall it and reinstall it you know whatever But like I said, I've been using Sid my kids use Sid my wife uses Debian I think I recently switched her over to Sid just because she was writing different versions of software than I was Because she was running stable, which is going to be a little bit older So I think I last time I messed with her computer. I upgraded her upgrade her. I switched her over to Sid But yeah, let me know what you think And this is not a war. I mean you're using Linux. You're using legs. You got the Linux kernel Everything else you do is up to you. So let me know below Yeah


Everybody forced tier ripping 2021 top scrim platinum anniversary baseball light eight box number 11 random team style There are the results you can always find them a late sports cars calm Good luck on the break Let's see what we got. Yeah, you better be careful in twitch chat Sam Six is a mod.  You are not a mod anywhere. You're all module in YouTube module in both Twins refractor kentamaiata Who's the villain black and white mini diamond braves fill the acro. Let's get that next break filled up everybody Aqua wave blue jays Robbie Ray. We go tweet it out. I forgot to do that We got pristine coming up soon as well if you like some uh Look over some more autos Cliff what's up? Cliff makes his quarterly appearance raves refractor dance v. Swanson 13 months. Dang. I wonder what mine's at. I Got it two days after he started membership.  Why do you say Ryan black and white mini diamond Orioles Cal Ripken jr. Nice Cal Even going well busy, but going well rookie refractor Padres Ryan Weathers knee Okay, so what I know what I said. Oh, I said it differently. Didn't I I like sounded out the whole thing Black and white mini diamond Mets Mike Piazza Rangers refractor Juan Gonzalez Black and white mini diamond Griffin canning a's or angels. Sorry angels Aqua wave Mets Mike Piazza Twins refractor Harmon killer brew Justin feels our paper again. There's dang That's a pretty big hit, huh? Black and white mini diamond a's mark canna You use your government name Sam X factor Mariners Ken Griffey jr.  I double check. But yeah Mariners refractor Edgar Martinez just because they kind of blend in but I've seen boxes here and there With no autos unfortunately Oh, there goes youtube back on uh Restream black white mini diamond astros from braval des Everything just refreshed for me.  No, definitely not sam illegal But I have to be a date.  He is uh doing some it stuff at the shop. Hey, he's aqua wave.   Yeah It wasn't it was a sick part It's pretty nasty.  It was a pretty nasty bee dog Marlins, uh black-white mini diamond rookie louis ds. I think he just likes it so much because brian dawkins is better than ed reed Aqua wave rays pete fairbanks I don't get it. You guys watch Reeves refractor fill negro.  Don't worry Ah lane so you agree I know he doesn't agree.  Yeah chipper and belcher like neck and neck, dude refractor red socks jd martinez.   That's my favorite when that happens lose all that I set up 16 to go Come on guys. Let's get it filled up Okay, bond. Thank you. Thank you Yeah, it was insane. I was like what?  They both have like really similar home run totals and Del tray has 3k hits chipper does not Both good defensive players chipper is a switch hater.  I think I've ever been to I was there a few weeks ago. Actually rookie refractor cubs braily marquez I don't know chipper was from there Hi, he's red sox dany santana yellow orange to 25 Oh, the land. Yeah, it's not for at all black white mini diamond debacks luke weaver refractor rookie royals edward olivaris They both wore number 20 Yeah, I know I'll be duck better Going through my mind. He hit harder boom end of story Black and white mini diamond astros hose al-tube Extractor tigers hose velverde Oh dang, oh dang dude lane always has the hot takes Devers refractor red sox Always with the hot takes lane and crazy out here black white mini diamond royals carlo santana I don't actually believe that guys lane might though They also play different styles, I will say greed and Dawkins Very different styles read was like it go do whatever you want And catch interceptions taken back for for touchdowns, but Dawkins was like After you I think read's better though refractor braves andrew jones Bob Sanders He was really really good before he got hurt. He was like really really good To be fair I know you're talking crazy lane, but I respect it tim salmon black and white mini diamond angels Every player with a fish last name. It's gotta play for the angels. I guess Except uh mike karp. Is that a baseball player mike karp? That sounds familiar to me I was gonna say got refractor twinge j cave probably the angels at heart black and white mini diamond reds johnny bench Dawkins didn't play with a raven. So therefore he's better than reed I think most of us in the dream would agree on that Uh, aqua wave royals Jorge Solaire I don't like the eagles any more than the ravens. I guess though rangers refractor nick solak Best safety ball time everybody knows is Devin McCordy Easily black white mini diamond twins Jorge Polanco zero bias Totally not wearing a patriot shirt currently Rodney Harrison second best got x factor rookie cleveland tristan mckenzie You know Harrison's pretty underrated. I think I don't think he's like an all-timer, but Pretty underrated Fractor Rockies, right man. I think it's because the rest of the defense was so good And usually when the whole defense is good the safeties get like not so much respect Usually unless you're like eddy Black and white mini diamond risotto for the uh tigers I did not bottle. I'll have to check that out I like a good black and white design And I do like those jerseys. So I'm sure it looks pretty nasty I think those alternate helmets kind of been around for a while. I've seen like signatures on them I think but I've never seen them like they've never been implemented to like the actual team Uh, there's just a few numbered cards that I'll go over in this one 25 Danny Santana to 199 colton wong to 70 nomar gracia para To 75 reberto wassuna and to 199. Justin more no That'll do it one more of those coming up next


Welcome to the Thargoid Report, I'm CMDR Buur. As you've probably guessed by now from the appearance of this video after a 5 month absence, the Thargoid Menace is once again on the move. This morning the Galnet in-game news service is reporting massive Thargoid incursions in the following systems, Saleno, Asterope, Atlas, Witchhead Sector DLYD17, Witchhead Sector HWWC19 and Witchhead Sector FBXC11. As a result, stations are now ablaze and in need of search and rescue, evacuation and emergency relief deliveries in all six systems. If you're new to this aspect of the game, here's what's available to you. Each burning station will have a rescue megaship parked right next to it. Those megaships will have missions you can pick up that will pay handsomely for destroyed Thargoids and recovered escape pods. The burning stations themselves will have passenger missions with people desperate to be evacuated. If you want to kill Thargoids, head on to one of the systems listed on screen and search out the active Thargoid combat zones. To wing up with other commanders and also get guidance on how to combat Thargoids, then head to the Discord server for the Anti-Xeno Initiative where you will find all the information you need as well as other commanders fighting bugs. The AXI are also best placed to help with outfitting and ship builds should you need it. Wherever you go, commanders, remember, pick your fights with care. If you want to help evacuate or help with search and rescue efforts at the damaged and burning stations, then head to the stations listed on screen with passenger cabins or limpets and cargo space. As well as evacuating civilians from these stations, you can also help by delivering food, water, basic medicines and natural fabrics to the affected stations. To find other commanders engaged in this activity, then head to the Discord server for the Post Disaster Evacuation Service. That's an entire community dedicated to the relief efforts at Thargoid affected stations. Those guys will also be able to best advise on equipment and ship loadout for that particular mission. If you are going into a burning station, take all the heat sinks. Links to my previous videos on this subject are below. If you want to help repair stations previously attacked by Thargoids, of which there are many, then head to the Operation Ida Discord with the biggest cargo hold you can muster. Those guys are devoted to repairing stations that are no longer on fire but now in desperate need of repair. They'll be able to tell you what to pick up, where to get it and where to transport it to. Additionally, a state of emergency has been declared at Artemis Lodge in the Saleno system and the commodity market there, whilst still open, will now only accept deliveries of food, evacuation shelters, basic and advanced medicines, all of which are fetching a good price. All other services at the station have been suspended. I just want to say a huge thanks to the AXI and in particular Commander Magram for their invaluable assistance in compiling this report. Commander Magram's Evolving Reddit post is the place to head for the very latest information. The good commander is constantly updating it as the situation changes. Links to everything I've talked about today are in the description below. That's it for now. I'm so excited to be back reporting on the Thargoids movements again. To stay updated remember to like this video and subscribe to the channel. Thank you so much for making it this far, we'll be back later this week with more videos. Until then, O7 Commanders, may all your hyperdictions be brief and don't let the horror daisies give you nightmares. We very much look forward to seeing you next time.


Computers keep changing the world, but their power and safety is limited by their rigid design. The T2TILE project works for bigger and safer computing using living systems principles. Follow our progress here on T Tuesday Updates. This is the 26th T Tuesday Update. Let's get into it. 26 weeks, that's half a year. I don't know that I really believed I was still going to be doing this after half a year. I'm wondering am I still going to be doing this after one year? We'll find out. So last week it was a big update across all the fronts and introducing this idea of the Worms movable linked list kind of structures. That was quite a bit of fun. A lot of people looked at it, kind of engaged in it. Andrew Walpole has already updated his MFM.rocks simulator. So it now has a version of the Worms here. We can use N and make a Worm. His Wormers are actually quite a bit more elusive and hard to catch than the ones I was showing last week. You can build walls around them and they jump right out. But they're quite a bit of fun. I'm still thinking that we're going to get quite a bit of mileage out of these Worms in all sorts of different contexts. I want to figure out ways to make the software underneath them easier to reuse so that we'll be able to get more mileage out of the whole idea. But I'm still kind of excited about that. Didn't push on the whole lot this week. Hope to come back to it soon. Where we left off was we were struggling with, are we going to be able to do this Rojas reduction of hazardous substances when we actually make the boards using lead-free solders? Kind of what it boils down to. And ETS, doing that is not necessarily that easy for them given the particular equipment they have. So I was looking for other places in Albuquerque that might be able to do it. I did get quotes. They were not so compelling that it was a slam dunk let's switch. Especially because ETS stepped up. So even though it's more work because basically they're going to need to hand solder the through-hole parts to do lead-free. They're going to do it at the price that we had already talked about several months ago. So I think that's pretty much a lock as far as I'm concerned. ETS for the win. I've gotten with UNM to get this whole purchase order thing set up so that we can actually get them paid. There's any number of things that can go wrong as we've already seen all the way along. But it's possible we'll actually start to get these tiles assembled as soon as next week. Perhaps not before I talk to you again, but in the week coming after the next episode we shall see. That has been a very long road. What else? Oh yeah, okay. So the 3D printing. I'm sure you're as tired of this as I am. But here's the news on that front. I was getting these ERM intent bed errors that was causing me to lose prints and it was very frustrating. And I talked to the warranty people at Prusa Research and they were telling me I had to take the board apart so that I could look at this thing. And I was trying to look at it and it really looked fine. And I was much more concerned with this little place where the cable containing the power supply to heat up the print bed so that the prints will stick better and stay flatter. Because it seemed to me that it was something wrong there. And I had opened it up. I had fiddled around with it.  I closed it back up. And then it seemed it was actually working again. I was getting successful prints of three avoiding that back corner because that seemed to cause more trouble. And I got several good prints out of it. Oh yeah. And actually as I was recording last week's T Tuesday update a triple three cases were printing in the background which I'm going to try to avoid doing. I'm not printing anything right now for example because when I listened to last week's episode with the headphones it was kind of aggravating because I could hear them in the background. But in fact this was what was printing.  So that was pretty good because I don't trust the filament outsensor on this. I didn't need to. However, and I got another one eight hours later and another one eight hours after that. It's great. Until it wasn't. The air tempered mint tempered air came back. This one was not very terrible. It was you know barely started the print. So that was great. But then shortly thereafter I had just changed the reel and was working on it. And this one this one lost about six hours of printing time plus a lot of plastic to get it air mint tempered. So at this point you say well come on. I cannot keep doing this if this thing cannot get fixed. Either I have to send it in. I have to give it to somebody or at this point in the Ackley family there's this thing that once we declare an appliance officially dead. So that like you know first do no harm. Well now I can't do any harm because officially dead. Then I can go in and I can screw with it. And sometimes it actually comes back to life. This is the reanimator. Well so the Prusa I3 Mark III was getting to the point of being declared dead. So well first I took some of the cap on tape and I wrapped it all around the thing trying to keep the thing from flexing as much because that really seemed to be where the problem was. And in fact this was just the reverse. So taping it up like this meant I got air mint tempered airs almost immediately. And even before I tried to print anything and so forth. So on the one hand that's like oh terrible. But on the other hand that was basically all but proving that I was right that it was that something about the cable bed interface that was causing the trouble. So I went back I took a look at it. I opened it up again. This time I did not get deterred by the fact that the fabric cable wrapping was sort of sealed down at the end. I just cleared it out. Opened it up and sure enough right in there. This double black cable is the thermistor sensor wires. The big heavy red and black cable is the power cable for heating the bed. And it went right through it and right there it was really squeezing the thermistor cable.  You know the stranded wire but you could feel like oh man this thing has really been under stress. Well so since it's dead I opened them up. I cut one and I also took it out from being in between these two things. It's like that didn't seem to be doing anybody any favors. I stripped the ends. I got some stranded wire of my own cut a few pieces. Fired up the soldering iron. Twisted the new piece of wire on, soldered it down, crimped the things in a little bit. Used the hot air gun with some heat shrink tubing and made a replacement little jumper. Did the same thing for the other wire. Soldered it up. Heat shrunk it down. Closed the whole thing up. At this point I left the textile cable wrap. I didn't try to stuff it through the hole. I couldn't believe that it's better if I did because it would kind of keep the wires from flexing quite as much. But I just assumed to see it if they're actually flexing so much that they're going bad. And here it is back mounted up again where now you can see the cables as you couldn't before. And I got a beautiful print no problem. Eight hours later I got another one. After that I said hey let's try the four up again. In ten hours, well ten and a half hours, I had four up. I'm using the entire print bed again. This thing is fixed as far as the Irmintent bed error goes. It's still got the problem with the print fan thing being mistakenly detected as not running. I'll bet you a buck that it's the same kind of problem up in the extruder head. But since there's a software switch, just don't bother checking the print fan. At the moment I'm just saying don't bother checking the print fan. Let's go. And then another four more. So now they're coming out. And so that's pretty good. I think, you know, I didn't want to go to this next level of relationship with my printer. But I have now done so. So I think we're going to be able to finish, except for the fact that there's a ton of wasted plastic. I've put it in order to get another couple of rolls of the Prusament Galaxy Blacks, the same stuff that we're doing. That hasn't shipped yet, but it should be shipping reasonably soon. Hopefully before we run out of the last reel that we got here now. So that's good. On the rest of the parts, in addition to the cases, the main thing was these glow rods. This was a picture I showed back in February when I had just cut a bunch of acrylic rods into these little pieces. So that one piece goes over each LED, which is way down at the bottom of the circuit board. And the light comes up to the top of going through the acrylic rod using internal reflection. So each case needs two of these things.  By the end of March, I had run dry, ordered another set of them from Amazon. They showed up in this past week. I cut a bunch more and we're back in business on the glow rods as well. So really, you know, things going pretty good as far as finishing up the physical hardware that stuff. The cases that we can do aside from the circuit board assembly. The one other main thing that we do have is the intertile connectors. We need the connectors between them. I also showed this earlier in the year back when we were dealing with the analog signal noise that we hadn't diagnosed correctly. So I was trying to make an intertile connector that had this special little mouth to put down an array of serial resistors, which series resistors, which in the end I thought were actually not necessary. So last week I sent off a cleaned up version that got rid of the series resistor network in the middle and just generally simplified things and cleaned it up. And those things arrived from Osh Park as well in another one of their perfect little perfect purple packages. And here they are got nine of them. And they're pretty much the same things that we saw before except they have actual less on them since there's no component. Each one of these things takes two of these keyed headers.  After they've soldered up and flipped it over, T212 PD, power and data. These are the full connectors that we use within the Lotus. The word we're sharing power and data. We're going to have the DOs, the data only that we use between the Lotuses separate from these also have to deal with them. There's a lot more PDs than DOs. So deal with the PDs first. So I started up three of them. Here they are. And here's one of them in plugged into the position in a tile. And you can see the thing is way below the tile surface. So if you had another tile coming in here, there's like no way you're going to be able to get these things out. That's why we have the 3D printed holders. Here are three of them. These were stuff that had been printed up ages ago that had just been sitting in a box. Each one of these things consists of three pieces. It's got the finger tab that you grab onto. It's got the loop that goes around the circuit board. And then it's got the little cap that goes on top. And so here it is. Here's the loop going around the circuit board. It's actually keyed. The loop has a little notch in it there to line up with the notch that the keyed header has. Now this actually was showing that there was a bit of a problem that when I tried to get the U to go through the slot in the circuit board, it was really tight. And I'm not exactly sure why it was so tight just on one side. So that may need to be revised. I could either make the 3D printing width a little bit less, but I don't want to do that because I need the strength. But if I make the gap in the circuit board wider, then I lose copper, which I wouldn't really like either. So I'm not sure exactly what I'm going to do there. But eventually I managed to get it seated all the way down. Here's the U thing pulled all the way through. Here's the finger tab with the holes that those things are going to go up through. It's hard to tell, but if you look here, right here, there's actually a notch in one of the finger holes. One of the U tabs that comes up, but not in the other one that actually keys into a slot on the finger tab. So in fact, this thing actually only orients one way, at least when the 3D printing is being accurate enough. So it goes in and the two sides of the U come up through the thing and they're sticking in there.  It works pretty well. And here's the cap going on that pushes the U arms apart and there it is completely seated. And so here's a final, completely assembled one with the U strap going down around the piece. The finger tab up on top and the cap holding it all together. Another angle. And here you can kind of see how it jumps around the key and the header. And here's what it looks like from the side. I feel all right about these things, although I mean they are kind of tall. So it's one of these sort of function versus vision sort of things, right? I mean, as it stands now these things stick up a fair bit above the surface of the tile, which in a way is an elegant and if you have a low angle vision on it, it kind of gets in the way. But on the other hand, the whole point is, is that you need to be able to grab it so that you can pull it out. It needs to go up above the level of the tile. So I think it's all right. And yeah, and here's another one where it was really kind of jammed coming through. I had to push more than I wanted to. And in fact, I busted one of the U's right across the part where it's the thinnest, where it's cut away to go around the asymmetric key. So that's a problem. So either I have to, if I make the cut wider, then I'm going to lose copper. And this copper is actually carrying power or ground back and forth. So I don't want to lose more than I need to. We'll see what I'm going to do about that. All right. And okay, so we're six months in the next six months. Well, I would like to say, I think at this point, we have maybe a month, a month and a half, two months tops. We should have the boards assembled, the cases, power supplies with intertile connectors so that it's going to be much more a matter of software. There's a lot to do on infrastructure software, let alone the higher level stuff like the worms and the cells and all that stuff, which is what I really want to get to. By the end of the year, I want to be up at worms and cells on the grid. I would like to, we were talking about this some in the past week in the chat room about ways of maybe being able to live stream the grid and being able to get people to maybe sign up to run their stuff on the grid and then see it live stream back, something like that. I want to get as many people involved as possible. I would like, in fact, to figure out a way if it would help, if there would be people who would be interested and people who might be willing to invest some time and effort to sort of do a programming class online. Sort of, you know, here's how to program in ULAM or here's what we know about how to program in ULAM and SPLAT. If you're willing to spring for a raspberry pine or run the simulator if you haven't got a UNIX box, a Linux box of your own, you know, okay, you're going to have to invest 40 bucks or something like that to get the hardware to run it on. But then maybe we could meet weekly and try to get exercises and so on and so forth, kind of make our own little class to see if we couldn't learn how to program this stuff. I would like to explore that if there's any interest. I don't know. But we've come an awful long way in a half a year. I feel good about where we've gotten to and it's not an anniversary, it's a half an anniversary but it's sort of like a happy T Tuesday this is from last year but I don't think I ever showed the picture before. So I think we're doing great if we can build this grid and get it running in a month, month and a half, two months tops. That'll be good. And then we can move back towards software. And maybe, you know, I would be happy if we can get to the point where we can declare victory on T Tuesday updates and say, you know, let's have a series finale and then move on to something else, you know. We'll see how it goes. Don't know yet. Thanks everybody who's been contributing, supporting, watching the videos in any way it really helps. The next video, the next update will be out in a week. Hope to see you there.


Kansas City is capable of. So let's try that one more time. Good morning. Exactly. So hi there. My name is David Blankettle, and I work for a company called AppSara. And one of the things that I tend to hate the most in life is when you go to a talk or someone says I'm going to give you a talk and it's supposed to be a technical talk and it turns into this marketing talk, right?  I cannot stand that. So given that, I want to say sort of a proviso, which is that I will probably want to say some things that sound a little marketing-y, not very much. And so here's what I propose to do. I have here these three wooden blocks, red, blue, and yellow. What I propose is every time I want to say something that is, you know, could even be construed as being sort of like a marketing sales-y thing, I take away one of these blocks. And then if I've run out of them, I cannot say a single marketing thing anymore. So this way you know that my talk is not going to be all that. Can we agree that this is a fine and dandy system? So let's do it. So I'm going to take a little one at the start to tell you what the company I work for does. Okay? I think that's reasonable. Yes? Okay. So I work for a company called AppSara. They're in San Francisco. They make this software that allows you that DevOps love because it allows you to sort of take whatever work that you want from a shell script to a container to an operating system, toss it to the public clouds or run it on prem or move it around. And there's a policy engine in the middle of it that allows you to set up these policies. And we might talk a little bit about policies in this particular talk. You'd be very surprised that that will show up. So that's all I want to say. So let's move on. I think the best way to start my talk is to go to the end of my talk. And the beginning of my talk and the end of my talk is talking about production. Because in my opinion, production environments are all about trust. It is super important that you're, that your thing works. It is super important that you understand in production what your workloads contain. What are you actually running there? You know, that's kind of important. It's really important to know what can whatever it is you're running. I'm using workload as sort of the generic way to say things. What can I consume? What resources? What CPU? What memory? You know, what network bandwidth? That sort of stuff. You might have some constraints on where your workload runs. If you're dealing with EU data protection laws, they can't leave Sweden. Or if you have this machine over here that has lots of memory you want it to run over there. Or maybe it is you have this server that you have that you run all your PCI stuff on. So you want to make sure that you can determine where it runs. And finally, and perhaps one of the more crucial things is you need to know what your thing can talk to. It really is important to say, okay, this thing can talk to that and that's it. Or this thing can talk to the internet or the internet can talk to it. But it's really a bummer in production if you find out that suddenly the thing you're running is somehow talking to large swaths of the internet and you didn't expect it. Right? So that's really a bummer. So you have to kind of pay attention to this sort of stuff. And I think everybody here knows that the bigger the deploy you have the harder it is to know all these things and to have to maintain this trust. And if you're doing multiple clouds, which some of you here, is anybody in this room doing at least one plus clouds? Yeah, like so. So at least like a good 30%. It gets really, really hard. So what I want to do is I want to come up and tell you something I think that will help with this sort of stuff. But the problem that I have is that the thing I want to talk about typically gets associated with like a sleepy time thing, right?  But I want to let you know that I won't let that happen. I promise. So what I want to talk about, and I think part of the solution is this one little word here and for those of you in the back on your phones, maybe this helps. Okay. So this is what I want to talk about. Now, when I say policy, invariably people have this reaction because they start thinking about these awesome things like the CBB security policy and procedures handbook or maybe they talk about this one, which I highly recommend you wait till the movie comes out for, you know, like fiscal policy or maybe even your employee manual, which is just rocks. Now, I know I bet there have been people in this room who have had to sit in on meetings where you're deciding policy, right? Right. For your organization. Can you raise your hand if you have? I just want to know it will help.   Right. Or if you've really been doing it for a while, more likely that your meeting looks a lot like this, right? Right. And so I want to suggest that it doesn't have to be that way. I want to suggest that it is possible to have policy be more sexy. Okay. Then just what I'm saying. And those of you who are at the corner is come on in and there's plenty of space up here. So you know, you can come in. So here, let me prove to you can be sexy. Here is a diagram for policy that my marketing group made. I don't think that counts because, you know, you could make that too. But if you don't think that's sexy enough here, let's do this. Okay. So does this give you the sense of just how sexy policy can be? Because we're going to stick with the music for just a little while because I like it so much. Okay. So here's what I'm going to assert. Chances are that your environment looks a little bit like this, right? You have this long road going straight down that way. Or maybe, maybe just maybe your environment looks more like this, right? Couple of curves in terms of like when you're trying to get to production or possibly like this or more like that. Well, I'm willing to bet actually that your environment probably looks more like this, right? Now, one of the things that you may or may not have paid attention to when you saw these pictures, if you were watching is all the pictures have these things. What are these things? Guardrails. Exactly. So here's the point that I want to make to you is we're going to be talking about guardrails because if you can set up guardrails for your environment then it is possible to allow whoever is using your stuff to do what they want and you can sleep at night because they can't do anything that you didn't say they can do, right? So this is why I think this is important. And in fact, I'm going to ask you to go demand this sort of guardrails from all of your vendors, from all your open source projects, from all these sort of things. Now, just because I know what kind of crowd this is, who can tell me where this slide comes from? Yes. This is why I love people so much. My people, you know, it's so great. Yes, it is indeed from young Frankenstein. You're absolutely right.  The situations you have that you might care about is like when a developer wakes up at 2 a.m. goes, you know, I'm sure more memory will make it work better, you know, lots more, right? Or, yeah, the fact that you're chuckling is a bad sign. Or now we're a public docker image, what now? We're like, so like, I don't know, did you know that the official MySQL image, it probably still does, had shell shock in the middle of it. Doesn't that sound great? Go run out of production. Go, people, go. It's awesome. Or, you know, all of a sudden your container is talking to, I don't know, shouldn't be doing anything. Or the new open SSL exploit is called like, I don't know, Shave Fuzzy Bunny or something, right? Right? And we all have to deal with that. And are we vulnerable? I don't know. Or what version of Java are we supposed to be using in our environment? You want to be able to constrain that. Or here's even better one. Who has the database credentials? It's in a spreadsheet where, and what can those credentials do, right? So the question I think that is reasonable to ask is where is your policy in your environment now? In my experience, people have one of two different kinds of environments. First off, they often have a department or a person or a group of people whose job it is to handle sort of the compliance and the policy and stuff like that. And they're like the customs guard. Their job is to say no, right? At the right time in theory. So the problem is, is that doesn't scale or check. It means that every time you want to do something, you need to go talk to this person. If there isn't any of them and there are any of you, by default you're gonna have to queue. And that doesn't scale. So it's maximally frictional. Or, in my experience, people go with what I would call the Wild Wild West, right? Where anybody with a credit card can provision infrastructure and go get what they want. Okay? Now the problem with the Wild Wild West, for those of you who watch Westerns, is that invariably somebody takes a bullet. Like a straight bullet. Like, they, oh, darn, we forgot to shore up the mine and it fell in. Or, you know, somebody forgot to back up that database or whatever, right? And so that's not so cool. So the tricky thing is, is that what invariably happens is when you have the first kind, often people go off and try to do stuff on their own. If the first kind is so frictional, people go off and do the shadow IT thing on their own, right? Like you've seen it where they go off and provision their own stuff, right? And then congratulations, you have the best or the worst of both worlds. You win or lose, you know? So what would be better? So my opinion, what would be better? And this is by the way cosplay, so I can show you that one. It's not, you know, not required. I would assert that if you have something that was pervasive, you know, like everywhere in the things that you wanted to control that was explicit, so you could be really super careful about what it is you want to state in your policy sort of world. And this is the key, this is the kicker. It needs to be automatically enforced. If you have a situation where you have a lovely software that handles policy and every once in a while it goes, is this okay? How about this? Is this okay? Like it's not worth anything, right? It needs to, it needs to, you need to let the machines do what the machines do well. Let the people do what people do well. Like Todd Underwood, an SRE manager at Google says, you know, stop feeding blood to the machines. And I really truly believe that. So let's talk about what you would need if you were going to do this sort of automatically enforced thing. So first off is the easy one, right? You want to be able to say, I want to constrain things in terms of CPU, disk space, network usage, number of things I'm running, or maybe I want to know how memory all together, you know, stuff like that. It's important to be able to control workload to workload stuff. This thing here, my app server, talking my database, that's okay. These two things can talk and only they can talk.  I think it's super important that when you're giving permission on these lines that it's really granular, that it's per port, not per container or VM, right? It is the case that you want to make sure that if this guy is talking to this guy, and this is the app, and this is the database server, that it can only talk on the database port, right? Because the reason is, is if someone pops your database server, and it happens, right, they can, if you have this lovely transit of trusting, go attack your app server. But if in fact you've only said only these things can only talk on that port, then your attack surface is much lower. And I think that's important. And per protocol as well. You want to be able to say, but you want to be, you want to be able to specify, right? So this automatic bi-directional trust, because this is what we often do, we often say, okay, I'm cool, this thing can talk to that thing. But what that often means is that thing can talk to this thing in the same way, and that's not necessary, and that's perhaps a less good security posture. Okay, so we talked a little bit before about ingress and egress. It's really important to make sure that you can control what comes to your thing and goes out from your thing. If you can't, that's bad. External connectivity and routing, if in fact you have something that's providing a web service and you want to move it around to another cloud, you better have a way to redirect when something comes in for that URL. Instead of it going to this thing, now it's going to this thing over in that cloud. You need to be able to control that. Ideally automatically. You know, when it comes to multi-cloud stuff. It's really super nice to be able to say, only allow this version of Java in production. Or anything that is currently running this version of Java in production can keep on running, but don't allow anyone else to run anything that is of that version. Because you want to be able to retire stuff. Right, so having that sort of stuff is cool. You want to be able to say things about what is allowed to deploy in terms of CI-CD systems. You want to be able to say, okay, only things that have passed a security check are allowed in production. Or only things that don't have personal information in it, PII in it. Or maybe you want to have something that says don't allow the letter E in any of my code. You know, whatever it is, whatever your business needs, you need to be able to control that when it comes to deployment. And here is one of the tricks that nobody pays attention to usually. If you're in a situation, and I bet you've had this situation, we have a developer and she is trying to debug her application. And that application talks to a database and she's like, you know, I can't get this thing to work. Can you please give me, can you please tell me what transactions are going on on the server? So your choice at that moment is one of three things. One, give that person direct SSH access to the server. Do we all like that? Yes? Is that good? Yeah, okay, good. I could, the sarcasm is dripping. Or you give this person a copy of the logs, but that's kind of static, right? And they want to run more stuff. So congratulations, they come to you n times, where n is potentially infinite, right? Or you set up something else. And I'm suggesting you want to have some other way to give them access, to allow them to say stream their logs, if you can, so they can see it. So you want to try to build that. If you don't have that now, I bet you want it. And clearly we're talking about policy, so you need to control who can edit it and when. Okay, now what I'm going to do is I'm going to take another one of these away. Can we agree that it's okay? Yes, everybody cool with that? I just want to say about one thing that our stuff does that I haven't seen before, and if you want to go implement it, go for it. I think it's a great idea. It's not, it's, some people, when they talk to me afterwards, they say, oh, that thing that your thing does, and this is only one of the cool things we do, but it's one of the ones that makes me happy, so I want to tell you about it. It is really cool if you can say, I've got an application and it's talking to the database. If you can have something that will stick, they don't like me to say man in the middle because that gives a bad connotation to it, but you all know what I mean when I say like, I guess the proper term would be inline component. So you have the application, you have this thing that we'll put there for you, and then you have the database. And your application talks to this thing, this thing talks to the database. Now what we can do with that sort of stuff is first off, the real credentials to the database can live in this thing, and it can have a federal credentials that are only good for the time of that discussion, which means that if your developer were to check the credentials into GitHub perhaps, or something like that, it doesn't matter because the credentials don't mean anything, they're only good for that particular connection. The other cool thing that is also really cool is we can do policy right there. So we can say things like, don't ever let my app drop a table. And what will happen is your app can send drop table, drop table, drop table as long as you like, and we'll just throw that on the floor. Or we can introduce artificial latency. Do you want to test like latency monkey? Do you want to test whether or not your application works well when your database gets bogged down? You can do stuff like that. And all sorts of cool stuff you can do if you get in the middle. So I think that's just a cool pattern. I suggest you check it out. Okay, so what did I leave out? I don't actually like this, I don't actually like this list.  Let's just give rid of these. What did I leave out? Let's actually go here.  Oh, no, no, that's not the way it works. No, no, no, this is not like prayer. Okay, I want you to participate. What I want, I guess, sorry, that's going to get me in a weird place. Let's not talk about that. I want you to tell me what I left out. What do you think you need in the land of policy that you really want that I haven't discussed? And I'm cool with output silences applying the policies. So you want a better way to apply policies, okay? That's good. I like that. Number three, these guys are working. This is good. You need a way to communicate policy. That's really interesting. Okay? No, I totally mean it. That's an interesting approach. I mean an interesting thing that I think we should think of. Obviously, you can tell I can spell communicate. Let's pick that one. Oh, come on. Let's see. Okay. Well, I think that I asserted that I said I automated enforcement. So let's just assume that's in that, right? Because I had that picture of the RoboCop. I think that counts. What else? But I mean, I keep on going though. What else? One at a time, please. Updates. You want to figure out how to handle policy update? I agree. What else? There were two at the same time. Okay, tell you what, I'm going to call that doc. I'll tell you I'll use your term. Totally fine with that. References? Yes. Okay. Let's get one more. I'm sure there's more. Someone behind me. Someone's up there. Go ahead. I heard testing. I want to write that down, but tell me what you mean by usage so I can capture it. Oh, yeah, you want some sort of auditing, right? Auditing, stuff like that. Okay. So I think that's actually no, no, no. Cut it out. Cut it out. Stop mirroring. Oh, we did stop mirroring. Excellent. Okay. So five other things that I think you really want to have in any policy system that you use is better way to apply standards and references. Policy. Oh, that's horrible. I cannot leave that on the slide. Sorry. Why didn't you guys stop me? You were sitting right there. It's not. Yeah, that's, that's true. Just ask my spouse. Testing, right. Exactly. Testing and auditing. These are things that you have to absolutely have. I'm glad I could share that with you. Okay. So instead of being annoying and just not telling you where you can actually find this sort of stuff, let me give you some idea, but unfortunately, I have some bad news for you. The bad news is that you're not probably going to be get this level of granularity of policy from your cloud provider if you're going to go to them. So Amazon is usually ahead of the curve on a lot of things. They have the ability to set instance parameters and other stuff like that, ACLs like that, but it doesn't give you the granularity that we're talking about. Like you can say, I only want this kind of, this kind of EC2 instance, but you can't be more specific than that. Azure is getting better, but when I made this slide, they only had role-based access control that had three-set roles, and if you wanted another role, it was great. We have these three-set roles, and if you really want another one, you could get those three. So, same with GCP, which is now GCP, where they were just basically saying, hey, if team members have edit permissions, congratulations, they can do stuff, which is not exactly the level you want. And I don't know who here has the pleasure of working with SoftLayer. Anybody? Okay, so if you've not worked with SoftLayer, when I actually contacted them and said, hey, where can I find policy controls in your system, they said, well, it's actually, you know, whatever you can set in the GUI is going to be fine for you. And so I went to their GUI, and there were like 70, and I counted them, some odd checkboxes. Not all about policy, but just in general, and I thought, oh my lord, like, you know, it's so many checkboxes. So, yeah. But what about your platform? Okay? Anybody know what that is? So, the bad news is, they're getting slightly better, but in terms of, in the very, very latest release, but not really. There isn't really anything there when it comes to this sort of policy sort of stuff. For reasons we can talk about. This one, let's play, let's play, guess that, guess that thing. Which one? Stack or Shift? Come on, folks. Okay, thanks. Yeah, not yet. So, there is some work in this world called Congress. And what Congress is, it's meant to be this sort of generic policy engine. And the way Congress is supposed to work is that all of your components get feed their logs and other stuff to Congress. And Congress will then say, oops, somebody did something wrong. And then maybe it can run some sort of linearization script. Now, that to me isn't sounding like what you really want.  It's not the case that sometimes, sometimes they can prevent things from happening, but often they have to show up after the fact and say, I'm sorry, let me help you. So, I don't think that's the way you want to go. And I want to pull my last one here. Oops, sorry, not yet. I'm going to pull my last, not quite yet. This one? Sorry, we know, who is this? Yeah, so Kubernetes is actually a little further along than both of these in that it has things like quotas and stuff like that. And they're starting to add some role-based access stuff to it. It's getting better. Okay, here's where I pull my last one. Okay? It is the case that this is something we've been thinking about for like, you know, four and a half years at this point. And if you want to sort of play with policy and action, you should definitely check out the stuff that we do. And there's a free version that I'll point you out later if you care about. But the thing is, is that we have a platform whose whole idea is to stick policy in the middle. And what could you do if you have policy? And I want you to play with that at some point. So I think what I've just done is given you your own pitchfork and your own torch so they can go to all places. And I don't mean just to me, but go to everyone out there and say, where is your policy control? Where is this sort of stuff there? I want it, I want it, I want it, right? So now you have your own thing. And with that, I'm going to get, oh, I'll point to this. If you want to actually grab the free version of our thing and play with it, it's that you're all. But with that, I think I'm going to come to the end. Oh, and before I do, one thing I should mention is, actually, because I'm a DevOps person who had another block in my pocket, just in case. Anyway, thank you very much. And I used to do a lot of role-based access stuff for some in Netscape. And when I first looked to Amazon, what I saw was IAM. And when I looked at IAM, I said, well, there's my role-based role management in terms of defining a user and then driving that user back into the system at the code level to say that, okay, developers, this is the user, this is the guy that does this work. Right. I can shut them down at that level. So how does IAM, those things, fit in with some of the other things? So IAM is the closest thing, I think, to what you want in that day. They do have, they do have more obviously, the ability to do this. I think the thing is, is that you want to be able to tell sort of more complex stories because sometimes you want to control down at the user level, but sometimes you want to control down at the environment level. Sometimes you want to say, in production, this is okay. In development, this is okay. And those could be different things, but that's not per user, right? Or maybe it's per team or maybe it's this year or maybe it's this project. And so you want to have some sort of ability to be more expressive. Our stuff uses a policy language to be expressive because you really want to, you want to say more than just, this person can do X because it's very complex. It also gets really tricky if this person is on two different teams, right? And now, okay, great. You know, like, what does that mean? You know? So, up another mic, pointing at mic, yes. Other questions? I saw another hand go up. If you could do a smaller edition of my way, I'd appreciate it. No. So it sounds like you, there were maybe a couple of different categories of policies that you talked about. Yeah. So with the men in the middle, sort of like a messaging policy between microservices, obviously like admin type provisioning policies, what other kind of categories of policies would you consider to implement? So, okay. So I started off with that sort of notion that there are kind of four things you want to control. What can you run? You know, like for everyone, what can you, what can you run? What can it talk to? Where can it live? And how many resources can it consume? And so you basically take those four things into every one of your little realm, every one of the realms that you're talking about. Like as you said, exactly microservices are between applications and databases is one place. Provisioning you want to think about and using stuff. You also want to think about communication. You also want to think about when you move stuff around. Ideally it's, you need your policy system to deal well with moving your workloads around. Like if in fact, if you moved your stuff from AWS to GCP, because let's say, let's say Google is having a fire sale, right? And you just, you want to do some sort of cloud arbitrage. Everything has to be true over there too, right? So I think that there's, so I think that there are, there are other realms and I think it's kind of environment specific as to where you want to apply it. And that's why I like the idea of language because language is a very expressive and it can be used in, you know, we can use, we're using language now in this context. It would be a very different context if we were outside on the hallway and I was yelling at you because you didn't wash the dishes, right? But the same language is going to hold for both of those. And make sure you do the dishes. Yeah. So how do you do with that, Spain millionaires? I think you're saying, right? Is that what you're saying? Or something like that. Yeah. So there are two ways that, there are two ways that I know that you can do that in various places, including us and like Kubernetes, do have this. Thing number one is do what you're talking about, which is export your, export your logs after some sort of thing that consumes logs, right? And that could be, that could be, I mean like, it's not free in user time, but that could be like an elk stack or it could be like super spiffy, spunky, please give me the thing that has the, the jewel encrusted, you know, log management system. So that's one possibility. The other possibility is you can build into what you're doing something that allows you to essentially let somebody have the ability to tail the logs of whatever's going on, right? So in our thing, you just say APC job, job log, and it's going to show you everything that's coming out of standard, standard in and standard error, standard out and standard error, right? Because it's just built in to know that it's attached onto that and send what the contents of what's coming out into that container somewhere else. So either you built it in or you export your stuff, in my opinion. But what you don't do is you don't, is you don't copy your logs to somebody because there's, that's for a, for a number of reasons in addition to the like it's static, I mean it's fraught because like they might have some data they don't need. And what you don't do is you don't give them SSH access in, you know, as awesome as they are. In my opinion. Is that, is that good? Oh, thank you very much. Thank you very much.


If you're sitting in your English language trip, you want assessments, let me walk you through what to expect from this paper. Remember that this is the fiction paper, therefore you always get one unseen fiction extract and you've got to answer four questions based on that extract and the fifth question is creative or descriptive writing. It's always a choice, don't do both questions. Now in terms of how to manage yourself through each of the questions, remember that question number one is a statement question where you find four statements that are true based on the first paragraph, spend no more than five minutes on this question. Question number two, this is the language question. This question's worth eight marks, therefore spend no more than 10 minutes on this question aimed to write at least two paragraphs. Question number three, which is the structure question, write at least two paragraphs because it's also worth eight marks. There's four, spend 10 minutes on this question. Question number four, which is the student statement question, try to aim to write at least three, if not four paragraphs. This question's worth 20 marks, therefore spend a minimum of 20 minutes on this question. And question number five, which is half of the paper's overall marks, which is 40 marks, spend 15 minutes on this question.


From the Walt Disney World Swan and Dolphin Resort in Orlando, Florida, it's theCUBE. Covering Splunk.com 2016, brought to you by Splunk. Now, here are your hosts, John Furrier and John Walls. Well, welcome back to Orlando. We are live here on the show floor at dot.com 2016, here on theCUBE, the flagship broadcast of SiliconANGLE TV, where we extract the signal from the noise, shows all across the country this week. Of course, we're here with Splunk. And along with John Furrier, I'm John Walls, and we're now joined by Chris Kurtz, who is assistant architect and really a huge advocate, Splunk advocate at Arizona State University. So, Chris, glad to have you with us. Thank you very much, glad to be here. We could talk about three dozen things with Chris. We gotta tell him what we just talked about. So, yeah, we'll get to the Splunk stuff in a minute, but they've been at Arizona State 14 years. 10 of which were spent working on various NASA projects that dealt with the Mars rover project, which I'm just fascinated by that you were involved and Arizona State was integral to those projects. Absolutely. I worked for a group called the Mars Space Flight Facility, led by a scientist named Dr. Phil Christensen, and he's a NASA researcher. Had four instruments in orbit or on the surface of Mars at the same time. And I ran, I was the computer guy for him, so I was the assistant manager, and I worked on Spirit and Opportunity, both of the older rovers, and worked on Mars Global Surveyor and Mars Odyssey, so I did that for a decade. So, when you told people, yeah, I got a job that's out of this world, you really meant it, you really didn't have a job out of this world. A large number of scientists have graduated and moved on to other fields and stayed in geology and continued to work with JPL and NASA and other NASA groups. And so, there's a lot of people out there that I helped get their PhDs. My son's at University of Santa Barbara at Physics major and he's always fascinated with the whole space concept and he's so interested. So, are there a lot of young kids coming in? They must be fascinated by all the science now has changed. Absolutely, and as a university, our job is to train these kids and help them get future jobs and both undergraduate and graduate degrees, PhDs, et cetera. That group is really focused on trying to get as many young people involved as possible and make that available. That's cool, well, I mean, you certainly got a challenge. When you say you shipped your product, you definitely ship it out of this world. Yeah, no maintenance on that. That's beyond FedEx too, I mean. You're hanging around the Splunk trust. Yeah, I shipped the product into space. What have you done? Well, I put it on Amazon. But I mean, all kidding aside, this is the fun part, right? So, you've got a job that's real world, you've got real instrumentation out in space and that's something you're working on. But behind is the data. Behind is a lot of stuff that's the computation. Your day-to-day job requires data, simulations. You probably have some cloud on, super confused on demand. You need to simulate, you need to do stuff to get to where you're going. How are you using Splunk? How is your job changed by Splunk? Has it changed your role? How you approach it? Yep, so Splunk was brought into Arizona State for the security group to pull information from our operations group real time or as real time as we possibly could. I came in at that level at the very beginning and have shepherded Splunk into a full-blown enterprise product. We started as a 50 gigabyte customer a little over four years ago. We're at a terabyte now and I've really been able to architect and shepherd Splunk into its position now. I work for our jeopardy CIO directly in the data analytics group and our goal is to make Splunk into an enterprise tool that the entire university can use, not just security, not just operations. Everybody's going to be able at the university to use it and hopefully eventually even researchers like the Mars Groups will be able to use Splunk. It's funny Chris, take a step back as you also have an instrumentation background legitimately instruments in space but instrumenting an enterprise in a digitized way is really where Splunk's winning. Absolutely. People want to digitize and understand the data, the digital assets flowing around. How do you get that done? How do you become the disruptor, the agitator, the innovator, all kind of rolled into one because you got to kind of get that sphere in there and clear the way, right? I mean, how do you get that done? Yeah, so we started with an actual need. We had data that was in operations and that data needed to get to the security group in a timely fashion. And so we started there and then as the security group used it more and more, we turned that on its ear and turned back to the operations group and say, look at how good this is working. Look at how much simpler this is making your job. Let's bring in more data. Let's bring in new sources of data. One of the common questions about Splunk is always what's the ROI? I need use cases. I'll tell you, the best way to get use cases is hallway use cases. You're standing around with your coworkers in the hallway while getting a drink of water and you say, I wonder if we could take this bit of data and if we could combine it with this bit of data and we could do something new with it. And almost every single use case that we've come up with has been this, I wonder if we could take these two pieces of data and combine them. And then also, well, that's kind of the intoxicating conversations. People are like, oh yeah, let's do that. But then the ROI may fall down and say, well, I got access to server or, so the risk is, ah, but now Splunk solves that problem because you create a separate Splunk instance, right? So we have one Splunk instance for the entire university, but we segment the data into operational units into indexes so that the firewall data is in one index and we can control who has access to it and the server data is in another index and we control who has access to that. That allows our information security office to be clear about who's seeing the data and what's important and only the proper people are seeing it. Does that mitigate the risk kind of fear, if you will? I think that mitigates the risk and fear a lot. And one of the things that I love about Splunk is that as an audit tool, it's very comfortable so that I can turn around and I am missed compliance or I have other compliance and I can say, yeah, we're using Splunk, we're compliant, we can keep the data separate, we can keep it for as long as we need to. That's nice insurance. Absolutely, and we can also use Splunk as both the carrot and the stick. I was recently told by somebody that I was the carrot and the stick. So the carrot is look at all this great data that we're going to bring in, it's going to be fast, it's going to be reactionary, you can use all the data in any way you want, you can produce these awesome reports but you're going to get held to the fact that the data's in there and if the data doesn't show things that are working well, you're going to see that too. You're accountable for that. You're accountable for that too. So you mentioned some areas in which you are currently applying Splunk, we're using deploying it. I mean, why not university-wide? Is this the time and resource issue? Time and resources one step at a time. I'm in the office of the deputy CIO in data analytics. We moved Splunk into that area specifically because we wanted it to be an enterprise tool that was not owned by security and was not owned by operations. It's a tool just like, I don't want to say email, but it's a tool that everybody in the university can use. So starting with the university technology office, starting with the things that we have the manpower and we have the mandate for, but starting to bring in others, I'm an evangelist for Splunk on campus. If a researcher is interested, I'd go talk to them. You can show them how Splunk can be used in their research. If their research is of a certain area, we may go to Splunk for good and say, hey, look, we have a use case. I did that recently with T-Gen. Is it a safe zone that way by design? Because you're not getting political, right? Right. Would you get in? Absolutely. It's a safe zone by design and we're going to start to bring in people who are asking, start to bring them into the fold and then isolate them. And then if we need to set up a separate environment for NIST purposes or HIPAA, we can go ahead and do that. But we want it to be an enterprise level tool. You're also a Splunk Trust MVP. I'm also a trust professor. You're working within that community and we've talked a little bit about the community already today, actually quite a bit. It does show off quite a bit. There's always a handout, right? There's always somebody there to be helpful and we find that to be a really unique trait that's evolved out of this Splunk tribal affinity or whatever you want to call it. Absolutely. This community is amazing. I've been in higher ed for 14 years. I've been in the IT field for 25 years. I've never seen a community around a product like this. Absolutely wonderful. Why is that? Products good, that helps. But Splunk gives you access to the people. That's the number one thing is that any Splunk customer can talk to a product manager or somebody who's developing the product and get feedback and provide feedback and a lot of companies don't provide that. You can get to the sales people. You can get to the sales engineer. You're never going to get beyond that. And people give up and there's no real authenticity to it. Absolutely. I found out a feature of a product I was just looking at today isn't available and I said, well, I want that. He says, okay, great, let's talk about that. Let's see if the product can go in that direction for you and that's amazing. And they do that for all the customers. They're really listening. They really do listen. It was mentioned in Doug's keynote that they do listen. They're not always going to do what you want, but they are going to listen and they really honestly do listen. That's different. We had the other two guys up here and I love this because we're kind of joking. We're all old timers talking about IRC chat rooms and believe me the stories in the old days were worse now. We're a big IRC chat organization. And they were saying that they don't mind the brutal feedback either, which actually shows maturity for a young company like small taxis. They want the bad feedback. They want the bad feedback. They want the back feedback as well as the good. And the number of times this week I've heard, can I get your contact? Would you be willing to be in a beta? Would you be willing to look at an example of the product? One of the features that was in Doug's keynote is a feature that I have been working with Splunk behind the scenes for on a year and a half. I've been providing feedback for over a year on that. Just yeah, that's I think the direction you go. Yeah, that's good. Yeah, that's the thing that we should, I think we should be doing. What do they think they should do with the community going forward? Because I was pointing out yesterday and our commentary on our wrap up was they're really making a big expansion with the community. Why wouldn't they? It's already expanding. And that's a competitive advantage for the company. It is. Now, the danger is you can let it over build too fast. I mean, they have a good DNA so I'm not going to say that's the case, but they got to worry about that. I mean, how do you keep that in check? How do you grow an organic community fast while maintaining all the benefits? I think that's a very hard problem. So I think that you need to continue to grow the community, continue to grow the trust. The trust got a little larger this year. Trust members vote on upcoming trust members. And then we turn that information over to Splunk and they have the final say. But yeah, you got to grow that. You got to represent all of the different areas. There's two people in higher ed who are members of the trust. There's a bunch of different industries that are. You're in that trust. I'm in that trust. You're one of the two. I'm one of the two. And by doing that, you need to make sure that the customer has really continued to be involved. And if the customer decides to not be involved. Has there been a revolt yet? I mean, there's always a revolt. At some point, there's always growing pains. Has there been a revolt in the trust network? No, no, no, no. We love Splunk and it's a product and they do, they absolutely listen to us. So there certainly hasn't been a revolt. So there's no need for a revolt. There's no need for a revolt. This chatter, rumblings, but it's all positive. But we meet with Splunk senior, maybe not senior executive, but we meet with Splunk people on a regular basis and they do listen and that's the amazing thing. It's different from any other high-tech company. You always wonder. You don't want people getting jammed stuff down your throat and you see communities, as companies get older, they don't really be mindful of the sensitivity of the human aspect of the community. All right, so I'm going to ask the same question. I asked the other guys, what's the weirdest use case you've seen in the community? Because Splunk has so many use cases. What's the weirdest corner case of coolness that you've seen? So not mine, but one of this, the sales engineers I worked with, worked with a company that was Splunking data from snow-making machines. And so they were bringing in weather data to figure out when to make snow so that you get the best snow for skiing. I thought that was pretty awesome. That is awesome. Say that again. They were the snow blowers. The snow blowers, to make snow on the mountains for skiing, so those snow blowers have an immense amount of telemetry on them. How much water, water pressure, all that stuff, they're bringing in that all into Splunk and weather data to determine at what time is the best time to make the best snow for skiing. Now that's die-hard skiing. So between seven o'clock and six a.m. When the temperature is in this range. Which puts our best rainbow for the bed lightest powder or whatever. I wonder if that was an East Coast person because in the West Coast we don't have that problem. You don't need that in Colorado or... I think people get to make snow, they have the lower elevation. I sure, Pennsylvania, Maryland. I thought that was an amazing kind of edge use case that's not, you know, IT security laws. So what's your elevator pitch? If you're an evangelist and you're talking to somebody from University of Arizona or University of Denver, whatever, another university type who's looking. What do you tell them? Splunk can take any log you want. It doesn't matter what it's type, it doesn't matter what it's format. You can get it into Splunk and then you can compare and you can do transactions. So you can look at authentication and firewall data and web server and temperature in the room and whatever you want. And no other product is flexible to let you do that. It doesn't matter what the data is, you can get it in Splunk very easy, very fast, and honestly at a very convenient price. What about people who want to bring Splunk as a central nerve center for data? I think that's definitely the way to go. Let's just say I have all this firehose Twitter data and I want to jam that in there. And I have all this point of sale data. Can I jam that in there? Yep. Would that work? Absolutely, we bring in Twitter data. We look at Arizona State's incoming feed of mentions and then we're able to send that to the appropriate group and maybe a student has an issue and we want to be able to say, hey, somebody needs to look at this issue. So we monitor that type of information. We look at the amount of bandwidth that the university is using. We look at temperature. I'm working on a project with E911 to look at that data in Splunk and how to better. The goal is to better serve the students at the best price and protect everybody. Yeah, and that security aspect there too. Absolutely. What does it shape network traffic at all? Because number one complaint kids want to do is they want to have a server in their dorm room so they can have servers and then have game servers. It's a future prospect. We haven't done it yet, but I think the goal is to put as much operational data in Splunk as possible. What's the coolest thing kids are doing on campus these days with technology? Just out of just curious. Raspberry Pi is everywhere. Arduino is everywhere. We have a very good 3D printer program in our engineering school. We have a very active program for some of the robotics clubs. And so the technology that's in my age when I was a kid was unheard of is now $25 and sitting on their desk. And the tech culture is certainly broadened too. It used to be us geeks. Like now it's the tech culture as a genre. There's so much touch points. Everybody has four devices. They've got their laptop. They've maybe got a desktop. They've got a phone. They've got a tablet. And they're all bringing them on to campus. And they expect everything to work. Great. How's the STEM stuff going on too? A lot of women in check going on. Absolutely. A lot of STEM and a lot of STEAM. Add in arts in there. And I think that that's the key to the future. That's one of the reasons I've stayed at the university for so long is I really do feel like I'm improving the next generation. Well the STEAM is really important. It's important to get that A in there because arts is really a key part of this now. Absolutely. And can we make sure that we use Splunk to get John's son to class on time? Yeah, maybe. Can we do that? He's never on time. He's a physics major. I don't even think he goes to class. I just thought maybe we could nudge him in that direction. You know, I hit a 10 o'clock one time. Maybe not. No, no. Chris, thanks for joining us. We appreciate that. Absolutely, it's been a pleasure. And a fascinating background you've had. But it's interesting to hear about the current application too and best of luck down the road at ASU. Absolutely. Thanks very much for the opportunity. BUSC, right? Yeah, absolutely. The game this weekend. All right. Chris Kurtz from Arizona State back with more here at con.com 2016. Live on theCUBE in Orlando.


Okay, so well, good afternoon everyone and thank you for this invitation to talk about music in the Transcriber's User Conference. So, well, let me start with an introduction to the problem that we are dealing with here. So the thing is that music is a key element of our culture. And humanity learned to preserve and transmit music by writing. And as a result of this, we estimate that there are billions of pages with written musical over the world that represent as happens with the exorcist. The music sources also represent an incredible heritage that has been encoding centuries of human creativity. And this heritage is crucial for carrying out logical studies that will allow us to allow us to reach a knowledge beyond our current understanding of the evolution of music first. But that's so paramount to better understand our own cultural evolution. But the big obstacle in this context is that most of these sources exist only as physical copies that are stored in libraries and archives. And in this form, they are doomed to remain hidden and the huge potential to explore our music culture is prone to be completely wasted. So against this situation, there has been many efforts to developing technology that takes this music sources as input, creates their content and presents them in a format that makes their indexing and retrieval finally possible. And this is known as optical music recognition or handwritten music recognition when applied to handwritten sources in an analogy to handwritten test recognition. I'm going to explain now the technology behind optical music recognition or handwritten music recognition very briefly. So the task of teaching computers to remixing has been studied for years. Currently, there exists some available software for optical music recognition. And well, although they don't mention this explicitly when advertised the product, the software solutions only work for modern printed music. And even in these conditions quite often the results are said to be disappointing. So in recent years, my research team has been actively working on further developing this kind of of music reading systems for all types of music, but especially for a written music heritage. And we have many recent use cases demonstrating the success of this technology with different sources and manuscript times. The audience has allowed us to determine a general workflow which can be adapted to multiple scenarios with moderate effort. So what we are trying to do now is to transfer this knowledge that we have developed in scientific field, let's say or in controlled scenarios, want to transfer this knowledge to usable tools, so that all people can benefit from. And then what follows, I am going to present these rather generic blocks for optical music recognition or handwritten music recognition, using a use case about pension music manuscripts. So musical documents include different types of information. In general, for the purpose of written music recognition, we will be interested in two of these, the notes, plays on the stats on the staff lines, and the lyrics. They represent the text that must be sung. Also, we can also find some ornamental letters that contribute also to the text to recognize. So therefore the layout analysis states must first detect and categorize the different regions of the image to know the type of information they contain and where they are located within the image. Once we have isolated these components, on the one hand, irretion with musical notes is processed by a handwritten music recognition system to recover the musical information that is encoded in the image. For this, we have developed some kind of general music language that basically encodes the, the class, the, the, the first sign that indicates some information about the, the meaning of the rest of the notes. And then add general language that gives the information of where the notes are placed on the staff. So as I said, this process obtains this as a textual encoding and add up textual encoding of the written music. On the other hand, the regions must be processed by OCR or HDR systems, obtaining the list of characters that are contained therein. Here with music, we have an additional step that we must separate the text into silhouettes, because we need to know how to, how to put together the words to be sung. Once the musical information, notes and text are recovered from the image, this must be transformed into a structural digital format, a standard format that allows subsequent processes. So there are many of these in music, among them we can highlight MEI, the analog to TAI in the musical context, but there are many other possibilities that have a wide support. And there are even some conversors to navigate from one to the other. But basically, the idea is to finally represent the music content in a standard format. So, so far, this is what we have developed in our, in our research, in my research group. And the final step is to deploy these techniques to generate usable tools. So here in this work, we propose the inclusion of the now how investigated in recent years into the transcribers tool. In this way, any music manuscript could be processed automatically in the same way that text manuscripts are already being processed by transcribers. And integrating this into transcribers infrastructure, we will allow all the users to use and enhance the existing OMR or HMR technology. So, basically to sum up my talk here, I would like to emphasize that the music context is an exciting application that with a wide range of possibilities. The research in the from the computer science perspective has already shown promising results. So we know that the task is doable with moderate effort. But this is just necessary to transfer this now how to use our technologies. Of course it's use case will require some minor changes in the in the general workflow but we are pretty sure that are, we can, we can use our general blocks for processing music. So, the, the main, the main conclusion of my of my talk is that the current state of affairs represents a good opportunity to increase transcribers is a scope of application, including all the music heritage that we can found all around the world. So before ending, let me say that we are looking for collaborators who would be willing to join in this into the development of the technology into scribbles. Currently the project is led by, well, on the one hand by myself from the technical computer science perspective. This is also by Robert Lucida from the point of view of digital musicology. So please contact me or Roberts if you have any question or interested in this project. And that's all from my side. Thank you very much for your time and attention.


It makes us feel good because our food is a nostalgic taste. It's a very much like a taste of home. So when people like it and they get that feeling, it makes you feel good. During COVID for me personally, it was a, so I grew up in Massachusetts, my wife's from the Cape, we would eat lobster rolls during COVID. And it was like a thing of like a reminder of home. Cause it's like we couldn't fly home. And so it was just like driving to a place to have lobster rolls was the moment. And it was really special to your point. It was celebratory. And like freeing during COVID. It was like, that's the thing. It was like, we felt free.


Hi everyone, I just want to go through a quick tutorial on how to set up a course page on UBC Wiki. Before you create the page on UBC Wiki, make sure you're logged in to UBC Wiki. To create a new page, go to the create a new page from the sidebar here. So this is a create a new page. If you scroll to the bottom of the pages, you can see this multiple input box to create a page. If you're creating a new course on the course input box right here, type the name of your course. So I'm just going to type the name of the course and after you decided with the name of the course, click on create course page. So now you have created a course page and it loads the start tab template automatically and also a course template box. If you click on this sign here, you can see instructions on how to use this page. So to edit the course page here, you can just double click on the box here and then you can change the course title and you can type your name and email address in office hours and edit the box here. And if you click a save page, then the course is automatically set up. And this is a tab here that's automatically created for you. And if you click on one of the tabs here, it will automatically allow you to create a new sub page. Then you can go back to your course and when you click on here, you can see that the projects are here. So the start tabs are only created on the first page by default. If you want to copy over the start tabs, you can just edit the page, click on the tab here and copy this template and then go back to your page that you want to add the start tabs and just paste it and the tabs are automatically created here. If you want to change the name of the tabs, you can do so by editing the page, clicking on this template tab and change the name of the tab. So for example, instead of guidelines, I want to call my courses overview. So under the tab one here where it says guidelines, I just change to overview. So this part that says link one is basically, it just shows the link of the page that's associated with the tab one, which is overview. But need for you don't have to change the name of the link. And then if you want to delete some of tabs, so for example, if I want to delete past projects, you can do so by clicking on the tab that you want to delete.  And since I deleted the tab four, I also want to delete the link that is associated with the link that I just delete. So just do the same. And I just press apply changes and then press save changes. So now my tab has been modified. Please note that editing a tab only changes the tab on one page. So if you want to apply this tab on other pages that you have created, just click on edit, copy the tab and then edit, remove the tab and then paste again the tab and press save changes. So this is a really quick overview of how to use the course template. If you have any questions about how to edit the tabs, please go to the documentation on start tab right here. This documentation has information on how to edit the tabs, as well as how to change the slidings on the tab. So this is a really quick tutorial. See you next time.