Thanks for the introduction. So I'm going to talk about leakage resilience secret sharing and applications, and this is based on joint work with Prashant Nalini Vasudevan. So let me start the talk by giving you a brief overview of threshold secret sharing. So as you might all be aware, it was introduced in the seminal works of Shamir and Blackley in the late 70s. And in this setting, there is a dealer who has a secret message M, and he wants to split this secret into N shares, SH1 to SHN with some threshold parameter T. The dealer then sends the IH share SHI to party PI. So we require a threshold secret sharing to satisfy two properties. The first is the correctness property, which states that any group of T or more parties can come together, use their shares to reconstruct the secret message M. And the second property is the secrecy property, which states that any adversary who's correcting at most T minus 1 parties learns no information about the secret message. So threshold secret sharing is a fundamental cryptographic primitive with numerous applications. Some of the applications include constructing secure multi-party computation protocols, constructing threshold cryptographic primitives and so on. And the security of all these applications crucially rely on the secrecy property of the underlying secret sharing scheme. So the question we would like to address today is that, what if the adversary in addition to corrupting T minus 1 parties, also learn some partial information about the Harness party shares? So this information could be leaked to the adversary via some side channels that it might have on the storage devices of the Harness parties. So the privacy property that I just mentioned does not give any guarantees under the stronger adversarial model. And hence we need a stronger notion of security in order to capture this. So this was done by two independent works, one by Benhamudda et al, which appeared in crypto last year and other by Goyal and Kumar that appeared in stock 2018. And they introduced this notion called as leakage-resilient secret sharing. So leakage-resilient secret sharing is just like any other threshold secret sharing satisfying the correctness property. In addition, the privacy property is now strengthened to something called as leakage-resilience. So this states that any adversary who's corrupting at most T minus 1 parties learns no information about the underlying secret message M even when given some bounded leakage from the other shares. So let's see the formal definition. So the formal definition is modeled as a game between an adversary and a challenger. So the challenger first generates the sharing of some secret message M and let's call the shares to be SH1 to SHN. The adversary now gives a set T which denotes the set of corrupted parties as well as some leakage functions FIs to be applied on the Harness party shares. So we require two properties. The first is that the size of the set T which denotes the number of corrupted parties that should be less than or equal to T minus 1. The second property is that the output length of this function FI should be bounded. So notice that if we allow the output length of these functions to be arbitrary, then the functions output length could be as long as the share size. And if the identity and the functions are just identity functions, then the adversary gets all the information about the secret. So here we cannot hope to give any sort of privacy and hence we need to restrict the output length of these leakage functions to have some bounded length. However, notice that we do not place any restrictions on the computational complexity of these leakage functions. So these leakage functions could be arbitrary as long as they have a bounded output length. So given this the challenger now sends back the shares corresponding to the corrupted parties as well as the output of these leakage functions applied on the harnessed parties shares. So at the end we require the adversary given even this additional information not to learn any information about the secret message M. Okay, so this is the formal definition and let me give you a brief overview of the prior work in this area. So Guru Swami and Wooters in 2017 showed that Shamir's secret sharing when instantiated over finite fields with characteristic two is not leakage resilient. That is they showed an explicit reconstruction strategy that allows an adversary to obtain the entire secret given some partial information from all the shares. In interesting work, Ben Hamuda et al. showed that Shamir's secret sharing when instantiated over a large prime order field is in fact leakage resilient for thresholds T greater than or equal to N minus N to the one fourth. And in the work of Goyal and Kumar, they gave a different construction of leakage resilient secret sharing scheme for the constant thresholds case. So as you can see, there is a huge gap which is left. So the first question that we would like to address is that can we construct a leakage resilient secret sharing scheme for all thresholds? And the second question is that can we extend it to for all monotone access structures? So in this work, we resolve this question. So we show a compiler that takes any secret sharing scheme for a monotone access structure A with some rate R and it converts into a leakage resilient secret sharing scheme for the same access structure with the following properties. The first property is that the rate of the resultant secret sharing scheme is only a constant multiplicative factor worse than the rate of the original sharing scheme. That is the rate of the leakage resilient secret sharing is R over 3.01. And the second property is that the leakage resilience rate which is defined to be the ratio of the number of bits leaked to the share size can be made to be arbitrarily close to one. So this in turn implies that even if we leak almost 99% of the share size, we can prove security. And in the next talk, you'll hear from Mark about their construction which also gives such a compiler. Okay, so as an application of our compiler, we show how to construct a constant rate non-malable secret sharing scheme in the information theoretic setting. So as you heard in the first talk, non-malable secret sharing is just like any other threshold secret sharing scheme that satisfies the correctness and the secrecy properties. It also satisfies this additional non-malability property which roughly states that any tampering attack on the shares either preserves the original secret or completely destroys it. So this notion was introduced in the work of Goer and Kumar in 2018. And it can be thought of as a generalization of this notion of non-malable codes. And a question that was left open in the work was to construct a constant rate non-malable secret sharing in the information theoretic setting. So what we show in this work is that if we plug in our leakage resilience secret sharing with the non-malable secret sharing compiler of Badrinarayan and Myset that appeared in EuroCrip this year, we can in fact get a constant rate threshold non-malable secret sharing for thresholds T greater than or equal to four. And in the next talk, you'll also hear about giving a stronger notion of non-malable secret sharing from this leakage resilience secret sharing. And I hope that Mark will be able to give these details. So as another application, we also give a leakage tolerant multi-party computation for general interaction patterns. But unfortunately, I wouldn't have time to go into the details and I would encourage you to look into our paper. Okay, so in the rest of the talk, I'll focus on the threshold case. I'll give you a construction of a leakage resilience secret sharing that has a constant rate, but the rate would be small, it would be worse than the promised by a compiler. And also the leakage resilience rate that our construction satisfied would be worse, but then the optimum of one, but it's still a constant. So these simplifications are just for the purpose of this talk. Okay, so let's start with the construction. So let's say that we want to secret share a message in. So the first step in our construction is to just split this message M into N shares using Shamir secret sharing. So here we do not assume any leakage resilience property from the underlying Shamir secret sharing scheme. Okay, so let's assume that each of these Shamir shares is in a finite field F. The next step is to choose a random vector R from F to the K, where K is some constant. Okay, so once you choose this R, you then choose a random vector L1 from F to the K such that the inner product of L1 with this R is equal to the first Shamir share SS1. Then you do this for the next one as well. So you choose a random vector L2 such that the inner product of L2 with the same R is the second Shamir share SS2 and so on. So you choose L3 up to LN such that the inner product with R is the corresponding Shamir shares. Okay, so thus you obtain L1 to LN and this is the second step. So the final step is to take this vector R and you then split it into N shares R1 to RN using Shamir secret sharing now over F to the K. Okay, so the share corresponding to the I at party will be LI comma RI. Okay, so this is the secret sharing scheme. So how do we reconstruct? You first, given any T shares, you can use the Shamir secret sharing to reconstruct this R. Then you take the inner product with the corresponding LIs to get the T Shamir shares of M and then you use the reconstruction of Shamir again to get the secret message. So this is how the reconstruction works. So the interesting point is that how do we show that it is in fact secure against in the leakage model? So for the purpose of the stock, let's assume that the final T minus one shares are revealed in the clear. This corresponds to the set T and there is some arbitrary leakage function acting on the rest of the shares. So this is just for the purpose of the stock. So the proof actually follows from several observations. So the first observation is that each individual leakage function F does not learn any information about the secret vector R that was chosen in the sharing phase. So to see why this is the case, notice that each of these FIs just looks at one of these RIs and since R is in fact a Shamir share of R, it hides all the information about R. So one can roughly think about the leakage function acting solely on the vector LIs. So this is the first observation that the FI of LI comma RI, FI does not get any information about R. So the second observation is that the output of this leakage function FI of LI comma RI hides all information about the Shamir share SSI. Okay, so to see why this is the case, notice that inner product acts as a strong two source extractor. So even given some bounded leakage on one of the sources, here one of the sources is LI, the inner product of LI with the other source which is R has sufficient entropy. So this can be formalized to show that FI of LI comma RI hides all information about the underlying Shamir share SSI. So this is the second observation. And the third observation is that the only Shamir shares that the adversary gets access to are those which correspond to, which are revealed in the clear. And since there are at most T minus one revealed shares, it follows from the privacy of the Shamir secret sharing of N that these T minus one shares hide information about it. So this is the rough intuition behind the proof. Of course, there are lots of subtleties involved and I would encourage you to look into the paper for the exact details. So to conclude the main result in our paper is to give a compiler that converts a secret sharing scheme for a monotone access structure A to a leakage resilience secret sharing scheme for the same access structure with the following property. So it has a constant factor degradation in the rate and it has optimal leakage resilience rate. And we gave applications to constructing constant rate non-malable secret sharing in the information theoretic setting as well as application to constructing leakage tolerant MPC protocols for restricted interaction patterns. And in a concurrent and an independent work, Kumar Meika and Sahai gave a stronger notion of leakage resilience property and they actually gave interesting constructions based on connections to communication complexity. So an interesting open question would be to find other applications of leakage resilience secret sharing scheme. And that's it. Thank you for your attention. Mark Simkin will continue the presentation. All right, so I'm going to present our paper which deals with a very similar topic to the paper that we just heard about. So this is stronger leakage resilient and non-malable secret sharing for general access structures. And this is a paper joint work with Divesh Agarwal, Ivan Damgard, Jesper Busnilsen, Machi Abramsky, Eric Provanto, Joe Ribeiro and me. And yes, so we like already heard like what is non-malable secret sharing with this leakage resilience secret sharing in the previous talk. So I'm kind of gonna focus on the things that you didn't hear so much yet. So non-malable secret sharing, as you had before was introduced quite recently, but like a lot of papers deal with this problem and the idea is again that you have some file and you secret share it like you compute a bunch of shares and now the adversary can somehow tamper with each file independently with each share independently. And what we would like is that the reconstructed secret from the tampered shares is either the same as it was before or it is completely unrelated. Okay, so we want to prevent that it is transformed into a related message. And the first notion dealt with the case of a single tampering and like a minimal reconstruction set. And what we do in this work is that we extend this non-malability notion to something that we call concurrent reconstruction. And the idea is that in this case, the adversary cannot specify like one set of tampering, not one vector of tampering functions, but several vectors of tampering functions. And so he does this in a non-adaptive way which is in contrast to the paper that Antonio presented. So here he like has to specify all of the vectors at once. And then the secret sharing at the top will basically be thrown into these tampering functions. And then even we can use different reconstruction sets here which are again chosen non-adaptively by the adversary. We reconstructed different reconstruction sets to get different kind of corrupted secrets. And again, we want to have the property that all of those secrets are so that for any one of those secrets, it's either the same one as it was before or it is completely unrelated. Okay, and yes. Okay, so what we do in our papers basically, this is kind of abstractly speaking, like we construct like leakage resilience, secret sharing construct non-mailable secret sharing, but the general idea of how to construct all of them follows the same kind of blueprint. So what we will end up doing is we will take a secret sharing scheme and we will take some encoding function and we will like mingle them together. And then depending on which encoding function you plug in you will get either leakage resilience or you will get non-mailability. So it's kind of like a general simple approach of how to do these things. Yes, so we get leakage resilience. So and all of this is for general access structures and with information theoretic security. And yes, our non-mailable secret sharing will be for three monotone general access structures so that means that any authorized set has at least size three. And then we use again basically the same approach to show that you can also build something which we'll call leakage or non-mailable threshold signatures which I'll like skim over towards the end of the talk. And in comparison to the previous talk what we basically have is that both so both the non-mailable secret sharing and the leakage resilience secret sharing that we construct has a signal like a worse rate than the constructions from the previous talk but in comparison to the previous talk we achieve a stronger security notion for our non-mailable secret sharing. So this is kind of how the two papers complement each other. Okay, so kind of on a very high level what we have is we're given some secret sharing for some access structure and what we would like now to do is we would like to take those shares and somehow re-encode them into new shares such that we get like the leakage resilience and non-mailability properties. And what we, yes. And what we will basically do is think of like we have some encoding function which takes each one of those shares and it will produce two different shares. Okay, and then again we will plug in different encoding functions to get different things. So what we simply do is we will take each of those shares and we will split it into two shares with this encoding function. And now we will redistribute the shares accordingly as follows, so originally the first share was this and now the new first share will be this vector of shares, okay? So what does this, what is this? It will be the green one of the first share and then all of the other red ones, okay? And for the second share it will be like the green one of the second one and then all of the red ones from the other ones and we'll continue doing this. Now if we want to reconstruct, say we have this first and the second share then we can combine those two and those two to reconstruct the original two shares and then if this is kind of like, if the X structure allows these two shares to reconstruct the secret then the whole construction will kind of reconstruct the secret, okay? And note that kind of if this encoding in some sense requires that you definitely need both of those parts to reconstruct what you encoded then for the third share, for the fourth share, for the fifth share, you'd never have the green part, okay? So like they know exactly, they can exactly decode the two shares that they are supposed to decode. Yes, and the other important thing is that every one of the green shares is held exactly by one party, okay? So yeah, it's a very obvious statement. That's one party that has each green share. So now the question is what do we do, what encoding do we use to obtain different secret sharing schemes? So let's start with non-leakage resilient secret sharing and it's in the same model as before. So we basically can independently leak from each share and we would like to ensure that the secret remains hidden even when the adversary sees the leakage, okay? So what we will use is basically a strong seeded extractor which is a primitive that it takes this like a uniformly random seed as input, some high min entropy string. Yeah, that has a lot of entropy and when you apply the extractor you will get something that looks uniform or is close to uniform, okay? And the strong here means that even if the seed is revealed, this still looks close to uniformly random. And another property that we will need for our construction is that this extractor also has something that is called efficient pre-image sampling. So that means that if I have something here I can efficiently find some uniformly random inputs or close to uniformly random inputs that will, if the extractor is applied to it give me that output, okay? And what we now simply do is to encode one of those original secret shares we will apply this inverse of the extractor to obtain these two things. So basically one of those will be the seed and one of those will be the high min entropy sample. And like as we've seen from the previous samples from the previous slides, the jth share will then be kind of a bunch of the red ones and one of the green ones. This will compose the new share. And if we look what this means here is we will basically have one of those things will be this long sample and the rest of those will be the short seeds which will in total compose the new share of our leakage resilience secret sharing scheme. And the intuition why this is a leakage resilience secret sharing scheme is that even if the adverse we get to leak pretty much all of the red shares as I said before the green share is only held by one part like each of the green shares is only held by one party. And what this just says is that this just has to be some high min entropy sample. So that means that if after leaking some of its bits there's still a lot of entropy left then he cannot do anything based on the properties of the extractor, okay? And we all like by plugging in a different encoding scheme we almost immediately get non-mailable secret sharing we just need to make some small tweaks. So the one thing that we need to prevent if we want to have non-mailable secret sharing is that in the construction that I said before whatever encoding scheme we use it doesn't prevent that the adverse we could just override a share with some default value. Okay so in this case the adverse you could just go and override the second share here with some default value. And this could potentially lead to a reconstruction here that reconstructs to related secret to get like a, if you wanna think of a very simple example think of a modified Shamir secret sharing, okay? Like imagine you have Shamir secret sharing and you are given a non-minimal authorized set. Now what does modified Shamir secret sharing scheme could do is could say okay I will take a minimal authorized set and reconstructed secret and then I will have a special kind of share and for every occurrence of this special share I will add plus one to the reconstructed secret. So in this case if I had this kind of artificial secret sharing scheme I could override this thing here with this special share and this would result in this constructing a related secret, okay? So this is kind of an artificial example but the compiler has to deal with all kinds of secret sharing schemes. But this problem is solved in a very simple fashion so we just add a nonce to every share so now rather than encoding the first share, the second share and so on we just pick an additional nonce R and then this encoding will basically be the first share concatenated with R and so on and the reconstruction function is modified accordingly that it reconstructs the blue shares and if the nonces are not consistent then it will abort and otherwise it will reconstruct the secret because now if you were to override a share you would need to somehow know R which you don't so this is kind of why this nonce prevents this attack and I won't go into details like what encoding scheme you have to use but basically it's similar to the encoding scheme that I just showed you for the leakage resilient secret sharing just that it has kind of some extra non-mailability properties and then these non-mailability properties directly transferred to the secret sharing scheme that we construct. And then pretty much the same trick that we did through this talk so far you can also play to get something that we call leakage resilient or non-mailable threshold signatures so what you just do is so in a threshold signature scheme you have a key pair and the key is split into a bunch of secret like key shares and all of those key shares can be used to sign messages and then these signature algorithms produce signature shares and from these signature shares I can basically construct a signature for the message that will verify under this public key and then we introduce non-mailable secret sharing non-mailable threshold signatures where we require that even if kind of the adversary man is allowed to tamper once with the vector of secret keys and afterwards he's allowed to query for signatures on messages of his choice he should still not break the unforgeability guarantee and in a similar fashion we get something for leakage resilience so here there are the secret keys the adversary gets to see some leakage on all of those keys and again then like in a chosen message type of security notion he should not be able to forge a message so I won't go into detail how we construct it but basically the constructions are kind of similar to what I showed before of how to distribute the secret like how to split the secret shares or the secret keys in this point and how to distribute them among the players so with this we kind of get leakage resilient and non-mailable threshold signatures yes questions? We have time for questions and both authors will be on stage to answer them as you ponder yours, I have one of mine can you speak of applications of your scheme and how close we are in terms of concrete parameters to being suitable for these applications? Let me think about practicality so the main issue with this to answer this why for me it's a hard question to answer is because I'm not sure what you would consider a practical parameter for the threshold signature scheme for reasonable values of N I think it is like you get somewhat larger secret keys than you have in the original threshold signature scheme but they're not extremely large I think this could be practical if you wanted to do something like this Any other questions? Well let's thank all the speakers of the session Thank you


Yo, it's poppin' dude. Felix out here, VB. You know what I mean? Ah, ha, ha, ha, ha. We're taking this back, mother. Let's get it. Yo, set a rip! Ah! Vambian is the one space where, artistically, you can just do whatever you want, and, individually, to be able to come together as a collective, that's what it just feels like VB's about. VB, VB, VB, VB, VB, VB! Exit bright to Exit 33A, state group 27 South, Brockton. Brockton is the hometown of everyone in the group, actually. The majority of us went to Brockton High, and we all knew each other. We was all friends, and, from that, it led on to Vambian. Champion Records is a brotherhood collective of 13 strong, independent, hungry black men from Massachusetts trying to make a way. Confidence plays a big role. There's a lot of different personalities. These are even things I fight sometimes. At the end of the day I know my message and what I care about is what's going to make me stand out amongst the crowd. My name is Jals. I go by Meach Bull. My name is Luke Bars. My name is Arley. My name's Ben Juligius. My name's Jals. My name's Ben Juligius. My name's Jals. My name's Ben Juligius. So, how do you stand out? I'm big. So, I think it's not about standing out. We all just mesh well together. We're all so different in our art, in our expression, but we know how to blend it in. And the ambience is deeper than rap and it's just beautiful to be a part of it, as you can see. Quincy hit for real once the studio shut down. Like they said the whole world shut down to whatever. Once they shut the studio down, we didn't know what to do. So, our solution was coming to this backyard. And that RV behind us is where we will record in music for like two, three months. Hold up, man. Michael, look. What's up? You can see how the floor's not even stable. The floor's not even stable. We see the league. We ain't care about none of that, man. The thing is we were here during the winter, so it was cold. We had the low pop filter right here, the mic. Sometimes the mic would be in here. Our shit's stuck. Sometimes we record in the back, and it's nasty. But the love of the game, man, you can't be scared. It's not like Atlanta. It's not like New York.  You know what I mean? Certain things wasn't set in place for us. So like, if there was a disadvantage, we made it work. Van Buren, we're about to drop the greatest album of our time now. Different flows, different ideas, different sounds. Everyone's brutal. Everyone's gonna see it coming. Facts. Yeah, they're not gonna see this direction coming. Loop is very geared towards the fashion aspect of it, because it is called Dover Street Market, which is in terms of just clothing, fashions, streetwear. And then DS Summit is really what kicks it off. And that's how I look at it. This is the bomb that breaks the door down, and we just all start running. You feel me? It's a testament to our brotherhood, the fact that we went so well with so many different sounds. It's kind of like we have a great rapport with each other. So we're in the studio every day. And it's like, yeah, that's it. You mean the studio? Man, it's just wicked. What's up? We out here at the Gino's. You feel me? ET Lior, I'm out here, you know? We so in love.  Us being here, we believe everybody should be doing just, you know, investing your own community, local businesses. You know, we all rise together.  Gino's goes up. Tell fair back, cross-match with the CC. Everybody, ask them when the game goes show up. I just want to know which foreign mode pulled out. Big bank, take little bank. And each time, we don't play middle. Y'all got to fix side, fix side. Stop it. Yes, sir. Van Buren. I see it as like a beacon of hope for a city that is in need of it. So that comes with a lot of pressure. It comes with also on the other side, it comes with a lot of, like it's a good feeling when you're able to connect with other people and really build your name up from the ground up. So when we have Van Buren as a name, it is a badge of honor because it's a big responsibility that we all have. The movement that we're going to create in the upcoming years is going to be something for the books.


Bethany says with a significant portion of our workforce operating remotely I'm exploring how SharePoint can facilitate better collaboration and communication. That sounds like a postcard. I'm interested in best practices for setting up SharePoint to support remote teams effectively, especially in terms of document sharing, communication channels, and project collaborations. Well that's just a small question isn't it Bethany? It's really small. I had just recently a project I was working on that was still living in file share with VPN in an email and I've never seen such a siloed going right the way back. They were right, still they had all older SharePoints that were 2009, 12, like going all the way back right through to 19, but they were still all on-premise and they were going to the cloud and watching these people work was so stilted and so siloed and information was lost and the teams weren't actually collaborating or communicating at all unless they were in depth by meeting and they then couldn't get their work done to then have it and shift to the other side. Now when you look at that you kind of think oh that's the norm but once you've lived in the new world it makes such a massive difference in terms of having that you know the SharePoint piece where they could just get their information from any device that alone and having SharePoint for them to be able to collaborate and just send a link instead of attachments and losing files and not knowing which version it was and then just that alone we saw such an increase in the way that they were collaborating especially with remotely with information feeling lost and living in meetings so they started to work a bit more asynchronously instead of synchronously like in the death by meeting that alone I think was just good to see. Best practices this is the starting point right everybody got shoved into the cloud because of the pandemic and right now we're retroactively having to go back and fix things you know like you get a team and you get a team there's like 50,000 teams or 10 people because every time they created a meeting so planning that architecture and starting with who needs to work together you know I always my formula is like who needs to work together what are they working on how are they going to get that work done and that's how I structure my teams but you don't have to have teams for SharePoint sites either so you know you can have SharePoint sites for the communication piece and who needs to know what when and set up your communication size but always start with the who you can shove technology out the door but people aren't going to use it unless it's usable and we do that by talking to them and asking them what what do you need to get done and who do you need to work with to get that done. But I look at this too and I think it's like is it just SharePoint are you looking at the entire platform Microsoft 365 because I mean are like where does teams fit is it depending on the size of the organization are you looking at engage you know for that for that aspect of it I mean all these pieces how they work together I mean this is such a again not a small question it is truly and it depends answer by I think those there's no wrong answer for for like what you guys have shared there but I mean my first thought is you're depending on what you want to do is first go in and define what are those the outcomes what are the goals what are you trying to do if this truly is just the SharePoint the intranet component of that it's very different than answering this question about collaboration and communication in general which can be a lot of different pieces together. So Christian I'll kind of add to what everyone has said so far I think there's a lot of things we need to think about here. Sure SharePoint might be the answer for the more formal things as far as documentation for HR or maybe the finance likes to work in SharePoint if they've been doing that for a while but for that collaboration that we're talking about that's essentially what teams was set up for was to be that central hub for your communications for your collaboration. So to what Christy and Sherry were saying it is essential to make sure that you have the right structure for a team. I think a lot of that goes to if it's not working right now get those end users in there with you and do some user acceptance testing find out what's not working so that you can reconfigure those teams if you have too many teams like Sherry was saying if we've got team sprawl happening it could also be there's too many channels right if they're having a hard time and they're overwhelmed at finding where they need to go to have that conversation or to find that information. We've got search but we know that that might not be the end all for finding things quickly that they need. Maybe it's restructuring how many channels there are and how that collaboration needs to happen there to your point Christian. I think it's also making sure that you're bringing in the right apps and services into that team and helping them to know hey you can have a planner tab here. You know you've got this one notebook that comes with it. You can add a list. You can bring in whatever website you need. So if you can design it to where it is that hub that they can get everything done that they need to you're going to foster better adoption and quicker ways for them to know oh I get it now this is the way I can collaborate and then also doing things like hey did you know you can get to one drive from teams you don't have to go out to that separate app. So then we get into the app switching and the glass over the whole of 365 with using teams. Yeah, don't be getting into that. We're not having the context switching and the app to app switching that has to happen. We could do pretty much everything that we need to do right. Be in that deep focused work. Yeah, yeah, I think you know a lot of times when I see it starting it's that creating of that just starting from the I need to create a SharePoint site just will hang on a second are you looking as you say Christian is it you're doing the internet and you need a hub and what does the structure of the organization to look like because I've seen it go really really pear shaped but they didn't want to create it where there was too much going depth. They just wanted to go wide and when they went wide it became a mess because they didn't want to do it by org structure. You couldn't find a thing so there's that internet side of it to the I'm a team and I need to collaborate as a team and you know what does it look like and if you've got a large organization trying to get to org wide after 100 it falls apart and you need to then go into vibrant gauge. So it's like what tech are you trying to you know what is the solution? What are you trying to answer here for the business? Because that is as you said you know best practice it's like well best practice but for what area cause SharePoint is a beast. So I've got questions for the question because you could use it in you could use it in so many ways. Are you trying to set up you know a brand site emergency operations that you're trying to you know there's so many different things that you could do with this technology. So best practice though is still the same you know structure. She says Sharon governance. Who are the people? How are they collaborating? Why are they collaborating or needing to communicate with the hybrid workforce? Is it you just need them to have somewhere to go and get information because you just need to share points aren't so yeah so many facets to this so many facets and one of the things that I would add which is kind of ironic considering a lot of the people on this color trainers is that so much has changed in the last five or six years in terms of SharePoint like all of you guys have mentioned that one of the things that we recommend to all of our clients is you know if we're going to be doing an internet setup or a migration or we're going to implement teams or something like that. We really push hard to have some upfront training to let them know like this is how it works now. It's kind of funny because you know even several years ago I'd walk in and admins would meet with me and be like okay well how do I do this this isn't like let's stop and let me draw on a whiteboard what it looks like now because I don't think you understand how much it's changed so I think there's an education piece from a best practice perspective for if you're especially going to the cloud and doing 365 I don't care if you are on the admin side on the dev side on the user side on the marketing communication side I do think that so much has changed that part of the best practice rollout in my opinion would be to have some element of training as you're doing this because that way people will understand what it is you're trying to accomplish. Not only that but I just did it sorry I just did it with champs and don't have the designer and everything they're not your champs the people that are managing the documentation or working or the migration they are not necessarily champs they can be they can be one and the same but you've got two levels of it because someone that's in the doing doesn't mean that they make a good champ to advocate and train and help the rest of the organization so you know we've got the volunteer and the volunteer so don't confuse the two in terms of best practice have the two groups with that education to drive forward and to do two different components when it comes to SharePoint on top of that Sharon. Don't feel the need to reinvent the wheel either because there's adoption.microsoft.com you're not the first ones and if you want to learn from the mistakes of others or you know those of us you know all of us are sitting here going call me because we can't get one. Step 2 have their white papers and awards and things like that on best practice global best practice around SharePoint don't have a look at some of them and have a look and see what they've done to help this journey they've got some fabulous content. Yeah and to Sherry's point the adoption site has some great scenarios too and they may not be specific to your industry or to the specific departments or roles that you're trying to have that collaboration for but they should be a good place for you to maybe get some ideas of how that correlates to the type of collaboration that you're looking to have and I would say early on you want to get a mix of end users into some kind of a workshop to be able to figure out as you're doing the training like Sharon was saying those are when they have the aha moments of oh yeah this would work really well for this specific need that we've had like these roadblocks with or it's been a very clunky manual process but now I get it on how this can make us more automated or have better communications and collaboration happen with that and then that kind of becomes what you then build from or know that you're going to include to help train in the future like you can use those kinds of great little bits to help you build that out and know that that's going to foster adoption if it's the things that they're excited about and that are going to help them within their department or across those business units or as an entire organization those are the little gems to find and the idea of workshopping it piloting something out trying it with a smaller group the other important aspect of this and it's great you brought up Heather the broader adoption of that too is that the more that you can align it and fit it into the culture of your organization and tweak it to the nuances of what's different about the way that people in your org collaborate you know if you have been you know an older generation of employees there that aren't as you know active on mobile devices for example you might do things differently than with you know a Gen Z and everybody is connected and they get that aspect of it but they're not going to do more of the documentation they want more of the chat in the instant versus the you know the long and you know video and documentation type of collaboration so you know if you have that chance to play around with the culture test it out and then grow it organically it's gonna have a lot better chance of sticking over the long term if you do that organic path yeah yeah I've seen I've seen quite a few organizations go and create a ton of SharePoint sites for all their various groups and areas and things like that and then teams and then I'm going hang on a second but if you create a Microsoft team team it gives you a group it gives you a SharePoint and then they've got two and I'm like guys are you know they don't understand the architecture really important because I've seen one IT fellow create a hundred and three SharePoint sites straight off the bat and made it just a oh look made a mess so yeah think about it yeah it's funny you know sometimes okay and being able to figure out how to get out of the math you know one thing I've noticed a lot of times is people that aren't familiar with teams and the fact that you're editing the file real time maybe Heather has a presentation I like the presentation but I don't realize that I'm actively changing Heather's version in teams so things like making it read only by default or changing certain aspects or explaining those aspects of this is being changed real time explaining to users you still have version history if somebody did mess up your file can be really helpful and then you don't need five or ten different separate copies that's a big thing exactly we don't need final final final final final final final final final well it's one of the things I mean where we started talking about governance you know having you know discussion about governance and part of that is exactly you brought up brought up is you know what what are the constraints that we need to have in the system what are the life cycle management what like what are we legally bound to go and do to save your backup archival of data our treatment of data kind of all those things that may already be defined for your organization so that also needs to play in if you go into building something new if it's truly a green field you're rolling out building an internet you know for the first time using SharePoint the more that you can be aware of okay what are these constraints around the system then you don't it's not going to limit you later on what you can do you already know what the rules are the guide the guardrails for the collaboration and then you build within that and then let people like one of my favorite things is to to go and build the provisioning templates there's a number of there's third-party tools there's things you can do out of the box sort of but you go build those in just so that people don't have to worry about setting the lifecycle management setting the right policies what are our sharing standards kind of all of those other things it's already established the guardrails are in so I know when I go to create a team or a SharePoint site I get to pick from the menu the options that are available to me already maybe they're still an approval process which is another thing that you need to discuss but again it you know go and figure out from governance with the guardrails have those build that into as you go and pilot in the workshop these things out and it's going to make it a lot easier for people so don't they don't get excited about something only to feel like they're getting pulled back no you can't do it or can't do it that way yeah now from an education perspective I also found that if they're creating from teams folders and everything they're creating that from there there's less mess than if they go straight to SharePoint and they start creating folders from there and then they've got files and folders that aren't attached inside the teams because it sits outside of it some of the other things that are kind of best practice like that training and education of where do they start from and if they're going to create what does it actually mean for best practice when it comes to collaborate because otherwise they find that they're losing stuff but they haven't really they just have put it in a place that it's difficult I know that recent feature has saved my time so many times in either teams or one drive just if I've recently worked on it I don't necessarily have to remember which team was I in or what is this in my one drive what folder did I store it under super helpful yeah and I mean if you're rolling at SharePoint have you rolled out one drive to go with it you know really an important component a lot of these things go hand in hand and you know so that they can work from their desktop and continue to be able to you know work that way because purely working online construct a lot of users can struggle see what I meant Bethany can of worms we talk for an hour it's a lot all day yeah yeah yeah well it's a big it's a huge topic so yes it's a huge topic


What's up everybody? This is Optic's cello pack break number 19 sold out on jaspyscasebreaks.com This is a one-pack break of cello basketball So I actually had number 18 copied in there that would have been bad. This is number 19 At the end of this break, so it's totally separate randomizer We're gonna take all 30 names and randomize them the top three names will win a spot each in the $299.99 high-end monster mixer 24 boxes. I think Steven I think Jason does on on Instagram. I know Teddy did some Leaf wrestling before so I think Jason does No wrestling like hip-hacks or anything their leaf All right, five times on both lists So remember totally seven randomizer for the giveaway spots This is just for the cello pack break And there's five four and a one five times remember when random org made us pay for their service That was such a I mean, I shouldn't say scam because we've been using their service for free for like ten years So but that kind of stunk five times on the teams Yes, I mean she might as well pulled me out as I'm the starting pitcher of game seven of the world series We're fighting a million cards in this battle and she pulls me out for an interview. I'm like, well, I gotta do it It's sports illustrated, you know It's not like, you know Some random blog I Was about to blow it off completely by I should do it. So maybe my attitude wasn't correct Jason Pacers James jazz Brian wizards actually a pretty good article. So I mean just don't go By and with the breakers who are quoted in it Stephen Kay Hornets, Jamie Bucks, Zach Suns, Sean Mavericks, Martin Raptors, Josh Heap Obadiah Bulls, Zach Celtic's Thunder, Orlando Blazers Jason Spurs, Peter Pelicans, Tony Nuggets Martin Kings Mike Magic, Andrew Timberwolves, Brian Hawks and Nets, Anthony Warriors, Mike Lakers Anthony Knicks, Jeffrey Rockets, Daniel Sixers James Clippers, Jeffrey Grizzlies and Anthony Cavs I'm gonna give it maybe half a minute for trades 30 seconds. We'll pause and Be back. All right. I haven't pledged any allegiance to any KBO team yet. The Samsung team though kind of looks like my team. They they're pretty desperate for some fans I think. All right. This is the cello pack break The Samsung Lions, I believe. I think they're like the unless I'm confusing it with the The team that won, but I feel like they were they were talking about the Samsung team as like the Browns of the KBO So I kind of feel bad Maybe it's maybe it's the other team. I'm thinking that. I don't know. It's pretty late Wow, Frank, we're signing with the Jets. I can't believe that. It's crazy. He's still playing All right, here's the cello pack. J. Georetic, Bradley Beale There's a rate of rookie. Nice blue velocity of Jalen Noel There's a Luca Brandon Clark There's a hollow Chris Paul, not numbered More of him back Lee. So there you go. That was the cello pack break Right now we're gonna randomize all 30 names. The top three will win a spot in the basketball mixer I'd like to do that tonight But if I had a guess it'll probably be going tomorrow on Wednesday Maybe Joe's one of Joe's first breaks. Joe will be on starting at 1 o'clock Pacific time Tuesday through Saturday And then I'll be coming on after his shift is over six times top three names win. Good luck There's one two three four five and six top three Zach Tony and James Congrats guys So there you go. Thanks everybody. Sorry to the people who lost But we do have another cello pack break if you wanted to try your luck Or we have a couple more full spots left if you just wanted to go grab one Check it out. Jazzpieceofcasebreaks.com


The tradition of students traveling into different destinations to spend holidays after a semester examination is facing out. Gadowville and McCauley an area dominated by students of the Banerjee State University is always vacated after a semester examination. However the reverse is now the case due to the current economic realities. Francis Tehr was out to find out the feelings of students. Calculated and I saw that if I was insist then maybe I will not be able to reach home or may not be able to come back. So I sit to read that a little money sent to me is just but enough to manage and stay. Like the last time I traveled down to Quarra State I paid only 10,000 error from Benuelins Park. It was Benuelins that I bought it and the park I paid 10,000 error as in transport. That's how I pay for the ticket. But on my wake up when I was coming back I just came recently to Commons 12,000 error. I was 2,000 error should be around tomorrow and they are talking about for 10,000 from here to Quarra State. It is very difficult. It is very very difficult and when I came around the school I can see that most of the students were unable to travel because of the high cost of transport. Most of them are staying in school today. This is the first time that for witnessing such a number of students staying back as a result of not having transport to go back to their home to meet their parents on their guidance as a result of the removal of subsidy. So many students have stayed back in their houses in school to buy some park out of school hostels to stay with their friends in school as a result of not having transport money. Hello hope you enjoyed the news please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


Everybody Matt here for late in sports car drip in 2021 Panini National Treasures football case number 118 pick your team We have Austin s Washington Austin be Niners Bernie s Jags Brent R. Bill's Brian T Broncos Brian P Seahawks chiefs Clayton R. Browns Corey s Colts Giants D W Cowboys and Steelers Edgar B Cardinals Panthers Eric our Bears Harper be Bengals Chargers Jets and Dolphins Keith s Vikings Kenneth H. Falcons Kristen K Raiders Mark s bucks Matt P lions Drew B Patriots Noah H. Saints Raquel be Eagles Roy D Ravens Ryan M. Ram Stewart Z Packers Timothy W. Titans and Zach M. Texans All right, here we go. Good luck everybody again six to go in each of our flawless case breaks up after this first up to 20 Barry Sanders as Card Lions It's just a Tucker to 99 So when he picked the 66 yard You have to find number 66 So it's like a 66 yard Oh, yeah, true. There's Jags patch to 49 James Robinson Vikings patch 25 Robert Smith Dolphins dual Jersey to 99 to a and Saints rookie dual patch to 49 Ian book you go Saints Chargers to 99 rookie Otto Trey McKinney and Bills true RPA 17 of 99 Greg Rousseau go Buffalo. This is Colts auto 49 Darius Leonard and redemption Falcons, that's rookie material signatures RPS Kyle Pitts There you go Atlanta. Nice hit for you Kenneth H box to Thank you all for hanging in there tonight. I know we're behind schedule 49 Justin Herbert Chargers and to 99 Rams Aaron Donald. This is bears Hall of Fame Jersey to 99 Mike Singletary Let's fill up flawless case number 57. It is up next till some big teams available At Panthers jumbo Jersey to 99 DJ Moore named fabric This is Colts Jersey to 99 Jonathan Taylor. Here's rookie dual patch to 25 Khalil Herbert You go bears this is Washington rookie auto to 25 Jarrett Patterson Steelers field pass rookie auto to 99 Najee Harris Awesome looking card. Yes.   That was fun. Let's do something like that again That is to 49 Josh Jacobs Raiders to 99 Travis Kelsey chiefs Jersey to 99 Jim Kelly. This is Niners Patch that's one of 25 Ricky waters That was a big Ricky waters fan Ricky waters and William Floyd man that back feels awesome This is Chargers rookie jumbo patch to 25 Josh Palmer and Jets rookie dual relic to 99 Zach Wilson More Zach Wilson. This is Vikings Rookie patch auto to 25 Kane wangoo Thanks Jason appreciate it. Thanks Maddox So sick Ravens auto to 25 Terrell Suggs This is Niners to 25 signature treasury triple relic auto Jerry Rice congrats San Francisco great hit awesome card Niners and Giants rookie patch auto four of ten Cadarius Tony Yeah, rookie glove signatures Nice hit Giants Last box we will do a hit recap at the end Flawless football is up next. Let's get those filled up six to go and each of those flawless breaks 25 Matt Ryan to 99 Miles Gaskin Rams Jersey to 99 Cam Acres was a Texans price Yeah, they were marked down I'm not sure what what the actual price was Chiefs patched 25 Len Dawson 17 to 25 almost got the Jersey number. That's Steelers quad patch 10 of 10 big Ben James Harrison Jerome beddison Heinz Ward nice hit Steelers Dolphins rookie dual patch nine of 17 Jalen waddle very nice This is Rams redemption It's rookie patch autographs Jacob Harris and Lions One-of-one rookie dual tag auto Amon Ross St. Brown Congrats Detroit Lions Awesome hit that is Matt P with the NFL PA dual tag Rookie auto very nice. This is Packers Auto to 99 Charles Woodson. Don't leave yet, Zach Don't leave yet in a little last spot magic here Texans rookie patch auto to a five Davis Mills congrats Texans great way to close out the case two of five horizontal RPA Eight two times five equals 10 equals Jersey number true. Yeah, we're gonna do a hit recap Yeah, no problem that congrats man Appreciate you closing out the break. I'm glad we hit something man. Thanks Ryan. Appreciate that awesome hit great case man That's awesome. I'm gonna say awesome one more time One of my goals like every since I've turned 40 one of my goals every year is to stop saying cool and awesome as much And by like January 3rd, I give up All right, here we go first the relics we had a nice one here for the Dolphins 17 Jalen waddle rookie dual patch Steelers quad patch to 10 Big Ben James Harrison Jerome Betis Heinz Ward Chiefs 25 Len Dawson Rams 99 cam acres Jets 99 Zach Wilson Chargers 25 Josh Palmer Niners To 25 Ricky waters Bills to 99 Jim Kelly bears 25 Cleo Herbert Bears 99 Mike singletary Colts to 99 Jonathan Taylor Panthers to 99 DJ Moore. It's either rookie premiere signatures or rookie photo shoot. I'm not sure Yeah, sorry drew Saints 49 in book Dolphins 99 to a Vikings 25 Robert Smith Jags to 49 James Robinson Packers autos Packers to 99 Charles Woodson redemption Rams RPA Jacob Harris That was night or signature treasury triple relic auto Jerry Rice Ravens to 25 Charles Suggs Washington 35 Chris Cooley and Steelers to 99 Nashi Harris Washington 25 Jarrett Patterson Colts 49 various Leonard and Chargers to 99 Trey McKinney we had bills true RPA to 99 Greg Rousseau had Vikings 25 rookie patch auto Kaynay Nwangu Nwangu Falcons redemption rookie material signatures Kyle Pitts Giants rookie glove signatures to 10 Kaderious Tony We had Lions rookie dual tag auto one-of-one Amon Ross St. Brown nice hit Lions We had Texans Horizontal rookie patch auto two of five Davis Mills some of the nameplate there looks like it probably said rookie Great hit for the Texans and big hit of the break Jets true RPA to 99 Zach Wilson Congrats again on that Harper great case. Thank you everybody appreciate it. We have flawless coming up next


So this is what I've learned in seven years of podcasting about Ruby. I'm gonna give you a brief history and then I'll talk about some of the lessons I've learned. But first, I'd like to thank the RailsConf organizers for putting me right in the middle of nap time. I really appreciated that. And in case you're wondering, yes, this is my son a couple of years ago. And yes, he is face down on the floor. He just fell asleep there like that. But anyway, gonna have lots of pictures of my kids and stuff too, so it's not a super serious talk. But yeah, I figure as I was talking to people, they were like, well, you're at the same time slot as Sandy met. So I figured out that you all must be one of these three groups. You're either a die hard Ruby Rogues fan, for which I thank you if you are. You don't know who Sandy is, or your overflow from her talk. Or you didn't wanna hear about nothing or something, or something or nothing. Or you didn't realize that we have a rock star next. In fact, it wasn't fair for them to put Kent after me cuz I mean, that's just a hard act to follow. But so you didn't know that you had to save front row seats to see Kent. Ultimately, the purpose of this talk, though, is to inspire you to go out and contribute to the community however you're gonna do it. And so these are lessons that I've learned as I have been involved in podcasting over the years. Over the last four years, I've been involved in these shows. And those are the stickers that are up here as well. Ruby Rogues, we started four years ago. I'll talk about kind of the origin story there. JavaScript Jabber and the Freelancer show started about eight months after that in January of 2012. And then I started iFreaks about a year and a half after that. And then Adventures in Angular started in July. So if you are interested in that, then that's been growing pretty rapidly. When I got started, I started a podcast called Rails Coach. This is not the original artwork. I had this done later because I planned on relaunching it and I never did. And then I also took over Teach Me to Code, which was screencasts about how to build things in Ruby on Rails. And I'll talk a little bit more about those as well. But did anyone listen to or watch any of these? These two? Yeah, a few people. So yeah, I mean, it's been kind of this wild ride. And I renamed Rails Coach to Teach Me to Code. And then I started another show called Rails Coach. And yeah, it's been this crazy thing. And then my latest project has been Rails Clips. And we just did a Kickstarter campaign for that. We being I, I guess. And the idea is that we don't have Railscast anymore. I wish there was Railscast, so I decided to do that. And so I'm gonna be putting out videos every week. You can subscribe just like Railscast Pro. And hopefully we can cover topics that are interesting to you. In ways that we can't really do with the audio format. But ultimately, I'm just gonna tell you my story. So these are my kids. This was also a few years ago. And I think she was three or four. And yeah, she was reading a story to her one-year-old brother. The story of me getting into podcasting is, it started when I was working for a company called Mozi. Now Mozi, they do online backup. I'm not gonna tell you the long and sorted tale about how I wound up in QA. But I was working QA and there was the other person in QA that I was working with at the time. He got one of these brand new devices. And it looked about like that too. And it was like this mind-blowingly cool technology that they don't even make them like that anymore. But he started listening to podcasts. And so I'd be sitting at my desk working and he'd be sitting in the other corner of a very small room working. And he'd be laughing at stuff that people were saying. And so I figured out pretty fast, he's listening to podcasts. And so I was like, well, I can't afford an iPod. But this sounds like fun. And so he explained to me that I didn't need to go get an iPod. I could listen to them off of iTunes. And so I got a little Mac mini, put it on my desk, which ultimately led to me running the beta test for the Mac client. But anyway, and I started listening to podcasts. And it was really interesting because I started finding podcasts about things I was interested in. One of them that some of you may have listened to. In fact, show of hands, how many of you listened to Rails NB way back in the day? Right, with Greg Pollock. So I was really new. I had done Ruby on Rails for like a year before I was in QA. And I was super excited about this show. And I thought, oh, everybody in Rails is like so much better than me. And these guys are celebrities. But I decided, what the heck, I'm gonna try something new and I'm gonna start a podcast. Another side note, this is a hamburger with egg and bacon on it. And if you look real close, the bun is a donut. Donuts, so anyway, it was actually pretty good. Anyway, so I decided to try something new. So I knew zero about podcasting. I'd been developing Ruby on Rails for like a year. It wasn't even my full-time job for the duration I did it. So I had no experience with any of it. And I emailed Greg and I was like, Greg Pollock, you are awesome. I wanna start a podcast. I wanna talk about Rails. I don't wanna start another Rails NB podcast. So what do I do? And what surprised me was that he came back and he said, that's awesome. You should start a podcast and here are some ideas. And he basically encouraged me to do a show where I would interview other developers. And so I reached out to somebody that I had already been in contact with. And Greg was the first interview I did for that show. So the first one, the first episode was what I thought made a good developer and the next one was Greg Pollock. Well, about three episodes later, I interviewed James Gray. You can kind of see where this is going, right? And he offered me a bunch of feedback on the way that I did the show, which kind of changed the way that I approached things. And one other highlight, I was actually at RailsConf. It was like 2008 or 2009. I don't remember exactly the year, but I was walking through the crowd. It was like the second day of RailsConf. And there was this empty seat right next to this guy. And I was like, I would love to interview David Hirenmeyer Hansen. So I sat down next to him and started talking to him. And as a new Rails developer, you can imagine, who here thinks David is intimidating? Maybe a little bit. So I was scared to death. And I sat down and I started talking to him and I was like, I have this podcast and I'd love to interview you. And he kind of begrudgingly said yes. I don't think he was super excited. But he came on the show and I interviewed him. It was like episode 50 of the RailsCoach podcast. You can find that on TeachMeToCode.com. But what this taught me was that you can be bold. You can go out and do things that are really scary. You can find opportunities in these places where you're not really sure what's going to happen next. Or where you feel like you might get shot down. Or you might fail. But you have to be bold. You have to go out there and just take charge and be excited. And find these opportunities. And this also affected the way that I code. And I started taking more risks in the projects that I would accept. Or in the way that I would approach specific problems. And this led to a lot of different things. I must have started like five ORMs. Jeremy knows how much work that is. But it was really an opportunity for me to grow. And it led me to other places in my career, my coding, and in my professional life. The other thing that it taught me, going back to the incidents with Greg and James, was that sometimes you have to ask for help, okay? So you might get stuck, he got stuck. And my wife went to help him out. And then stopped and said, get the camera. And so, yeah, but yeah, his foot was stuck in the drain. And we just popped him out right after that. But you may get stuck, right? You may find that I don't know what to do next. I don't know where to go. I don't know how to proceed. And if you ask for help, what you'll find is that a lot of people want you to succeed. So sometimes you'll find a mentor. Sometimes you'll find people who are willing to give you money or resources. One incident that comes to mind is with Teach Me to Code. Before I was doing Teach Me to Code, my friend Eric was doing Teach Me to Code, Eric Berry. And he started it and he started reaching out to a bunch of us in the community to start making videos for his video series. And so I put one together on Rails Routing. It's really old, don't go watch it. But what happened was I did the video and then I started tweeting and blogging about some of the things that I had struggled with. I didn't have a good mic and I didn't really have. I'd use a trial version of software to record the video. And I got this email out of the blue from Telestream. Telestream is the company that does ScreenFlow. Who here uses ScreenFlow? Anybody? Yeah, awesome company, great product. And they sent me a free license for ScreenFlow and a $200 microphone to record my screencasts. I've also, over the years, I've asked for help in finding work. I've asked for donations to the podcasts. And what I've found is that all of the listeners, all of the people who are involved in the shows, David Brady's found me work a few times. If you ask for help, people just will come out and help you. And I found this even for people that don't have a platform or people that listen to them. I mean, some of this stuff happened when I didn't have anybody listening to me. And so if you take the opportunity to find people who want you to succeed and you ask for help, you'll get it. One other thing that I've seen is when other people ask me for help, and this is kind of the reverse. But a lot of times I wind up saying things that are way smarter than I thought, right? And so sometimes the help will come when you have a sounding board. It's like rubber ducking, where you have a duck on your desk and you talk to the duck and you explain the problem. And then the solution comes to your mind. And that happens pretty commonly. I mean, some of the things that people tweet that I said on the shows. I didn't even know that I knew that stuff before I said it. And so just by asking for help or discussing the issues with people will give you opportunities to learn and to grow. And so that's just another example of some of the things that I've learned over the last few years doing these podcasts. Another thing that you want to do is experiment. And we've had, I've listened to talks about experiment driven development, or using scientific methods for exploring different aspects of code. There are a few people that really inspire me to experiment. Dave Thomas is one of those. I mean, every time I talk to the guy, it's just like, I feel all creative again. The last episode of Ruby Rogues, we had him on, and there's a lot of that in there. In the business, I have a friend, Stephen Robinson. He runs rubynow.com. And he encouraged me to actually split the sponsorships into levels. And to charge more for the first one, and charge differently for the different sponsorship levels. And just to experiment with them and see what worked. And that worked out very nicely. And I've tweaked that a little bit as time goes on. One other thing that I've really learned from Ruby Rogues, and this comes down a lot more to more of the social areas of Ruby Rogues. I don't know if people really realize how diverse a group we are. Beyond the obvious things, gender and race. Over the years, I mean, we've had very different political views, religious views, views on the way the world works, ways that the world should work. And having the opportunity to actually explore those areas and have a safe place to talk about these ideas with the different experiences not just in code, but in life, has really been a tremendous blessing for me. And in some ways, it's strengthened the stances that I have that are different from the other Rogues. And in other ways, it's really helped me to understand why people think the way they think and then to approach my own thinking and change the way that I think about things. And you get this in code and I think we come to conferences to kind of get these ideas. But I encourage you when you get these ideas or when you talk to somebody with a different background than you or different lifestyle than you, that you take the opportunity to really go explore that and experiment with it.  But I can think about it and I can think about where that would take me. And I can really come to understand where people are at. And this is something that really came out in the Ruby Rogues retreat that we did a few years ago. We had the opportunity to all get together in one house and just talk. And we were working on a book that never materialized. But ultimately, we really did get to explore these different areas of where other people are at. And we did have a very interesting group. I mean, if you ever want to find somebody with a very interesting background, go talk to Katrina Owen. Just fascinating some of the things that she's been through. James Gray is another person with some of the health challenges and things that he's had in his life. And he's given talks on this and you can go look them up. But just imagine how that affects the way that he approaches life and approaches code and approaches his family. There's just so much to learn. And having this opportunity to kind of experience things in a small way through the way that they live is very interesting. I'm gonna talk a little bit about how we got into Ruby Rogues. So as some of you may or may not know, I'm a big fan of the TWIT network. Does anyone here listen to those podcasts? Yeah, one or two people. So I'm a big fan of Leo Laporte.  So for the most part, though, it's just interesting, stimulating conversation about technology. And I had been podcasting for about three years. And I'd been thinking for a while that it would be really nice if we had a TWIT style show, which means that you bring in a bunch of panelists and you talk about the topics or the news of the day or whatever in technology. And I thought that would be really cool for Ruby. But I don't know why, but I never actually pulled the trigger on that. And then one day, James tweeted on Twitter, I guess that's redundant, tweeted on Twitter. But James tweeted and he said, hey, look, it'd be really cool if we had this panel discussion on Ruby. And of course I replied back, I've been thinking the same thing. And so we started to pull people together and pretty soon we had a panel. Now that panel stayed together for all of three months before we had people drop off and we replaced them with new people. And so we lost Aaron Patterson and Peter Cooper but picked up Obdi Grimm and Josh Susser, who are some of my favorite people in the whole world. So we started Ruby Rogues. That was four years ago next week, I think. And it was just awesome. And we've had a good run, we've really been enjoying hanging out. We've since replaced some of those folks with other folks. So now we have Jessica and Coraline and Saran on the show. And I don't know if David has anywhere else to go. So it's just this tremendous opportunity for us to sit down and talk and really explore where we're at. And so I really like the idea of experimenting and taking the things that we're learning from each other and just seeing what they're about. I also learned and I talked a little bit about this with Be Bold but being confident. So I may have an opinion that's different from one of the other Rogues. And that's totally fine. But it's that intersection and talking about where they don't line up. That's really the interesting conversation. And a lot of times what we find is that I'm willing to make trade-offs that they won't or they're willing to make trade-offs that I won't. And sometimes it just turns out that they've experienced something with an idea that I haven't. And so it was a negative thing for them. It was a positive thing when I tried it. And so by exploring these things we really get to figure things out. But initially when I was on Ruby Rogues I was very reticent to disagree with anybody on the show. And a lot of times I'm still pretty diplomatic but most of the time it's in areas that I really feel like there can be multiple right answers. And so then I just tell people what I think and then I accept that other people may have another opinion. But the times that I really struggled with Ruby Rogues or with any of the other shows were the times that I really wouldn't stand up for what I thought or where I wouldn't share my ideas because I didn't think that they merited the same consideration that the other Rogues did. And being confident also extends to code. And I like drawing these lessons from life to code because a lot of them really apply. So if you have a good idea, share it. If you have an approach that you feel I can really make things better in your code, then try it, do it. I mean, sometimes we're on teams and we can't always do it both ways. But at least bring the idea up and stand behind it until you're convinced that it's not the case. And I think the other side of being confident is also being humble enough to accept that somebody else may have a better idea. So your idea may be good, there's maybe better. And if they can present evidence to that, then be confident in switching. But more and more, the more I really stand up and tell people who I am and share what I'm about, that's really where I shine and that's really where I feel like I write my best code. So one other thing I want to talk about is there have been times, especially since I went freelance, where things got really tight money wise. And I've gone on the show a few times and said, please donate or whatever, or please help me find work.  And when you're behind the microphone, I mean I don't see the listeners. And when I go and look up how we're doing with the show, all I see are numbers. And so I know people are out there and there may be a few people tweeting at me here or there during the day. But a lot of times it's really easy to get discouraged. It's the same thing with our jobs, you feel like you're not progressing the way you want.  Or you feel like nobody recognizes the work you put in. And it's easy to get discouraged. But the thing is, is that ultimately, if you really reach out, if you really look out there, there are people that benefit from what you do. And it's also okay to do something a little bit different. And that's where some of these other shows came out of, was, I don't feel like I'm growing a lot in Ruby, so I started an iOS podcast. I mean, that's where iFreaks came from, I wanna learn how to do iOS. And so if you find ways to kind of shortcut the discouragement, then you can really reach beyond where you're at. And back when I was doing Rails Coach and teach me to code, teach me to code did have at least several hundred people that were watching the screencast regularly. Rails Coach I don't think ever got over like 150 to 200 people listening to it at a time. And I really started to feel like, okay, I don't know if anybody cares. But ultimately, for the people that did care, and I did get phone calls from people wanting to hire me and things like that. If you make a difference for one or two people in a major way, it really, it really, it can make a difference for you. In fact, that's the next thing that I wanted to talk about. So one of my favorite stories about making a difference, we had Greg Bogus on the show. I don't know how many of you remember that episode. He talked about mental illness and depression. And he has a pretty, it's kind of a scary story about his depression. And then he got through it and kind of reached a point where he's healthy and happy now, but it's something that I had never thought about. Well, last year I went to a conference called Agile Roots. Which is a conference in Utah about Agile development. And one of the staff members there during the lightning talks, because they had like four people sign up for lightning talks.  So he got up and he said, I listened to that episode. Now this isn't something that I feel like I did other than maybe highlight the conversation a little bit by getting him onto the show, myself and the other rogues. But he listened to that episode and he was in a similar place. And so he went and he got help. And he's like, my life is better. I have a better relationship with my wife. We now have two kids. I mean, all of these things that made a major difference for him. And I've heard other people that they listened to an episode about some technical topic and then they go and explore it. They kind of become an expert in that area and then they get a better job. You know, they move into a better life, they move into a better place. And it's these conversations that I think really make the difference from Ruby rogues and the other podcasts that we're involved with. Is that if you don't have to start the conversation. But if we can shine a light on the areas that make differences for other people and have those conversations. And sure some of them are used caching in your Rails app, your life will be better. And some of them are go get help for depression or be more aware of the minority or marginalized groups in our community. And all of these things make a difference to make things better for somebody. And so I don't take credit necessarily for starting the conversations. But in a lot of cases we've been able to have the conversations or continue the conversations in a more public way. And it really does make a difference for people. But honestly, and this is the thing that I really want you to take away is that if you're writing a blog post about how to handle an error or a blog post about how you struggle at work. Or you put up a podcast about something you're interested in. Or you start making videos or something like that. There's somebody out there that needs that information. And whether it makes a difference in their home life or makes a difference in their other endeavors. You're making a difference, you're doing good. And I think it's really important to be able to do that. And so all of the other lessons that I've been going through, I mean they all lead into this is that you can make a difference and people matter. I have to say that there are a couple of main reasons why I do the podcast now. And I kind of talked about having these conversations. But the conversations don't just happen with me. I mean they happen with people like Coraline and with Jessica and David and Abdi and Serran. They've happened in the past with Josh and James and Peter and Aaron. They happen on the other shows with a lot of other friends of mine. And to be honest, the biggest draw for me at this point doing the podcasts is that I get to talk to these people every week. We get to have conversations with my friends, with people that I care about. Every week about stuff that I care about, at least most of the time. And it makes a big difference. And these people matter to me. Coraline was out at Mountain West Ruby Conference and it was terrific to say hi and spend some time together. I got to see Jessica because she came out for the Pluralsight Author Summit. So I had dinner with her and her husband. And it's these connections. It's the connections that you all are making here at RailsConf that matter. I mean, sure, you're gonna pick stuff up from the sessions. And that's why your employer sent you here, I'm assuming. And you're gonna be able to make a difference in your work. But in the grand scheme of things, the people that we meet and the connections that we make are what matter. And so that really kind of explains the rest of the reason why I do the shows. Beyond being able to talk about stuff I like and talk to people that I like about it, is that then I get to have the conversations with you folks. So I get the opportunity to come out here and meet interesting people. I mean, I can name a few people in here. I met Zach the other day. I met Jeremy at Mountain West Ruby Conference. I've known Jim for a couple of years. And it's these connections, these opportunities. I can't see you in the corner, so if I know you, I'm sorry. But it's these opportunities to meet new people and make these connections and feel like a community that really make the difference and then being able to give back and make a difference in their lives in smaller big ways. That's what really matters. So I just encourage you, if you feel inspired to go out and do something, it doesn't have to be something big. One of the things that I did in the past was I wrote a little gem that uses Project Honeypot. I don't know if you're familiar with the project, but it identifies IP addresses for spammers, right, a little gem. It doesn't have to be a big thing. It doesn't have to be scary or frightening. You don't have to feel overwhelmed by the people that you want to talk to, but I have the conversations at work. That makes a difference. But whatever it is, find ways to encourage people and make people feel like they matter. And you've gotten to see a lot of pictures of the people that matter most to me. These are my kids. My wife took the picture. She doesn't like taking pictures of herself, so I didn't have any funny ones to share with her. But anyway, I'm Charles Max Wood at CmaxW on Twitter. And that's my email address. If you have any feedback, if you want ideas or encouragement or help getting started, just let me know. And that's pretty much it. One other thing, though, is that we're working on new material for our slides next year. So, do you have a question? Picks? Thanks. So I've got about 10 minutes for questions, which is kind of where I wanted to go. So I'm happy to answer questions about the stuff that I talked about here, or Ruby rogues, or podcasting, or anything else. But I reserve the right to say I don't know. So Jim's asking how we record the Ruby rogues episode with all of us being in different places. Yeah, we just record it with Skype. And if you want to see the rest of that set up, I have, if you go to TeachMeToCode.com, it's the last video I put on there. It's about two years old, but I'm still using the same setup more or less. And that'll show you how I record it and things like that. But yeah, we record over Skype. And my internet connection has been slowly degrading. Thank you, Comcast. But we're switching on Saturday, so hopefully it'll get better. But yeah. So yeah, we record over Skype. I have lots of ideas of things you can do. So if you want to contribute to the community, and you're not quite sure where to go, just come talk to me. And we'll figure out what you're about. All right, I don't see any other questions. So feel free to come up and get stickers. If you want Ruby rogues stickers, just tweet at me. And then I'll see if I can mail a couple out.


Alright so we're back in the workshop that has unfortunately burned to a crisp. It's been two months from the fire itself and the worst thing is that I have not been able to touch this. It's just been kind of stuck in this limbo of everything being destroyed and not able to actually move on and do anything. Then it advised to me that not until insurance is done that I can't touch anything because that could be considered destruction of evidence. It's been very frustrating and painful process. Not something I wish on anybody. Really frustrated with all the insurance. Nobody answers my questions. Everything just takes way longer than it should. The insurance company that we hope was going to cover this and that policy to actually review it. So they got assigned it and I tried calling and emailing without a response for two weeks and it wasn't until I looked up their number, their manager's number, I had to start calling them every hour on the hour until they finally responded. And unfortunately at this point through a very long and painful process insurance is denying coverage of the structure itself. The parent gap in our coverage, not seeing much more options at this point that we were covered under our existing insurance for a rented space but apparently did not extend to here. I couldn't pursue legally trying to challenge it but it sounds like it would be an uphill battle and likely would cost more in lawyer fees than I would get in the end. So we'll finally start the cleanup process and clear out this huge mess. See what we can recover, see what's salvageable and figure out where we go from there. While we go through all that, our production is going to be a little bit slowed down. So I want to give an opportunity for at least my creators who are interested in producing a video for our channel to reach out, shoot me an email and there will be compensation to that beyond just exposure going to actually pay you. It seems like a good opportunity to kind of offload some of our work while we're busy with all of this and we'll also have a chance to kind of highlight some smaller creators and give an opportunity. The good news is we had separate policies for the items inside the garage so those are all covered and the other good news is that the GoFundMe we started been really amazing and just how much people have been willing to donate to it and it is like the going to give us enough to at least rebuild what we have. Not really sure how much it's going to cost to rebuild. Despite everything in here being pretty much destroyed, we had a lot of our old projects kind of been archived. Got about 30 or 40 items, set up an auction page, this is kind of a rare opportunity to buy kind of a piece of how to make everything. If there's other objects that aren't up for sale that you are interested in, let me know and we'll consider doing a follow-up auction with some of those items. But otherwise, check out the auction and see if there's anything you want. This video is sponsored by Trade Coffee. Trade connects you to the best coffee from the nation's top roasters and delivers them right to your door. Maybe you prefer the dark savory notes of chocolate and marshmallows or the bright pick-me-up of a light roast. You can now find out with Trade Coffee. Maybe you can travel to the mountains of Mexico to cultivate your next cup by hand but you can still tour the globe and taste the difference. So how does it work? Step one, take the quiz. Answer questions about how you like your coffee and Trade will carry matches just for you. Step two, delivered right to your door. Choose your delivery frequency and it will appear at your doorstep delivered at peak freshness. Step three, rate and repeat. Rate your matches so trade can continue to delight you with coffees you love. Trade uses a sustainable and compostable packaging to ship their coffee in because they love the earth. All coffee is roasted and shipped to you within 24 hours of ordering. Trade guarantees you love your first coffee. If you don't, they'll ship you out a different bag for free. Just take the quiz by clicking the link in the description to get started. Free shipping is included, also free coffee. Use the link in the description to get your first bag from Trade Coffee for free. Explore the best coffee in the country with Trade. So like Andy said, we have a bunch of things for auction. It's going to be on 32actions.com and it is live now. All right, straight from the Mississippi Gorge and to your lips, a beautiful ocarina made from dirt. Lovely. From the same episode, we have this gemchorn, a bison horn flute, ethically sourced from the Como Zoo. How do you play it? All right, our cameraman, Joey, made this beautiful bamboo flute. I don't know how to play this. Here we have some early papyrus paper. It's clearly an attempt, but it's good. Well, I made this, so I'm biased, but this is the best thing we've ever made. It's a beekeeping mask made of willow branches and linen and it actually works and Halloween's coming up. So spooky. But if you weren't excited about just that, there's two. His and hers. Beautiful. This is a bamboo bow. Bundle bow? Bundle bow. Here we have the bamboo bundle bow. Fishing pole from the fishing pole episode has bronze eyelets and is made from wood. The reel is broken right now, but it's made of bronze and we will find it. I did catch a fish with this, so it does work. This is from the paint episode where Andy made his own paints and this is an Andy original painting. He will sign it.  Oh, and there is some corn stuck in it from the corn cannon episode. Cool. A little extra for free. Most things come with bonus corn. Upon further investigation, this is actually a bug. And then there's other little, it looks like fruit flies, so this is a living landscape. I like this painting. I think this is good. These are skis. These are made from box elder. Winter is coming, so strap up. They have been tested. This is very heavy. PUBG armor from the PUBG armor episode. We got bronze, steel, obsidian, clay, a lot of stuff going on here. Leather. Leather. Will it stop a bullet? Yes. I'm going to put it down because this is very heavy. Straight from the summer of 2019 into your home. This is the flamethrower guitar. Flamethrower has been disabled for your safety. From the beer episode, this is a fermentation vessel that we used to make the beer. And it could be a nice milk drug. This was the live stream DIY toilet paper. Great for a guest bathroom if you hate your guests. It's not been used, so sorry. This was our first attempt at the distilling vessel for our moonshine episode. So this is the one that worked because I made it, and this was the one that Andy made. Nice little friend. Good home decor. This is one of the first metal tools that we made. It is a native copper axe sourced from the mine in Michigan that we went to. I wasn't there. The proverbial we. Also made of native copper, this is in ads. Also used for chopping wood and other chopping activities. From the caveman brought episode, this is a cast bronze sickle made with help from Greg the sword casting guy. Used for harvesting grains. Very sharp knot, a toy. Hammer made of cast bronze. I have used this a lot, and it works. Might be a nice set with the sickle. It's commy. No. You're canceled. I was set up. With by chance you do casting at home. This is a cast we made but never used. This is an axe adds head combo mold. Pour it in. See if it works. These are also molds. This one's a bell clapper, and this one's Dobby. A ceramic oil lamp. Just put the wick in, pull it out through here, light it, lamp. What else do you need to know? Hemp sling. Put the stuff in here.  That is cool. And I'm getting my wallet out. Made of clay, a special note written in our own language. What does it say? It's a mystery. Figure it out if you can. We have a ceremonial dagger from the city of Orr. It's nice. It's heavy. Made of bronze. It was cast.  It's got my finger prints on it, frame me for murder. Please don't. I will be wiping it up. Okay, this is cast bronze that we were going to make into a saw similar to this, but we never carved the teeth into it. So DIY project. This was cast with Greg in Austin, Texas. Greg, the saw casting guy. All right, this is my very first project, a heckle. This was made so we could heckle the flax, kind of rake it through there. Very nice artifact for my time. Deer parchment. Good for things. This is leftover deer parchment from the book episode. Here it is. You ever have a moment in your life where you're like, what's going on? This is a greasy pig hide as from the drum episode. There it is. RIP. The very scissors that Andy made and then cut his own hair with. This is cast bronze and functional, if you're strong, especially made by Greg, the scissor casting guy and this Athenian sword with help from bronze casting guy made with help from Greg, the sword casting guy. It's starting to patina due to age. Greg's debut video was making this. The practice football for the creepy football episode made with real cow hide football. All season is upon us and press your friends. Here's some bread from the bread episode, fresh artisans, a nice two year old loaf. These are the only remaining artifacts of our lathe. This is the bit and this is the chisel. The last remaining tool that survived the fire for the episode of the tools that built the pyramid. This is a measuring tool so you can make sure that everything is evenly spaced. Got this set, the Adeladon and arrows. This is another Adeladon, a little simpler but it works. A set of four, count them, four bronze chisels. Cast bronze, it's lovely and functional. The cast currency, first htme money, it's marked with our letters in here, buy it to spend it. All right, this is the torch I made. It is from Pine Rosen and I think this was hemp, I burped. This was actually for a collab with MrBeast but he canceled. All right, this is an antler ad made from antler and this was used for the boat. To be exact, this is Dobby's boat but she said we could sell it. This has been lead on fire, not the fire but this is the little thorax. It would be quite the fit for the Halloween costume. All right, one of our more sought after items is this mycenane sword. It is slightly bent at the tip, that was from when we were testing it. Pretty cool. So this is the loom, it is disassembled clearly but it comes with all the pieces so you can make your very own loom. About 1,000 heddles on here, 250 per shaft. So that's how many warp threads are through the fabric is roughly 1,000. And then to lift the heddle shafts I put in this lever plate frame. This string goes back on either side down and then ties into the heddle shafts and so when you lower the lever it raises the heddle shaft to make the shed. So you'd lift every other shaft and that would lift every other thread and then you'd drop those and then lift these to lift the other threads and that's pretty much cool. This is the obsidian sword, yes the obsidian sword, our most popular video. This is a true relic. If we start the bidding at, oh it is broken by the way, but it can be yours. You would have known about this auction and you would have been keeping your eyes peeled. You probably followed me on Instagram. I posted about it on my story, you might want to do that. You can see some nice behind the scenes footage. That's it. So we hope that you can get something from your favorite channel to bring home and we really, really appreciate the help, thanks. Thank you to Trade for sponsoring this video. If you enjoyed this video be sure to subscribe and check out other content we have covering a wide variety of topics. Also if you've enjoyed these series consider supporting us on Patreon. We are largely a fan funded channel and depend on the support of our viewers in order to keep our series going. Thanks for watching.


My name's Zeeks and I'm a 22 year veteran of DefCon. This is DefCon 30 and yeah we're the Arts and Entertainment Department. What does that mean? Arts and Entertainment, we take care of anything and everything, music. As you can see behind me, we have a lot of gear now. A lot of gear. We've made a giant mess of this gear. But this gear is for you. This gear is to make you guys happy. What do I mean by happy? Well I mean there's inspiration when you listen to music. There's a sense of mystery that you solve when you listen to music. There's peace when you listen to music. These are the things we want to bring to you. These are the things that we as A&E want to provide you guys.  We want to provide that fun. We bring music, lights, loud noises, ceilings falling. This is some good good stuff. We like to reach out to you guys, every one of you. Go to DefConMusic.org. DefConMusic.org. You'll get all of our information from when the sets are, what time they are, to pretty much anything. We're going to try to focus on giving our entire music archive on there. Everything you get from media.defcon.org, we're going to have on there as an actual playlist. Remember DefCon12? We had music. DefCon9. We had music. This stuff was awesome. You weren't even there. You were a kid at DefCon9. We got that music. It's awesome. So please, DefConMusic.org. Love it. Okay, take care.