It's your boy realistic game here and today we're on this escape creep bob-obby Now I'm pretty sure it's supposed to be spongebob, but it's just for copyright purposes because roblox likes to get rid of all the good stuff I'm pretty sure it's just to avoid that and let's go ahead and jump straight into the zombie and guys before we do make sure to smash the like button Subscribe and turn the notification bell on. Let's get it. Oh my god. Yo, what is this? This reminds me of the true ingredient menu screen. It looks exactly the same.  All right, so let's go ahead and play You want to give us nightmares, huh? All right. Oh, yeah, we got my boy Andy and in here. What's up, man? All right, let's get it. We're inside the Krusty Krab. Look at this Hey, you I need help getting the secret formula from crabs, dude. Why does he look so twisted, bro? All right, uh, let's begin with this. We jump on the barrels, bro. She just fell All right, it's pretty easy. Why is everybody dying? Come on pick up the slack people. Okay, let's go in the kitchen You're about to whip it up in the kitchen my boy. All right. Oh my god. What? Dude, look at this spongebob. Why does he look like that? He looks like spongebob has been on some drugs or something. It doesn't look right, bro What the heck man? That looks so terrified. Hey, at least he still has a job flipping patties Okay, girl, where are we supposed to go? What french fry is safe? Okay, I'm gonna follow her bro. She knows the way. Hey, which one girls? Let me know No, girl Do it Bro, she's an expert. All right. Um Darn it a dead end quick use these bubbles to get to the other side Okay, where the heck are the bubbles? No, we just fell dude. We broke our ankles Where we got to be quick because it seems like the bubbles Disappear. Oh great. It was this one and this one. Oh You got a jump. I don't think she knows you got a jump Can you go here? Go here Here No, oh my god. Okay. I thought we were dead and Well out kid. That was pretty cool Hey, watch out with this. What is this bro? It's like it's not even oil spill. He's like decaying And now we got some flying tomatoes. Wow, that is very crazy Okay, who's that? What is this bro? Okay, just dodge of the ghost knives, whatever the heck these are. Oh Dude that almost chopped me. Oh My god, okay, let's get it. Here we go down here My god, look at those crabby patties, dude So nasty brother. Okay, I don't know what to do quick jump on these patties to get to that door over there Great. Now we have to jump on these patties Yeah, dude. Okay, they make us jump high. I was about to say like how are you supposed to cross this? They go here Or cut. Okay. Oh my god. That is a giant patty. Wait What door was he talking about this one? I was a little confused there.  Okay, let's get it All right, so far it's pretty easy. Oh my god, why is there like hands like On the ceiling bro. What is going on this place? Okay, find a key to open the safe Okay, we need to find a key now Great, where the heck is the key at? Oh, wow. Okay, have to pick up Okay, open this bad boy and the crabby patty formula has to be there Brother's nothing What? My life is a lie. Okay. Oh, we in the ball, baby. Oh my god. Mr. Krabs balling bro Where is that formula? I don't know brother, but let's just take the money and run Because I mean there's a lot of money in here. Look at this. He's balling. Okay, let's go come on Jump this way. Where do we go? Can we have to go this way now? Oh No Wait, is there like a badge up there? What is it? What's going on over here? I guess not I Thought it was like a secret badge But there isn't Okay, let's keep going and let's go through here All right, cool Like there in it the Krusty Krab.  Okay, let go go go. Oh my god. We got to be quick Dude, you're so fast. What the heck? Okay, go go go. We cannot stop but go. Oh my god. There's spikes on the ground Dude look at them. Oh my god. Go. I shouldn't have stopped there.   Oh The pineapple we're going to spend up house Hurry hurry before he catches us.  Okay, what is going on? What happened to Squidward's house? Bro, what happened to Squidward's house? It's like God demolished or something? All right, let's go inside of SpongeBob's. Oh great.  Okay, there's a button to open that door go find it Okay, great. Now we got to find a hidden button Hey, where the heck can it be at?  Bro, what is going on in SpongeBob's house? It's all trash. I Should have known I should have known stepping on the trash kills you Okay, uh, so we literally can't touch anything in this house because everything is deadly apparently So vibes that is a Freakishly name Alright, maybe they're into toes. I don't know man. All right, let's keep going Bro, you got to run girl. Yeah, there you go. Okay now where the heck is this taking us? We're oh my god, Gary. Why does Gary look depressed? Donate this let's donate real quick to mr. Packstabber. This is awesome Uh, I'll be that he created for us right there you go man. Okay, uh, don't wake up Gary Dang it Bro Gary just ate us.  I thought we were friends. We're inside Gary now time to find that formula Right, so it seems like we're not the only ones after the formula Gary seems to be after it as well Bro, what do Gary be eating bro? What the heck? He ate a whole box of snail bites Man's got a chill bro Okay, um My god Gary you've been a lot of trash, bro.  Oh What is that like it's like that's his rib cage in his all you can see his heart Maybe we touch his heart. He'll change for the better. Oh You can actually hear a beating That is pretty cool, man.  Oh, I used to hate mushrooms, but then now I'm like I'm like me about it You know sometimes you just learn how to not hate things anymore It's all great now.  I used to not covered in that slime that we saw in his butt Okay, yes, we did it for the formulas mine, bro. Let me get the formula, bro. I want to make some money, too Hey, we got Dennis Give me with Kevin. What's the name Jones? Don't got game something like that, but that's Kevin's boy. Hey, what's up, Andy? What's up a boy? Okay, Gary Poor Gary the right. I guess that's it for this hobby. It was pretty cool I've played an obby this cool and like detailed in a minute. Oh shadow to pack cyber for the amazing obby Not up to NDS out to gig of bacon that'll to tweeter even though he got removed from my shoulder and shadow to you guys Thank you for watching. I'll see you guys in the next one. Peace


A bomb threat at Park Rapids High School forced the school to go on lockdown temporarily this morning. Law enforcement responded to the scene around 8 a.m. after school officials received a voice message of a bomb threat for October 10th. Most students were still on buses at that time and re-routed to Century School, which is about a block away. Staff members evacuated immediately and the district activated its automated alert system to notify parents of the lockdown. Officers did a security sweep of the entire school and did not find anything suspicious. Classes resumed after a two-hour delay. The safety of our students and our staff always comes first. As soon as we were able to secure the building and get law enforcement on site and evacuate, they were able to do their job. The disarray probably came more at Century as the buses were dropping them off over there and they tried to get them into the auditorium or gymnasium to get attendance taken and so forth. Always trying to be prepared for when situations do occur and we will come back, we'll debrief and we will look at what worked, what didn't work, how we're going to do it in the future. Two juveniles were arrested after Park Rapids police traced down the phone number used to make the threats. The juveniles admitted they made the call and that the threat was a hoax. Authorities say they will stay alert and keep doing what they can to keep the area safe. We take this very seriously. We act as if it's a serious concern in which we did. We do have school resource officers. I am one that goes into the schools. We're going to continue to do what we do. The personnel at the high school did a great job and we were able to come out with no injuries and we were happy with the outcome with that. Authorities haven't released any information on the juveniles but they have contacted their families. The Hubbard County Sheriff's Office, Minnesota State Patrol and Paul Bunyan Task Force assisted on the scene. If you've enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland Public Television.


वहड वहड नीद, वहड वहड वहड वहड विज़द सब एक तुर्ट मैंडूः नीद, वो हम इस्पे खप्च्षर करे हूँगे. विजच्च मैंझ्च मैंज्च मेंज्झक की हम पोट्टेंस क्या है, वहड ये इस्विंग गिवन सोँ माच वेड, वाई उछ़दो spiritual in India, how it is being focussed, that's what I am discussing about. आप विजिं को атलगाक वाईईगे atalakayak the rules and procedures which we do, वो आप विजिं कोईईईईईईई गईईईईईईईईईई, अप वो वह उणर पायए िर पाय연गईईईईईईईई. then we will go to core basics of risk management, what are the types, how they are being calculated, what will be the implication on them, how it will be related. from here we will move to core topics, we will move to basic calculations, to volatility, there will be a learning important for us, what is volatility, how it is being gauged, how it is being applied. next topic, you must have read in your basic studies, in statistics, standard deviation, but we will be applying and learning it from the perspective of portfolio, how it evolves, how it is calculated, how it is being relevant, because it is very critical and important for the risk management learning. then we will be doing a practice of these courses, these areas, how it is being rooted, and what we have discussed, we will be practicing them. then another important area other than standard deviation is beta, some people call it beta, but point is, this is also an important risk management, you might have seen it, but here we will bring its implication and learning critically. then we will mainly have to see the management of the risk management and its application, portfolio categorization and learning, so we will be learning making few ratios that will help us gauge and rank rates. so we will be learning sharp ratio, trainer ratio, information ratio, in the name of these, you don't need to worry, because we will be spending time on that, income formulas, their composition, but now we are talking that these are the areas of this module. similarly contagion ratio and then we will be taking detailed illustrations with figures, with practice we will be doing here. so these are the main topics in this particular module, which we will be taking to spread. so as we said we are going to start with the basics, so we need to know what is risk? risk, the chances of loss or unfavorable outcome associated with any action, if there is a good thing, if it is favorable then we are happy with that, as we said risk that refer to unfavorable or uncertain item, so when we say uncertainty, this refer to situation where we are not known with any particular scenario, about which there are chances, that is uncertainty. risk is what is make is possible to make profit, a common statement is no pain, no gain, it is applied here also, no risk, almost no return, some risk-free return happens, but mainly to get a return you have to take risk, so higher the risk, higher the return, but not always and this is about justified risk. now when we will take it to the risk management module, when we say risk management, risk management is the process of identifying, assessing, controlling, controlling and controlling threads to the organization, to its capital and to its earning, that what are the risks on our organization, how we manage them, these threats and risks could be stemmed from widespread, these are many types of risks, not one risk, we are taking risks from multiple sources, we have to gauge them, we have to identify them, apply them and solve them out.


So I'm going to be talking about DH underscore bus factor at this talk and I have even better slides than last time, as you can see. As a little digression, if you want to make slides like the other talk, which is all Zoomie, that's the program that you install, because a lot of people ask me about it. I'm sorry, I'm a little hoarse right now, too. So yeah, if you want to make pretty slides, use that and now one with the rest of the talk, I guess. So this is kind of about Depp Helper's maintenance model and how we can improve it and ever since I wrote it back whenever that was, I've pretty much been the sole committer. I'm sorry then. I'm trying not to pursue feedback or something. Is that better? Okay. Yeah. So ever since I wrote Depp Helper, I've pretty much been the sole committer. I'm certainly not the sole code writer, but whenever there's a bug, I'm generally the one who ends up fixing it unless it's a nasty bug that I ignore for months and months and then somebody else fixes it. So that's one thing that I'd like to address, but another thing is that if you actually look at Pergam's name, DH underscore, something that are in the WN archive and you could write some ugly Haskell code like this that loads in the contents file, looks for things that look like Depp Helper that are in user bin that aren't DH make because it's not Depp Helper commands and you make it look pretty and you ignore Depp Helper because it's not interesting for this data set or while you partition things into Depp Helper or not, you get 58 commands in Depp Helper and 99 other commands. So Depp Helper is now distributed throughout the WN archive in some way and so I've kind of been thinking about that. I mean, are all these pieces that are out there part of Depp Helper or not is a question that I would like to get answered here and I don't know the answer to it. And I thought we could kind of go over the list of some of the commands and just get some idea of, first of all, could everybody who's in the audience who maintains or is in team maintenance of a DH underscore command, a Depp Helper command that isn't in Depp Helper or one that isn't Depp Helper and you're, you consider yourself mostly responsible for it. Could you please raise your hand? So what, 10 people, something? So yeah, there's a lot of these things. I don't know if anybody knows what they all do. Most of them should be written to a standard, which is that it's a parole script that uses this library in this way and looks like this and has documentation. A few of them, where's the Haskell ones? Ah, there they are. Or not, they're written in shell because Haskell would be too hard or something. So we have a little bit of consistency maybe and they should all take the same options at least, which even the Haskell ones sort of do, although not entirely. And there's a lot of them. And I kind of think that's okay, but I've also noticed that lately, especially in the past few years, I'll learn of some cool new Depp Helper command that does something that was added to some new package named DH-something and I never seem to have even heard of the idea until it landed in the archive. And maybe that's okay too. You know, I'm not yelling at people for doing work. I'm just, it's interesting that people think that I'm just going to say no, sorry this won't go into Depp Helper and we might as well just route around the block and put it in the archive. So that's kind of where I'm coming at in this session, which isn't really intended to be a big talk. The idea was just to have some kind of a little boff thing and discuss this, especially among the people who raised their hand, but also, you know, just among everybody who uses Depp Helper and so on. So I've been struggling with the question of do we just let Depp Helper split up and do we say, say everybody who maintains Depp Helper is part of the Depp Helper team, I'm sorry, maintains a Depp Helper command is suddenly part of the Depp Helper team. We add a mailing list and you know, we talk among ourselves and it doesn't matter which package it's in, you're still part of the team. Does that sound reasonable? Everybody who has opinion, feel free to, does that sound reasonable? Raise your hand. Not many people think it's reasonable. Okay. Does the people think that's an unreasonable thing to do? I'm sorry, the proposal is to basically say everybody who maintains one of these programs is suddenly in the Depp Helper team, whether they want to be or not, and are subscribed to some mailing list. You're raising your hand that it's reasonable, oh question. Yeah, I think there's one. Sorry, Joey. That's fine, I'll just bring it to you. Hello, that's working now. So I guess my question and that would be, would you be comfortable with any of the people who maintain random Depp Helper commands for something that's basically entirely demand-specific, having commit access to Depp Helper? Because that's sort of the question the other way around. It is sort of the question the other way around. And I mean, in a way, things that are in Depp Helper are special in some way, or at least some of them are, because they're kind of the commonly accepted subset of stuff that we all use most of. And so I think it's possible that maybe the team, I mean, you know, if you have a real team, then the team should be able to come to a consensus. This command belongs in Depp Helper now, and that's something else that I wanted to talk about is, which of these commands belong in Depp Helper? You know, how many of these things, and I didn't get around to running the stats and getting a breakdown per command, how many rules files use it. But, you know, we could do that. And we could say, you know, DH auto recall for something is used in 10% of all rules files, and therefore should be in Depp Helper. And if there's going to be a Depp Helper team, then, you know, it seems to me that the team could make that decision. So let me talk about something else that's kind of background to talking about this, which is that there are commands in Depp Helper that I don't maintain.  And, you know, they're basically responsible for it. If I get a bug, I just forward it to them. And so, looking at it that way, it's really no problem to have DH auto recall put in Depp Helper as long as they get the bug. And I could continue to be the sole maintainer of Depp Helper, and this could continue to work. I don't know if that even makes any sense at all, that I'm the only one with the commit bit to this. So I should probably talk about my concerns with having the commit bit, but I think we have a question in the back. Is that Steve? Yeah. So I was just wondering if you have any thoughts about what your position is on the question of helpers being included in the Depp Helper package versus helpers being included in the default sequence. Should there be a relationship there? And should that be the threshold at which things get included in the Depp Helper package? Okay. Auto-reconf is what? A great example, Colin says. Is it in the default sequence? Ah, thank you. Okay. Yes, it should. Yeah. I mean, it sounds to me that, okay, here's the problem with that. Anything in Depp Helper being in the default sequence idea. There's all kinds of garbage in Depp Helper. And a lot of it is garbage that I wrote, and some of it is garbage that I shouldn't be calling garbage because someone else kindly contributed it to me, and it happened to not end up solving the right problem in the right way for the right amount of time, and it's now deprecated. So you could say anything that's not deprecated in Depp Helper could be in the standard sequence. Maybe. There's a few things in Depp Helper now that aren't in the standard sequence and aren't deprecated for pretty good reasons. So I don't know. So the other thing that I wanted to bring up is my general feelings about how hard Depp Helper is to maintain. And I think this is something we need to think about before we really think about having a team maintain it because if there's only one guy who can maintain it, Depp Helper has a problem, and that's the real purpose of this talk, right? And it's kind of my fault that Depp Helper has actually become harder to maintain as time has gone on. And it's also kind of not. If Depp Helper were only used by 10% of Deppian, it would be much easier to maintain. If Depp Helper did not have this DH thing, it would be significantly easier to maintain. Really significantly. Probably 50% of my work now is someone wants to change something in DH and I have to figure out what this breaks and how to deal with the breakage. So even if there were a Depp Helper team, it would need to have experts on DH in it. And there are a few people who have done awesome work on DH, and so maybe we could rope them in and get them to handle bug reports on a daily basis since they know how to deal with it. They know how to think about, is this change which seems completely innocuous and the bug reporter is like, there's no way this change could possibly break anything or we're not even thinking about breakage because it's such a simple thing that if it were any other piece of software that wasn't used by every single source package in Deppian, making this change would be obviously correct. And in a way, I'm responsible for this problem too because Depp Helper's API is very broad and people in Deppian often think that Depp Helper's API is anything that Depp Helper does, whether it's documented or not, whether it's a bug or not, and they depend on this behavior and of course they'll do it without even realizing that they're depending on it. So I recently had a bug report here at DeppConf which I went and bisected the bug and it turned out that I introduced it the very day that I rewrote Depp Helper in Perl 15 years ago. I had a think-o and I put in one word where I shouldn't have and the bug lurked in the code all the way to the present when somebody ran over it and I was like, well, this is a trivial bug to, oh, wait, you can fix this bug in ways that could break things that depend on this behavior and this behavior isn't specified and yeah. I don't know if part of the problem is that now that I'm not as much of a Perl programmer anymore I kind of care a little bit more about correctness. Maybe I've shot myself in the foot and I just need to be the Joey that I was five or ten years ago was like, I'll just break everything, I don't care.  So I tend to think that I do have overblown fears about breaking stuff in Depp Helper and I think that Depp Helper should be good at handling random breakage, yeah. Go ahead, Colin, if there is a mic. Test, test. So on the old bug report in the past, you've correctly, I think, gone and said we need to make sure that all source packages in Debian work with this change. Fine, in some cases this may require going off and fixing packages in unstable to cope with this. In some cases those may take a while to probably get to testing, et cetera, et cetera. What's your threshold on the point when you decide it's good enough? Because in some cases the things that break may not be in Debian. In some cases they may not be in testing and we may have to security update them, et cetera, et cetera. Yeah, and I don't know if you said in Debian specifically thinking maybe in Ubuntu too. I was actually thinking more of, because I think we can probably figure it out, but I was thinking more of third-party packages that have happened to depend on some random weirdness and are probably aren't maintained by people who are plugged in enough to the rest of Debian to notice such changes. Right, so yeah, I mean if a change only breaks one package or three packages and we catch that on the next full archive rebuild and the breakage isn't package suddenly lost file that nobody will notice is gone and or something like that, then we're fine. And Ashish, no. I'll go ahead. Let me try that again, but I'll whisper to avoid feedback. Okay, great. Yeah, it sounds like you've said a few times with me as the only committer on DevHelper. So let's just change that question mark. It sounds like you don't want to, but it also sounds like you haven't given any reasons. Also every time you take a drink from that it looks like you're taking a swig of rye or something. I wish. I mean, I'm conflicted. That's why I'm having this talk because on the one hand I would love to have a DevHelper team and on the other hand, it's not that I'm questioning the competence of somebody on the team, it's just that I have a lot of experience with dealing with this and they don't necessarily. The mic is vanished again. I'll repeat it. Yeah, I'll repeat it. Then maybe it makes a lot of sense to let people commit whatever makes sense of something and if you read the diff before making a release, I'm sorry. Okay, here's the thing.  It's not a thing that I'm good at. So this is not a good solution. My patch review would basically consist of exactly what I'm complaining about now which is needing to go figure out what it breaks. I already get patches. So getting patches isn't the problem. So maybe what you need is a better testing framework to rebuild the entire archive with DevHelper. Maybe I do, but like I was saying, some of the failure modes might be hard to detect. It might just be missing a file or it might put the wrong thing in the post-it script or it could be anything. So hypothetically, if we had binary reproducible builds, then you could verify that the contents were the same. Yes, please do that. So where was I? If people have questions, keep asking them. Otherwise I'll just ramble on because I'm really just trying to come to kind of a decision here and your input is what I want. So when I'm just rambling, I'm just filling time. So I was thinking about the breaking the archive stuff and then trying to rebuild it to find what breaks. But what about silent failures? What if we don't notice the package suddenly has different entries and all we did is test whether it builds but now it's broken. I'm not that convinced that trying to have this broad interface and just trying to break things and see whether it still works is a good approach and maybe we need to step back a bit and need to make the interface more explicit and explicitly telling this is a Python package, this is a Makefile package, this is an Autocon package and not having to figure this out automatically. Okay, so you're thinking I'm talking about just the interface to DH and often magically figures out what to do and yeah, that's a problem and I pretty well understand how to avoid problems with that interface and a few other DH people do and we can easily teach that to a team and not have that run into those problems. The larger problem is outside of DH though. It's that any change to any dev helper command that can ripple down and have unforeseen consequences in the archive because it can be depending on a bug or something. Thank you. What I wanted to say is not about the DH main part about all the helpers, all the small helpers. Supposedly they should have some very clear interface, they should be very clear what they do which is many times not the case, especially for some other language helpers and whatnot but the thing is they seem very suited for having unit tests and a clear definition of what they do so once you have that it will be easy to check that they are not breaking. So I think there's about three different answers to that. One of them is the whole Debian Archive is a pretty good unit test. If you can actually use it as one. I use it as one for Pristine TAR and it works great because I have a well-defined interface. I'm only doing one thing with the whole Debian Archive. I'm trying to make Pristine TAR output it. Unit tests is something that would be wonderful and unfortunately I suck at writing test suites. This is why I don't write PURL anymore. And if there were a Dev Helper team maybe some of the Dev Helper team would feel motivated because they're in the team to actually write tests. I mean it's not that there aren't any tests in Dev Helper. There aren't very many. And I think there was a third answer to that. If I answered you sufficiently or was there something else? Okay, we're supposed to have tests. We're proposing to have tests as a way of making sure that things don't break when other people are contributing. Yeah, but again I'm talking about the kind of breakage that yeah, you can write a regression test for this kind of breakage just fine. But detecting the breakage in the first place is the problem. I don't know if there's anything about Dev Helper's design that makes this more likely to have this problem than anything else. I think that, for example, the package build package has exactly the same problem because I've struggled with, oh, you want to add these build flag things. Well that's actually going to cause arbitrary random breakage to packages in the archive when they're configured. When you turn on dash JX some make files will break. And people, you know, you have, it's a complicated system with a lot of moving parts and you can have very well documented simple commands with a simple interface and still have these problems. You mentioned sucking out writing test suites which I can definitely relate to. The, as a really, really low impedance option have you considered something like the way Lentian's test suite works which is, it's not actually this but imagine that you took a copy of every source package that breaks and shoved it into the Dev Helper tree and you know you could reduce it or something but would that kind of thing be a decent test to start and at least then you might have regression tests? It would be a good way to do regression tests, definitely. And I think that if we had a test suite not having to worry about how much the space it used would be a good thing. Because we really are going to want whole packages or whole packages minus the actual sourcey bits. So yeah, I, I love the idea of having a test suite. I'm kind of curious if anybody in the audience would be interested in working on writing one because I think we all have lives and stuff. Yeah. Oh, were you interested back there, Steve? No, I was. So I'm wondering with respect if the problem of interfaces changing and breaking things without realizing it is a test suite the right way to go because in a sense where you never test for the bug until you conceive of the bug so you're always risking breaking things anyway. The test suite is only going to cover you for regression testing anyway. Well, you know, I guess I'm wondering if just incrementing the Deb helper compat level more frequently is actually the way to go. I think you could be on something and I've really been doing it more often. Often if I get to a case where I'm like okay, I need to fix this bug by making this change. Oh no, this change could possibly theoretically break something. I don't really feel like trying to get a full archive of rebuild and check it even though I may understand what the breakage might do or I might not. So I just throw it in and say new Deb helper compatibility level fixes this and I'm doing that more and more. The problem with that is, and maybe it's a good thing, is that it distributes all the load to you. Well, not all of it because there's still the issue that you have a lot of dead code that you're carrying around in Deb help. There is the dead code issue, yes. But on the other hand, a test suite is not going to be necessarily smaller than that. That is absolutely true. However, how many people in this room have updated the W incompatibility version from N to N plus one or more without reading the man page? That's all? Come on people, be honest. Yes, man Deb helper. Search for compact in uppercase. That's exactly what I'm saying. So, but then that takes an active effort on the part of the maintainer to have broken their package in light of your changes. So they broke it, they keep both pieces. Yeah, it's definitely true. It's just that if you look at Debian as a whole, I'm still breaking Debian. The fact that somebody else has responsibility for it, Debian is still broken, right? So I have a horrible suggestion that everybody's going to hate. Every time you've got these, that's not the horrible suggestion we hate. Every time you increase this compact level and you keep the old version, you have to have some kind of if stuff in your code which no doubt is eventually going to become fragile and break. Have you considered just putting multiple versions of Delpepper in the archive? Yeah, I haven't considered that. I personally haven't found the maintenance burden of the old compact code to be that high so far. Very, I really don't refactor Deb helper that much.  But since I'm just putting an if in and the old branch is the old code and the new code that can be maintained, it's generally not been an issue and I don't know if it would really save me anything to have version Deb helpers in the archive. You could definitely do it that way. I just don't know that it's any better or any worse. So without going too far down this, it's impossible to fix Deb helper rabbit hole. You know, it's definitely possible to keep maintaining Deb helper the way it's been maintained and it seems to work okay because I only have, you know, three or four people a week sending me bug reports or saying why didn't you fix this bug report that I sent you three weeks ago or three months ago or whatever and I only get twice that many at DebConf, I think. Twice that many per day at DebConf. So I'd kind of like to, you know, get back to DebConf team idea a little bit because it's kind of seems to me it's the only idea I have that would make maintenance of DebHelper any better. I think I've said DebConf a few times when I met DebHelper. Yeah. So I have a comment on your code review thing. Personally I love code reviews and I love reviewing code so maybe your expectation is just a little bit too high. Maybe you think that a patch should be perfect or your review be perfect and can't fail and you want to verify it all whereas there already is great value in having a code review to catch just minor issues or design issues and all that stuff. And also before you answer I think that the only way to move forward with team maintaining DebHelper is to actually allow for some breakage to happen and then count on the people who are responsible for in quotes for that breakage to learn from their mistakes and not make them again and in such a way spread the knowledge and also your methodology. That's I think the important thing. So if I would send you a patch what I would love to get is the feedback that you say well here's what I would do personally to ensure that this doesn't break and then I could do it. I hope that I generally do that but sometimes maybe I just make all the changes and commit it with a commit message that doesn't make sense. I'm human too I guess right.  Okay, DebHel does, other people do, people I trust do. Okay great. So I guess I would like to explore the team thing and I don't see any reason not to just do it really. People in the team want to continue running stuff by me until they feel comfortable. Maybe that's just the way to do it and just let them figure it out. And it's really not like you have to have 10 or more years of hard won experience on DebHelper to maintain DebHelper because I clearly maintained it for 10 years before that was the case and Steve. So an interesting example that comes to mind in this discussion is the case where I proposed particular variables be exposed in places as substitution variables to allow multi-arch paths to be expanded in a useful way and you rejected that and I think at the time you made a very brief comment in the bug went off and implemented your own thing and it came back as a fatal complete that of course well that was the DH exec that led to DH exec it basically said you could have anything any DebHelper file could be an executable that does its own thing and spits out the result which is a clever insight and it's very general I guess what I'm trying to say is those kinds of insights are somewhat unique to you Oh well okay I was taking this comment in a completely different way so I think I'll just take it that way that's what you're actually saying so first of all I apologize for the depths of my heart for being an asshole about you and DebHelper and other things secondly yeah that was an interesting general solution that was arrived at in a fit of peak and I don't think that I'm unique in that regard I think that anybody can say well we'll just generalize the hell out of this or whatever you know and I'm not saying and if there's a DebHelper team I'm certainly going to be part of it going forward I have no interest in not being part of DebHelper maintenance at all I would just like to not have as many bug reports that I have to personally deal with and or that stay open for too long or and this splintering problem which I don't know if it's really a problem that we have all these different DebHelper commands out there but it seems to me that it can't be ideal unless we just want to fully distribute DebHelper maintenance throughout Debian and maybe we should be thinking about removing commands from DebHelper and giving them to other people or something so let me talk a little bit more I mean the fact that there are people who are responsible for little pieces of DebHelper already you know I could easily give up more little pieces that would not be a problem so what I've been really thinking about with this team is there is a DebHelper team and what is the team maintenance model I don't like the team maintenance model where everybody in the team is equally responsible for everything which means that no one is responsible for anything you know I think that if we have a DebHelper command to just say at the bottom who is responsible of the man page who is responsible for this command and that way when it breaks you know who to talk to or something like that we kind of need a team maintenance model DebHelper command or something and we've kind of split it up in that way already except for the third of it that is actually in DebHelper so I've kind of been mulling this kind of thing over and I don't know maybe it's the kind of thing that we need to form a team and think about it and you know come up with something that makes sense I think I've kind of run almost dry on as far as what I wanted to talk about because people seem receptive to being on a team did I ask for a show of hands for who would actually be interested in being on a DebHelper team okay let's see there's five or six maybe we have a third of Debby in here so there might be 15 okay or 20 I forgot to raise my hand that sounds like your reasonable team to get started I guess I kind of like the idea of just drafting everybody who has a DebHelper and command it on the mailing list at least because why not if we have a mailing list you know we should communicate on it that's what it's for okay I don't know really how I'm doing on time do I have 10 minutes left or something ah so it actually worked out I actually ran dry at the right time that's nice yeah I think I'm done unless somebody has comments so I guess we'll just go to comments now I wanted to make a couple of comments one I think what you were saying about the splitting is that in my opinion it will make sense to have more DebHelper packages and concentrate more on the core and maybe enforce more some adherence to the DebH standards and the other thing is what you said about team maintenance you were saying that you don't like a team with nobody everybody's responsible whatever and I think you might try some team can work pretty well doing that if the team is functional I've been on functional teams that have still had the problem that a bug came in and everybody was busy so the bug didn't get dealt with because they all thought that the other guy wasn't busy that's unless your team is all hanging out on IRC every day I don't see how you can avoid that do you yeah but I don't have the bandwidth to hang out on another IRC channel and actually know who's active I need to have a mailing list with synchronous communication please Steve I thought you had a mike I've been holding the mike for a bit I don't know if my comments were low you were looking at me with the mike in a way that indicated you wanted to talk okay never mind I think Geerest is the one with the mike I raised my hand before I'm not interested in maintaining all of DebHelper one of the maintainer of one of the DH comments. And I definitely would be okay for me to maintain it within a greater developer team, because there's also the best factor on those tools. I'm maintaining one myself. There are no co-maintenors or anything. So it's also great for those if they could be integrated back. And you have a subset of the same problem that I have. Really, I don't know which thing you're maintaining. Maybe it's only used by a few packages. It's not the DH link tree. I think I submitted it to you and you suggested it to me. I said something like, I can't maintain this or it doesn't seem like the idea. I would have no problem maintaining it within developer. So the only comment is, well, this tool is rather stable and doesn't change much. I'm not sure I would be interested to get all the traffic of bug traffic just to watch it. So if there are some coordinators, we could ping or assign it this. Yeah, I mean, if you do have that kind of responsibility, that kind of thing could develop, I guess. You know, and there could be some way of routing the bug to the person who's probably responsible and if they don't get around to it, routing it to the team or whatever. Yeah. That's only a potential problem. Otherwise, I think it's a great way to, it should rather be opening it's new kind sooner because well, that's a kind of, that's a way to find new volunteers, really. They start with one comment and tends to discover other bugs and fix them and gain knowledge. Yeah, can I poll the audience on another question, which is just as general Debbie and package maintainers who I assume probably use Dev Helper, how many of you use Dev Helper or things that aren't in Dev Helper or think you might, okay, like half the audience or more? How many of you find that to be annoying in some way or another? So, Joey, I was actually gonna comment that I wanted to really thank you for this talk. If for no other reason than I had no idea that this many of the DH underscore commands were not things that you were personally sort of keeping high on. And that's simultaneously wonderful and amazingly scary. It's interesting because I've certainly been using Dev Helper stuff for a long time and I've actually been a very happy consumer of DH now for a while and as I look down this list, there are a number of those that I'm using at one time or lots of times. And it's been very interesting because in general, they do mostly just seem to do the right things. And I am one of those people who actually test things a lot before I actually upload them, except in really strange and rare cases. So there have been a couple times when I've stumbled over something that surprised me, that caused me to trigger a conversation with you or somebody else. But in general, I have this gut sense that this ecosystem is working amazingly well, particularly now that I understand how distributed some of this is. So that's why I raised my hand a little while ago when you asked, are you worrying about this too much? Because my sense is, this is working pretty well and you can certainly do things to make it better or make it less stressful for yourself in the future. But it's not like, I feel like there's some big net present danger that we have to be tackling. I feel, I mean, I agree with you in a way. It's just that I feel that maybe I'm not as active on Dev Helper as I have been at some points in the past or something like that. And it might just be an app or whatever. I had a big app and then I did DH and so, who knows. But yeah, thank you for that. Gert. What about pointing out a new generation of DH? Make, write down some guidelines from, okay, this should be the next kind of Devian Helper. I wasn't there when the switch from D-Select to Upt was there, but there was a moment, okay, the old system doesn't work. We need a new generation. Would you be guiding that? Could you point out a roadmap for that? So, I mean, as far as I've been able to come up with, DH was the new generation of Dev Helper and it just built on the old generation of Dev Helper and I don't have some master idea that would make Dev Helper's architecture better because if I did, I would probably just do it. So, I can't really help with that. If somebody is trying to write the next Dev Helper and wants to replace it, and let's say it's maybe not CDBS or hey, maybe it is CDBS, I have some suggestions for you. If it's CDBS, I have a few more than I would have had for somebody else. So yeah. Thank you. Are there any more questions before we're done? Questions, comments, whatever, we're done then. It looks like, okay, well, thanks for a good discussion and thank you for helping me maybe make up my mind on this thing that I've been mulling over for a couple of years, I think, on an offense. Oh, Ashish, go ahead. What's the plan? Sleep on it and find somebody who can make a mailing list, I guess. I guess that's actually easy, isn't it? Okay, so thanks again, folks. Thank you.


Many indigenous peoples really rely on the natural resources, you know, for their own food, for their own livelihoods. So when hurricanes, droughts, floods happen, then this increases the level of poverty amongst them. There is a big amount of money now being put for climate change mitigation and adaptation. And in some instances which I have seen, indigenous peoples are not consulted whenever some projects funded by these funds are put in their communities. For example, renewable energy projects like hydroelectric dams are built in their communities and their free prior and informed consent is not obtained.


I'm Imelda Abanyo, the President of the Philippine Network of Environmental Journalists. As the journalists, my three tips for practitioners are number one, is give your story a human face. Number two, do away with jargon. Make it simple but not oversimplified and give solutions to your stories, not just a presenting a problem.


I feel like you should take it. Maybe subscribe Order that YouTube fun stuff So I was just roaming around getting all my scans done for this planet to see what rewards I would get and I found a ship And I was like, oh, that's a big ship. I like the look of that ship. It might be a good cargo ship Let's go steal it. Most of these ships and ship landing sites are usually hostile enemies I don't think I've ever come across anything but hostile enemies and they usually Spaces as you can see if I aim down my site. We've got a couple of spaces hanging around Now usually when I do this I kill all these on the floor and then the ship just slides away But I thought I'd be smart about it. I'm like, well, I want this ship. I don't want it to fly away. So when it's snuck on board Enjoy the rest of the video.  I kill anyone that's on board Steal the ship Wait, am I being am I being taken away?   Hey, you got me. What? Oh, was that it was that all the crew? I'm in space. Oh no, I Don't know what's happened. I'm lost. Oh, where are you shooting me from? Ah, oh That was not a great idea. Oh good Probably shouldn't be throwing grenades around on a ship. All right. Come on, mate. You know you wanna Oh, this is um fun I'm just trying to reload Now I have to steal this because my other ship's just down there somewhere Anyone up here? Hello I was in the middle of doing some important planet stuff. I didn't realize this was gonna happen Is everyone everybody dead? Take over the ship or leave the ship But I kind of have to take it over because I'm in space, aren't I? Oh Man that means I'm gonna have to wait if I leave the ship do I go back to my ship automatically But this looks like a cool ship. I might take this And see what goes on Upgraded piloting skill required. God damn it It was a whole big waste of time Okay, so Yeah, don't do this because I am now stuck On this ship Because I don't have anything docked to it. I can't get off the ship I can't take over the ship because I don't have the piloting skills So I guess for me, that's just the end of the road Nothing left for me in this world other than to sit on the ship and disappear So at this point I tried everything every Typical exit every single door that I could go through there was no way off this ship back to my ship I couldn't fast travel either the game wouldn't let me I was stuck in space And on top of that I needed to be an expert pilot So there are instances where it looks like that if you don't have the right perks Or you're just unlucky in the fact that they take off before you can kill everyone You will be stuck on the ship forever I then had to go through find an old save that I could use like an auto save and then to Retrace the step so I could get back to where I was In the game prior to finding this ship and it took me probably about 10 minutes to catch back up. So unfortunately I lost progress for a short period of time, but it's it's really frustrating that this is a thing Because what else can you possibly do here other than soft luck and have to reset? There should be some form of way of escaping like maybe you could use the ship's systems to hail down Someone that you know and they come and save you. I don't know something of that nature I think I just think it's a bit short-sighted to have this in the game But it's it's probably the first thing in this entire game that has frustrated me Everything else has just gone fluidly and smoothly and I haven't had a single issue or problem or anything with the game So I'll take it, you know to be honest because it could be a lot worse So before you attempt to rob any ships and steal them and steal everything inside and kill everybody Make sure that you have all the necessary perks and things that aren't gonna get you stuck in space I hope this helped hit the like button subscribe. Thank you for watching. I have been easy now.


Secretary Austin, you said yourself 25,000 women and children, you said yourself, the world is not sicker. Israel struck the Iranian conflict in Damascus. Israel has instigated wider conflict. Iran has not killed anyone yet. But if you continue to arm Israel's genocide, things will escalate.  There are people dying right now. I know that you're used to have investments in weapon manufacturing companies. Is that why you remain silent on this issue? You are not representing the security of the American people. You are endangering all of us. International law demands that you are ceasing weapons. They can't get treatment, Secretary. They can't get treatment for cancer. They can't get treatment.


Thank you. As one of, I'm sure probably a number of enigmatologists in the room and those listening in, I think I certainly appreciate the value of the UDP and UDN. Speaking for clinical geneticists, we were all very excited when Bill announced the formation of the UDP in 2008. And just some thoughts in relation to the questions that were posed, what components of the UDN clinical evaluation are most important. And I think what was brought up earlier about the constraints as clinical geneticists now where we're forced to, you know, bring in a certain number of RVUs and see patients and when I first started in this field, you know, we'd see maybe three new patients a week and we could sit and think about them and now, you know, it's more like at least 12 new patients a week who are all, you know, enigmas and have no diagnosis and we see our patients having gone on diagnostic odysseys and the frustration that they have with that. So clearly the UDP and UDN bringing, you know, these multidisciplinary experts together and the communication I think is extremely valuable. Just having time to sit and go over the deep phenotyping information that's available and to phenotype it, not only the clinical but the cellular level as well, determining what tests are appropriate and best practices to make the most of the evaluations that patients have. There's certainly value in the outcome data. I think one thing, you know, we're always so excited when we come up with a specific diagnosis for a patient but often on the patient side, you know, I've had experience with, you know, parents saying well now what, you know, what's the next step and to really bring together the phenotype and genotype data to, you know, hopefully extend that into, you know, investigating possible treatment options. The modeling cores I think are extremely important and then I think, you know, now that many of us are doing whole exome, whole genome sequencing, it's oftentimes those patients that have negative results where you're, you know, certain that it's a genetic condition but looking beyond that into, you know, epigenetic causes as well as the environmental and other exposures. So how can the clinical evaluation be optimized to ensure that consultants have time to deliberate and improve the diagnostic evaluations and I think, and this may be done more often now but to get, to have results of at least a whole exome prior to seeing the patient may be helpful since it does look like, you know, 50% of those who have a diagnosis that's been obtained through whole exome or whole genome sequencing and then, you know, how much of the evaluations can be done locally prior to a patient coming in. I know there's limitations in that sometimes the quality of like an MRI might be below what others are expecting and then should clinical sites have focused areas of clinical expertise, I think again oftentimes one of the limiting things is the lack of maybe a specialist in one specific area such as a neuroradiologist who's great at reading, you know, brain MRIs for congenital abnormalities versus like, you know, tumors and things like that so to perhaps, you know, leverage that more and share those experts and then also the focused areas of expertise among the different sites and just the question that I was going to ask earlier was whether it's possible to sort of, as Dr. Lee's presentation brought up with, you know, a patient with disorder of sex development and whether sites can sort of focus on certain areas like that and select patients who may have similar findings so that they can, you know, dive deeper into, you know, various specific conditions and study those. Thank you, Cindy. And our discussion leader is John Mink. John is Professor of Pediatric Neurology, NeuroScience and Pediatrics at the University of Rochester. He's also Chief of Child Neurology. His research interests include Baton's disease and movement disorders in children. And John is also on our Council, our NINDS Council. John.


Hey, this is Christian Buckley with another MVP buzz chat interview. And I'm here with Emily. Hey, good morning, good afternoon. Hey, we're the same. We're like close time zones. Usually I'm talking to people that are continents away. Yeah, I'm Emily Mancini, an architect at Sympraxis Consulting and I am based out of St. Petersburg, Florida. All right. And how long have you been an MVP? About a week and a half. Yeah, exciting times. I'm on this stint of all like the brand new people. I see like the, like the now people don't realize this too, that it used to be that MVPs were were added on a quarterly basis. Now they can be added, you know, every month. And so when you see those notifications hit LinkedIn, I usually go and I stalk that the MVP buzz hashtag. Who's new? Who's like excited about it and like a great time to introduce you to get to know you. Get to know me interview.  Like how long have you been in space? What's your MVP, your practice area? Office apps and services. So I specialize in user experience and information architecture and I've been at Sympraxis Consulting for just about two years before joining Sympraxis. I actually worked with Mark and Julie as I was a platform owner at a biotech. So they were one of the partners who helped us do our custom development. So I've known them for quite a few years. So it was a quite the dream job to then leave there and join them and be at Sympraxis with our amazing group of Mark, Julie, Todd, Derek and Mike. They are great. I know everybody on the team friends with them for a long time. So I miss seeing Mark is a great, he has a great sense of humor, but it's always great to do something that's just silly and ridiculous and he automatically plays like the straight face. Like I don't know what you're talking about kind of great to play off of, but always enjoy being around that team and Todd, of course, like to poke fun at him all the time. But some smart people, great team over at Sympraxis though, those that aren't familiar, go take a look if you can figure out how to spell it. I think you guys probably should have variations of URLs that you own for people that don't know how to define it, but it's pretty much spelled the way that it sounds. Well, yeah, based based off the Greek word for collaboration. So for those who are fluent, you know, maybe not as hard to spell. It's worse than Pataco. I mean, I've got talk, which is my community effort. So it's all about collaboration. Well, very cool. So what's some of the stuff that you talk about and present it because I know everybody at Sympraxis is very involved in community activities as well. So what kind of stuff are you out talking about? So it's been a pretty exciting week and a half. I also just joined the PNP team. So I'm part of the sharing is caring initiative. So a part of that kind of overlaps with all the other areas that I'm interested in, which are also the Microsoft Community Docs, which I know Mark has been working on for quite a while. So creating that documentation for the businesses and IT pros under Microsoft Community Docs. I'm also working on the maturity model for Microsoft 365. So something at St. Van Buren kicked off quite a few years ago. I've talked a lot about that. So yeah, very involved. In fact, I did a governance version of that and a social collaboration version of that years ago, all built off of Sadie's work. Yep. Oh, excellent. Well, we probably have some upcoming initiatives that we'd love your feedback on and always feel free to go into that repo, read those articles and give us some feedback on what you think. You know, I point people to the work that was done the stuff that's on a docs now. So I know that there's been some partners like Peter Carson up in Canada and other, you know, Eric Riz also up in Canada that have been doing some work around the maturity model and kind of mapping that to tools and working that into their consulting practices as a way, which I think is a really smart thing. And Microsoft has written some articles as well where they're encouraging that kind of thing for partners to go and do. Makes sense. Yeah. We see a lot of organizations not really knowing they turn it on and they're like, great, we're all going to work together a lot better now, but they're really trying to not missing that framework of well, what do I want to be doing and where should I be depending on these different aspects of your organization? Because for example, a six person company like Sympraxis, we don't necessarily need the same maturity that you need at a 30,000 biotech, right? Well, that's that's the thing. It's one of the most common questions that I I hear. I say this a lot. So I'm feel like I'm repeating myself, but new to you Emily, where people want very prescriptive guidance. They want to know specifically like which tools do I use at which part? How is the, you know, the kind of the orchestration of the various tools? How do I make it work within it? And they don't like the answer of well, it really kind of depends. It depends on the size of your organization, the collaboration culture of your organization. What are people accustomed to? Are you very process oriented or is it more social or email based? Is it more project management based task based? And each of those you can have a completely different assortment of solutions that you might add into the mix. And so what's great about having something like the maturity model concept is to have an idea to go in and assess where you are. And it's great to get help from a partner to help do that assessment, but assess where you are. And then just in you might be fine at that level. I mean, we're at a level. I know what you see them level like level two. Do I need to be a level five? No, I think three is really where we want to be in this category and the do that per workload and think about overall. I mean, it's it's a it's a healthy operational activity to constantly assess and reassess where you are and look at what else could we be doing? That's what digital transformation is all about. Knowing where you are today and where you want to be tomorrow and then figuring out a path to get there. That's digital transformation. Agreed and you know, not just based off the tech based off of real business need to support what the business is doing. And I feel like that's where people get lost really often is yeah, I get really excited about cool new tech as well, but if it's not relevant to helping my business, that's not necessarily where I should be spending my time. Right. Well, that's always the look. I started my career a long time ago as a technical project manager and I worked on projects where I was given like a directive like you will go and deploy in this technology and we deployed some beautiful things. It is highly functional and then then nobody used. Guess what it was looked at is viewed at a failure. Yeah, I did it right. I did what I was asked to do, but then my name was attached to something that nobody used and then therefore and adoption and engagement were never didn't really factor in. I did the trainings like people were onboarded. Yeah, it off the list. Then people weren't using it and that's why understanding why it's so important to like the culture of your organization and what do we really need to be doing because at the end of the day, you know, like collaboration technology. We used to say it's about SharePoint all the time and I was always one of these people that's like sometimes it's okay to be a laggard and stay on the older version that you've customized and do that if it's meeting those business needs. There's that opportunity cost. There's new features. There's new capabilities, better integrations, all those kinds of things and if the value of those things is greater than the cost of getting there. The time, the expense, all that kind of stuff. Then it might be, hey, you're fine to stay where you are for now. Right. And hopefully. Yeah. Sellers hate that. I should say that that's fair. That's fair. Hopefully those conversations are also coming outside of not just IT, right? So this idea that this whole collaboration platform is owned by that one department I disagree with, right? So making sure that all of those decisions of where you're spending your time on your projects is coming from some kind of cross-functional steering committee. So you're meeting all of the needs of the business and helping everyone across the organization. You know, just have one half the organization totally on Microsoft 365 and the other one on the file share. And I realize in some organizations, it might be very one-sided and you might have, it might be driven by the CTO or CIO or the IT department around those things, but and that's where, you know, really having good leadership team sponsorship for that to make sure that it is, hey, this is an entire company solution. Things like, you know, rolling out Microsoft Teams might be IT that supports the desktops and supports all the applications, but you know, again, it can't be a tech driven deployment. It needs to fit in and there needs to be ongoing, you know, community management, you know, success management type view of the world and then discussion about how do we make this a better solution for all of the business needs and that ongoing, it's a change management discussion. And most organizations are really bad at change management. Yeah, that's fair. When I was a platform owner at the biotech, when I joined the company, there was 150 people and then by the time I had left within a span of four years, we grew to 1500. So we had that really big challenge where we had all of our, you know, sales general admin really into Microsoft 365, but then we had this whole other wing of scientists who had legitimate use for using this public drive all the time because their instruments output their data there and this was a whole unmet need of how they were collaborating. And so one of the things I did there was make that steering committee get some of the scientific leadership into the room so they had a better understanding of the platform and could see align their goals to how I could support them with the technology because a lot of their goals are common and easy to solve with Microsoft 365. It's, you know, transparency and decision making, making sure that people can collaborate across cross functional groups. These are all things that we can absolutely solve with teams and all of these other solutions. So be honest with me. Was it difficult to get them to sit down to get to that point though where those meetings were productive?  Cause that was, that's been my experience. Yeah. Once people like feel they get like trust built within the change management process, they're okay, but that usually takes time to convince people. It does. I didn't start the initiation of that conversation until a couple years in. So we had a pretty solid background and track record of having successful implementations. And when we first launched Microsoft 365, I focused a lot on productivity training. So we essentially revolutionized the way people took and shared notes. We started out with one note, right? And trying to raise that transparency just from something immediately actionable that doesn't require a lot of IT support. So it's probably about a year to two years. And when I first joined the company, I actually had joined from the HR department and in a support role. So I already had established relationships with the C suite. So they already all knew me. So when I came to them with my pitch and proposal, which was very formal, the what's in it for them, I already had some mapping of their goals to how the platform could do it. And I didn't have anybody pushback at all. They were all absolutely there for it. So I think partly showcasing why it mattered. They saw the impact we could make and then coming to them with a clear deliverable of, hey, this is one hour of your time every month. I'm not giving you pre reads and I'm not giving you action items. I just need you in the room to make sure we prioritize the correct projects. They were all in. Yeah. Well, that's a that I think from what you just described, maybe that was one mistake that I had was I required pre reads. Effort. So I get that. So I do it again. It would be like you just show up. No, there's nothing you need to do. I just need you there. I need your attention in the room. You give me that 3045 minutes and everything that you need to know will be encapsulated within that. That would have been a winning strategy. Yeah, as a former executive assistant for many years, I worked full time to pay my way through college. I knew that nobody did the pre reads at any company I've ever worked at. So it's like realistically, it's not going to happen for me either. So I'm not going to try. How can I better distill my message, which also helps you practice for external speaking in the community of what are the absolute minimum top points that I need to fit into this 45 to 60 minutes. Yeah. Well, that's where that whole that whole meme came from like, you know, could this meeting have been an email? Could this yeah, that comes from that if people not planning that out. Why do we actually need to meet? I have no problem when people respond to me to and say we had time set up to go through stuff like, can we just do this over email? Yes, we can. I have no problem with that. You know, we don't need to go through the rest of it and talk about weather for five minutes and then go to go through that structure. So that that is great. Well, it's really cool. So what else is what's coming up in this impraxis world? What are you guys working on? What are you doing? Anything that you want to share with the community? Sure. So we started this year, you know, in in light of the pandemic and us all being home and a lot of the speaking gig shifting. We started doing these bi weekly webinars called ask impraxis. So it's every other Wednesday for a half an hour and we always have a topic, but the goal is also to have it be kind of like an open office hours where we have our pre canned presentation should know and have a lot of questions. But we're also here to talk through hearing what our clients and anyone in the community is thinking about and trying to work through. So we just did one this week. You know, we called it the Todd show because it was about PowerShell and what's new in PowerShell wasn't about time. Okay, that's yeah. No, it was not. And then let's see. I'm looking at my calendar the 24th. We're doing another one and it's all going to be about reactions to Viva and talking about what's going on there. Yeah, I'll be interested to to check that out and your responses to that. I think there's a longer discussion. We won't get into it, but given your your background with you know, the the classification of data and metadata and all that kind of like that side of things and from the SharePoint world and get your thoughts. I certainly have mine about Viva and what it will take for people to actually start using the new capabilities. It's going to be an interesting discussion ongoing discussion. Yeah, we're actually it's the it's the topic. Can my place include you in the invites that I just sent out for this month's tweet jam is nice. I would love to and it's you know, I love that kind of stuff. Just I'm sure just like you guys are doing you you're going to present on stuff, but I'm more interested in to hear the questions. What kind of questions that people have and just kind of broad community pulse to the of the community. What are people thinking about this? Because often with that when you open things up like that, you're like, I never thought of it that way. It's like you get so you know, like single minded about and here's the target customer. Here's use cases. This is how here's what the features go and do and then somebody comes in and says, well, this is how we actually work and be like. It's a scenario we never thought of so. Absolutely. I mean to your point, that's my one of my favorite parts about being involved in the community is all of these different perspectives and challenging each other's thoughts and being able to expand all of our thinking together. I think we can accomplish a lot of different things and also I feel really grateful to the community early on when I was changing my career towards where I am now. I had met Sue Hanley and Mark Anderson early on and they just absolutely changed my interests in where I wanted to head and were always mentors to me as I went through this process. So I'm deeply thankful to them. Yeah, there are some of my favorite people out there. There's there's a lot of very smart people, a lot of fun people within the community. It's the it truly is the and I'm specifically talking about the SharePoint community that like built up. So these folks like Mark that I've known for over a decade, you know, all kind of met them at that SharePoint conference 2009 and and there's just a huge group of people that are still like I talked to in a weekly basis, although Mark is more stranger to me now. So it's a one of those the downside to the to the pandemic is people that I would do these, you know, these big catch up moments, see it events and stuff that aren't happening, but I'll have to track them down and waste a bunch of this time. To your point, that's my favorite part about be part of the sharing is caring team too is, you know, Hugo Bernier and David Warner and April Dunham, like spending time with them. It's also hanging out with friends while you're doing stuff for the community. So how nice that we can all connect across the glow from our desks and still have that relationship building time to exactly. Well, Emily, people want to find out more about you or get in touch with you. What are the best ways they can reach you? Twitter is always great. So at E-E-Man Cine, please feel free to reach out, ask me any questions. I'm always happy to talk through use cases and hear your feedback. Hear what you're struggling with. Hear cool success stories too. I feel like people don't often share those and I definitely want to hear more about something cool that you've done that you want to tell the world about and do you have like a short snappy URL for the office hours or is it long-winded drawn out? You've got to go search for it to find those. I'm sure that it's simp.info slash ask simpraxis and if it's not, I'll be doing it immediately after this meeting. All right, we're going to we'll check that. So, well Emily really appreciate the time and getting to talk to you and congratulations again on your new MVP. Well deserved. Thank you. Thanks so much for having me. We'll talk to you soon.


Hey guys, Kim Ross here, and I'm a business consultant that specializes in reducing costs for businesses By looking that they're essential expenses and today I have a question for you What are some famous quotes by businessmen that you you highly regard? I'll give you one of mine from one of the most famous people in Omaha, Nebraska where I was born and raised Warren Buffett and it has to do with investing. He says rule number one in investing is don't lose And rule number two is pretty simple. It's don't forget rule number one This actually comes from an interview one of the first televised interviews that Warren Buffett ever made And I'll actually push post a link to it here in the description of this video And it's very insightful in the sense that what you want to do based on what he's saying right is Investing companies are investing things that don't lose for you, right? And in this particular case it really ties great into what it is I specialize in I want to help businesses not lose When it comes to over investing in their vendors, I think vendors spend a lot of time Hiding things or making it really difficult for you to understand what they offer you and you over pay for those things It's like any other business that you're investing in right that is providing your service or product You don't want to over pay for those things You don't want to over invest in those things and if you're a much like one or like myself That's what you need to look at is to see and evaluate what it really costs to Invest in a business and if that business is actually providing a good enough service to its customers that's Worth it in the end right and now ultimately you don't want to over pay for that in comparison to maybe what another business is Offering right and that's what Warren does Warren does that and he's made lots of money Being that simple right having simple Easy to understand easy to follow Philosophies of something in business at least when it comes to investing in the stock market and in businesses that is required And I think ultimately that is what we need to do in business too when it talks about operating business We can keep this simple if we can understand how to not lose then we should be in a good enough spot to Evaluate and understand the trajectory of our business at any given time and that's what I'm hoping to do with my clients Is I want them to understand and be able to simplify Their vendor situation right and say hey look these are the businesses that provide the services to you that are worth Investing in because in the end the return on that is going to help your business be even more profitable in the end So I think that's it's about all I really want to say about this. I really think I've Honed in on some things here about Warren that I I want to be able to convey to you because I really do feel like a lot of what Warren has ingrained in himself. He's ingrained in the society or in the in the In the town of Omaha I feel like when I was born and raised in in in that area a lot of folks Spent a lot of time investing in the right things Looking at things asking the right questions and that's something that it just comes second nature to me And I want to give that second nature to the businesses I serve and so that's that's what I'm out to say I'd really love to hear what some of your Famous quotes are what business people you regard and what what they say and how how you look at things at times But I really do do highly regard what Warren has to say and like I said I'll put in the description I'll link to this video that I found that's really profound as far as This was decades ago, right when he first started or maybe not first started But when he was first getting known as Warren Buffett, this was what he had to say And I don't I don't think he's astrayed too much off of off of that philosophy when it comes to investing and Evaluating businesses and it's not that business change doesn't change and that you your philosophies can't change There's a core to it and I think the core to it is really in this interview So I'd love it if you check that out I'd love to hear what your your thoughts are your comments are about that as well as I'd love to hear what quotes you like from other famous people In business what they have to say I'd like to have a discussion there and please subscribe if you haven't already Please like this video to help the numbers out helps the algorithms push out this content to other folks that Really do need to value business or want to understand business better I want to provide that content for them as well as give them some great advice and and have some great discussions as well And let your friends know I'm out there. So until next time, please visit my website. I'm Ken Ross comm and I'll see you around


And let's take you to Oregon State. The Commission of Police in Oregon State, Larry Bancoley, has erected the State Criminal Investigation Department to immediately commence investigation with a view to unraveling the awesomeness behind the Devilish Act. The annex office, located at Yanomotri in Abyokuta, the Oregon State Capitol, was set on fire by yet to be identified hoodlums. In the attack, over 600,000 permanent voter scouts were burnt, including voting cubicles, ballot boxes and orders. In effort to bring the hoodlums to justice, the command has resolved to reward anybody with credible information that would lead to the arrest of the perpetrators with the sum of 2.5 million Naira. In fighting among the Oregon Labor Party to another dimension, as a faction has suspended the State Chairman, Michael Ashaday, the Secretary, Faisola Michael, and the National Publicist Secretary, Abayomi Arambanbi for alleged gross misconduct and anti-party activities. The faction loyal to the Director-General of the L.P. Presidential Campaign Council, Dr. Dony Okube, who was expert along 10 orders for alleged breach of the party's constitution, said the State Party Chairman and the National Publicist Secretary's terms have been dismissed. Plus TV Africa recalled a faction loyal to the National Publicist Secretary, Abayomi Arambanbi, had announced the dismissal of Okube and 10 orders, L.P. leaders in the state, over alleged non-financial membership status, high-handedness, and financial recklessness. Meanwhile, the Deputy Chairman, Lukman Jagoon and 4 orders reaffirmed Okube's membership but suspended Ashaday, Faisola, Arambanbi, citing anti-party activities. We, leaders and stakeholders of Labor Party in Okube State, have suspended the membership of Mr. Michael Ashaday, the State Chairman, Mr. Michael Faisola, the State Secretary, from the Labor Party for gross misconduct and anti-party activities. Rising from an emergency leadership and stakeholders' meeting held today in Abayokuta, the party decided to ask these officers for various offenses bordering on carnivans with other parties, especially the ruling All Progressive Congress, a piece of government in the state. We recommend to the National Legislative, the National panel, and the replacement of Arambanbi as Acting National Publicist Secretary. The State Labor Party airbired their farms, the membership of Dr. Dwin Yokube, and 11 orders. We are not saying that some people have not even paid party due, as the year ended, to really say they have not paid. Transaction as at 31st December of every year, that is when you close the transaction for the whole year, that is when one is liable that has not paid this year, has not paid that. And those that are saying that others have not paid, have they paid? Do they even have a party membership card? Ask them. Ask them. You have.


In this review, we discuss a non-equilibrium thermodynamic theory for heat transport in superlattices, graded systems, and thermal metamaterials with defects. The aim is to provide researchers in non-equilibrium thermodynamics as well as material scientists with a framework to consider in a systematic way several non-equilibrium questions about current developments, which are fostering new aims in heat transport, and the techniques for achieving them. For instance, defect engineering, dislocation engineering, stress engineering, phonon engineering, and nanoengineering. We also suggest some new applications in the particular case of mobile defects. This article was authored by David Jue and Liliana Rastucia.


Ever since we were kids We get asked the question What do you want to be when you're older and usually it's imaginative fun and bold Nobody put up guardrails to our dreams our imagination and our creativity. I wanted to be a cartoonist We dared to be we dared to become But as we got older our field of possibilities grew more narrow our dreams shrunken size We started to get categorized We got placed inside the box From picking subjects at university To choosing a career path And I struggled with this. I took two gap years before eventually dropping out of my first degree As an adult we get asked what do you do for a living? These societal assigned labels allow others to stereotype us.   We hear things like having a focused niche is a lot more powerful than having a general Channel having a niche having a niche having a niche how to find your niche on YouTube once again Putting us back inside the box Telling us to stick to one thing you must choose Just because it's easier for others to define what and who we are So I asked why We are not products serving only one purpose We are not one-dimensional We are not meant to be confined inside this box We are all semi-grown not fully grown in an ever-discovering journey Never arriving at our true destination We are supposed to embrace out in a kid With naive curiosity Learning every chance we get To pick ourselves up with bravery after falling down There should be no mental barriers to our creativity No self-limitations in the way we see the world And most of all we shouldn't take ourselves or life too seriously I guess what I'm trying to say is welcome to this channel a channel. That's in its own category Not better or worse Just its own a channel that just is a Channel for the sake of creating with no niche Made by a semi-grown kid Your niche is you the human you need to be as broad as possible, but fully you which becomes your niche