Hello, everyone. How's it going? Today, I'm going to talk about a tactic that I use that might get a big technical, but I think it's very useful and I use it for sales, but also for work. In fact, I use it for pretty much everything I do. Now, I got this tactic from a book called Deep Work by Cal Newport, which by the way is a very good book. But let me introduce it briefly what this tactic is and kind of how it works. So what Newport writes, he talks in this book, Deep Work, he talks about having measures and he recommends measuring your productivity with leading measures, which are measures of your inputs that you can change day-to-day and are related to your desired goals. And you also, and this is opposed to lagging measures, which are more reliable, but are only visible in the past. So, and I'm reading this from the thing, but basically he has leading measures and lagging measures. Leading measures are your inputs are what you put in and that you can change day-to-day and they're related to your desired goals, but they're not your desired goals per se, but these are things you do. Number of words written, hours spent deep working, number of emails sent out, you know, that's what you have control over. Lagging measures are more reliable as to what you're looking for, but but they're only visible after they've already been accomplished and they're not something you do directly. So this this will be something like how much you earn, you know, earn this much, how many new clients you've acquired in a month or anything along those lines. And I found this very interesting and so let me show you briefly how I apply it to my work. There are a couple, so the first thing that I apply to is sales. Every freelancer out there is going to have to deal with sales. If you're looking for new clients, you're going to have to deal with sales and there are a couple ways to deal with it. Some people will say, okay, I need five clients by the end of the month. And to me, that is a lagging measure because you can only see that you have five clients after it and some not something you have direct control over. You don't get to say, okay, this this this this are my clients. Boom, done.  And they'll say, no, thanks. I'm good. No, thanks. I'm good. No, thanks. I'm good. Oh, yes, maybe. Okay. Let's talk about it. And so you don't have direct control over it. All you have, you know, all you have to go by is kind of trial and error. And so what I do is I try to measure the things I do have direct control over. Now I've been doing this for a while, but you can also see based on your experience what works best. So say you're sending out emails and say you want to send out, you know, sales emails that you want to, you'd say, are you interested in hiring me or something like that? And or I'd be interested in being put in your database or I'd be interested in working for you, whatever it might be. So that's something you can actually measure. How many of these emails you send out. So if you decide, okay, I want to send out 10, 20 of these emails a day, and I recommend somewhere around 20 something because with emails, emails are the easiest way to do sales just because you just send them out, but they're also the one with the kind of the worst response. So say you send 20 emails out every day, that's something you can control. And it's based on a calculation because if you're thinking, okay, maybe one out of every 100 emails turns into an actual sale. So I need to send out, and if I want to get four or five new clients by the end of the month, I need to send out 100 emails. So if I send out 20 emails a day, Monday, Tuesday, Wednesday, Friday, that's 100 emails per week, out of those one will become a client. Okay, I should get four clients by the end of the month, something like that. I'm just coming up with these numbers like this, but at least that kind of gives an idea of, at least that gives you something that you can shoot for directly and not saying, I want four clients by the end of the month. And so what you do is once you have this leading measure rather than the lagging measure, you only concentrate on that on sending out those emails. That's it. Another variation of this that I've heard is someone, this guy who worked in sales, and he said it's very common in sales. I don't know if it's true or not, but he worked in phone sales. And he said that actually a lot of salespeople, what they'll shoot for is not how many sales they make, because once again, you get more rejection than sales and you don't have much control over that. He said, but how many rejections? And it'll be something like, okay, once I get 10, 20 rejections, then I can stop for my lunch break. And so they shoot to get rejections, right? And so, hi, are you interested? No, I'm not interested. Okay. Rejection one. And then they go through the motions. And then every now and then they'll get someone's like, Oh yeah, actually, I'm interested. Tell me more about it. And that doesn't count towards their quota for lunchtime. So they're like, Oh, no, I need to add another call. But in the meantime, they made a sale. So actually it's pretty good. And they'll feel good about that. And that'll be able to push them and keep going forward. So anyway, I think looking at leading measures is always good. And that's in terms of sales in terms of other things. One is income. A lot of people will say I want to earn 80,000 a year or I don't know, four or 5,000 a month. Okay, you want to earn four or 5,000 a month. But if that's all you say about it, it's not going to happen. Trust me. What you need to do is, so what I do is kind of break it down. What does that mean in terms of things I have to do with things I actually have control over? And yeah, if that means sales, then it's something like that. If it means doing a lot more work and more work hours, then I try to break that down. And so I'll say something like, okay, I need three hours deep work as he calls it or in the zone work per day. And then I can achieve my goal. Okay, that I have control over. I can set aside three hours every day that I have control over, wherein I actually get my work done. And then the other thing will fall in place almost by itself. What I have to do is concentrate on the stuff I have direct control over. And I try to apply this to everything, by the way. So yeah, like going to the gym, you can go to the gym, you can say, okay, I want to lose this amount of pounds or I want to gain this much muscle. Okay, if you just say that, it's not going to happen. But if you kind of break it down, be like, okay, if I run this much per day, work out this many times per week, cut down what I eat by this much, something you should work. So that's what I do. I need to go to the gym three times a week. I need to run 10, 20 minutes every time I go to the gym. Okay, I have control over that. Even having control over that, you notice how often, at least for me, how often I actually skip the gym or stuff like that. But so imagine it's stuff you don't have control over, how easy it is not to achieve it. So find things you can have control over. And those are the things that will lead to the what he calls the lagging measures, the actual results. But focus on the things you have control over, not on the other thing. So if I want to lose weight, I want to lose 10 pounds by the end of the month. That's a great goal to have, but just having I want to lose 10 pounds by the end of the month won't make it happen. What will make it happen is things I have control over. Going to the gym three times a week, running 20 minutes every time I go to the gym, not eating, I don't know, cake or cookies or whatever, and sticking to healthy meals, whatever it might be. And then if I do, if I just concentrate on that, I'll lose the 10 pounds without even thinking about the 10 pounds, right? And anyway, so this is something that I've been trying to apply, as you can see, to many facets of my life and especially to work. When I deal with work, I try to deal with stuff I have control over. The number of emails I send out, the number of people I meet because I try to meet people face to face. So what I'll do is I'll say, okay, I want to attend three events per week that are relevant to what I do. And when I'm at that event, I want to, you know, because I don't want to go to the event and hang out there. So no, I want to receive, I want to meet people and either send, give or receive five business cards per event. So then I have their email address, and that's something concrete that I have more control over. And I like that. Just having business cards per se, just attending these events does nothing, but they lead to the results that I need later. And so anyway, that's something that I recommend. Again, it's a kind of a different way of looking at things that I liked a lot. It was once again, it was from the book, Deep Work by Cal Newport. I'll leave a link to it down in the description below, actually, just in case, because it is a very good book. And but yeah, one of the issues he deals with are these leading versus lagging measures and which one you should be keeping track of. Because very often it's not obvious and, you know, you want to keep track of one and the other at the same time, but it can get confusing. And so he kind of delves into it a bit more deeply. But I just wanted to show how I've been applying it to my work. And so I think you'll find it useful for your work as well, to concentrate on these leading measures, these things you have direct control over in order to achieve your goals later on. So yeah, hopefully you did find it useful. I hope you did. Don't forget to leave a thumbs up if you do find this useful, because that always helps out. Don't forget to subscribe if you haven't. And also remember, I provide services myself as well. I read over resumes, profile pages, websites. I have a link to a questionnaire you can fill out in the description below, which if you're interested in that, I also provide one-on-one consulting. I have a link to that as well. And otherwise, I'll see you in the next video. Thanks. Bye.


Tēnā koutou katoa, te porahi tuku iotanga o Pukeariki ko Andrew Moffat taku ingoa. Ia gadaftinu, nō i'm Andrew Moffat, Heritage Manager at Pukeariki, from Tropical Taranaki, or in the heart of Tropical Taranaki it is. And we're here today, myself and the currently absent Millie, to discuss a little digitisation project that we've got running involving a large collection of photographic negatives which we call the Swains and Woods Collection. So what we want this session to do is to be a really useful session for people in terms of sharing some of the trials of this project which we're starting to stack up quite a few of both, to be honest. So what we want to do is run through, share a few of these which will hopefully inform the projects that you're working on in different ways. And it was really interesting to see Cliff's talk just before in terms of the different ways that the cake can be sliced, I guess. So we're dealing with a different kind of collection here, but similar issues so we can get out of the way. So firstly, for those of you who don't live and breathe a project like we do at Pukeariki, a little bit about the collection. The Swains and Woods Collection is a large collection of studio photography. The photographic where negatives is an important part of the equation created by the New Plymouth photographic studios, Swains and Studios and Bernard Woods Studio. So Joseph Swains in there, you can pick him out. On the left he established Swains and Studios in 1923. Bernard Woods took over the studio together with his dog in the 1960s and then his daughter, Ginny Woods, assumed responsibility for the business in the 1980s. So what they did, they took photos. And the resulting collection of these years and years of practice, a very successful practice, was a large collection of studio photography. So we've got primarily studio photography. As someone said before, there's a lot of weddings, a lot of school groups, a lot of sports teams, that sort of thing. But also you can see we've got people of tractor in there, a bit of industrial heritage and some beer kissing. So a little bit about the project. I guess there's different ways to deal with this. So I was really interested this morning to hear about how the digitisation project can kill institutions and I think that that is a very real risk with something of the scale arrives on our doorstep. The collection arrived at very short notice in 2005. It was offered to us and the donation was brokered. And what it effectively did, it came in from some storage where it was stored and effectively a garden shed and arrived on our doorstep. It was a deal brokered by the Nicomath genealogists together with some of our staff. And this is the state of some of the negatives when they arrived. They're actually in surprisingly good condition and a lot there you can see they're sorted by, they've got some identification and are sorted but I guess skeletally identified would be a good way of saying. And I won't go into the details but there were things that we were discovering well let's just say we found maggots. So this effectively doubled the size of Pukiatiki's pictorial collection. You see I've highlighted massive challenge. That certainly was on a collection management front and so with the help of some outside advice and with a lot of head scratching on our behalf, we came up with a plan you can see at the end of three phases. Cleaning, rehousing and cataloging the two portions and then moving on to digitising the collection which I think we are all enjoying and that is the phase we are in now. So another thing to mention, this is a huge effort in terms of resource and the reason that this hasn't killed us or we haven't just got them sitting in the same state as a huge amount of external funding that we've been able to secure over the years. Taranaki Electricity Trust, the TSB Community Trust and lotteries were very important as well in the first phase of the project and also obviously we're part of the New Cymru District Council and the genealogists have been a huge help if I said and a lot of the support broken by the Pukiatiki Trust. So we're talking in total about $1.2 million of external funding over the life of the project from 2005 through to the digitisation and it's also been a tremendous team effort in other ways. I might get into trouble with this slide bringing up a few unfettering photos but I wanted to get across some of the scope and you'll see there's some white areas there with people who haven't made it in. I'm really aware of the support we've had from a number of institutions, National Library, chief among them and individuals as well. So it's been a huge team effort with the technicians cleaning, rehousing and cataloging the collection. It's easy when you say it like that but that's been years of hard work in the making to get us where we are now. So where we are now, here's a shot from our collection store and we couldn't fit in all the boxes but you'll see we've got a SW11 up there going right down to SW271 is the number of boxes I'm told which the collection has stored in. So quite an impressive array there and a lot of work to do. So of course these were, the collection was there but really until the digitised the collection of studio photography is not much use to anyone so that's where the digitisation comes in. We'd like to hand over to our digitisation coordinator, Millie Mitchell-Anion. This has been a big project for us so Millie's going to talk you through the next step. Which one do you push? Okay, awesome. Kia ora, I'm Millie Mitchell-Anion and I'm the coordinator for the Swenson Witch digitisation project. I'm going to talk about running this project, the equipment and processes we use, what it's taken to get it off the ground and just some of the few trials and triumphs we've encountered along the way. I'd also like to take the time to shout out to the National Library without their support. We'd be a little bit lost. But, rather than dropping in the deep end I'm going to briefly explain our process before moving into the technical stuff. We're simply capturing an image of a negative on top of a light box using a camera. So then we're inverting that image in Photoshop. But yeah, scanning the negatives wasn't investigated but we thought camera capture was a much faster and more efficient way to do it in the well run. Especially when 110,000 negatives enters the equation. But straight into the nitty-gritty, a light box is specifically designed for negative capture. The Canon camera we use has the capability of capturing raw files around 26 megabytes in size. We use a 50mm lens for larger negatives and 100mm lens for smaller negatives. The UV filters are on our lenses to prevent damage from the massive amounts of light filtering in. And then we sandwich the negative in between the light box and a sheave glass which is specifically designed to eliminate mutant rings, which as you can see from the cat picture here like where the arrows are they're undesirable in a digitisation project. We work with dual monitors. One higher quality Dell and the Philips is our secondary. In terms of software we are using camera raw to capture the raw image files. Adobe Bridge is a general file management tool and Adobe Photoshop for editing our raw files. We use Vernon, a collection management program for our text and image records and FileZilla for uploading our records to the web each day, might I add. Onto storage, IT had been involved from the outset of this project so we have a dedicated 6TB server hosted by the New Plymouth District Council solely for Pukiyariki images. I also asked about the server before I came here and we use a storage area network which is just a large can of disks all interconnected and configured for non-stop operations. This is at the council which is then backed up in another location within the city and this information is backed up again and taken off site by a third party installed somewhere securely in the depths of Taranaki. So we're feeling pretty confident about our digital storage situation. Onto training this week's awards team training began with Mark Beauty coming up from the National Library to train Ruth Harvey, Charlotte Stase and I. As you can see, Ruth, Charlotte and I are hard at work. During training Mark ran us through all the different scenarios we might encounter over the course of this project. Basic things like making sure file names were correct, files were the right size, working on banal things like file structures even though they're very important. We cemented the processes we use developed generic workspaces for Photoshop and Quick Actions. We spent a couple of days running through the project seeing what cropped up and even Andrew had to learn the basics. Yeah and then together we all trained the new Swains and Woods team members who are Claire Richardson otherwise known as Doctor QA me, Vice Vernon Amber Cookley, Professor Procesa and Jacob Metaitoga none other than Captain Catcher. So I explained a little bit about camera capture before but for a little refresh we start by sandwiching a negative between the lightbox and a layer of glass. We use camera raw to capture the image files in raw format and then those files are then saved on to our server. Alright, so technical bit. From there we cropped and stranded raw files and then processed them as 16 bit TIF files in Photoshop. We have action set up so it's only one click one button to convert the image into the right colour profile flip it and invert it. We'll then bring in the levels making sure not to use any detail by introducing true blacks or whites adjusting the mid tones and sometimes using curves to enhance them. After we've finished processing we'll save them as an 8 bit TIF. Once we've done a batch, they're ready for another team member to pair with you and check the quality of our work with all this QA. As we're checking the image we're checking that the edge is not compromised the image is sharp and we check for here and dirt that may have been added during our processing. We check whites, blacks, mid tones this is all quite a meticulous process as you can imagine. We check that all the whites and blacks are within an RGB range of 14 to 245 and another aspect of the QA is a general audit as we're going with our Vernon records which were already pre-done in stage one and stage two. And so there's also the ability there to add extra detail about the images once they're digitised we can start adding extra terms and tags so that they're searchable. Our final TIFs end up being about 17 megabytes in size smaller JV is then linked to for our online records and so it got from this in Vernon to this by the end of the day and then during our daily uploads the record is updated online. All of what I've seen so far is the easy bit since starting this journey to digitise 110,000 negatives we've had our moments and being tested on numerous occasions so in the beginning we had a bit of an issue with dust cotton gloves were leaving small fly away fibres on everything so we switched to nitrile gloves we made a Tyvek dust cover dubbed Casper the Dust Free Ghost for our camera copy, stand and light box Sorry because the collection came to us from a garden sheath not all the negatives were in great condition so there's always an issue trying to determine if a mark on the images is pre-existing and perfection or something we may have added so we're all experts at the game here versus scratch we also now clean the lenses once a week because at one stage we captured thousands of images with a small halo piece of dust on the lens which we then had to recapture you know learning curves another issue we've had to tackle is the shaky suspended floor we work on when someone walks past our workstation it just shakes a little bit so we've managed to work through this by capturing a faster shutter speed and it hasn't been an issue so far and Newton rings even though we use Newton ring glass pre-existing fingerprints on the negatives can look like Newton rings and give us a fright but it keeps us on our toes so we were asked during our job interview if we could deal with repetition so we took a flag here and said I did underestimate how many babies and brides they were going to be in a studio collection and I confirmed that people did get married and have babies in the 40s and 50s one day we checked our raw capture folder only to discover we've been shooting in low-res JPEGs for about 700 images or so they're about 200 kilobytes in size so useless so there's nothing we could do apart from recapture them raw backlog so on the topic of raws we're still struggling to find a balance between our raw capture station working faster than our processing and QA so we currently sit on between 5 and 10,000 raws of our sleets at any one time which can be a bit of insurance policy or it can lead to other problems like capturing a piece of dust on them for a while and consistency and taking a while to produce consistent style amongst the team and it's still something we're constantly working on and another hurdle is colour processing we've got issues of blue hues image quality reflections and the list goes on because colour digitisation hasn't been done on a large scale yet we have no model to base our processes on so we're figuring it out as we go and another major curve was the failure of the server because it was amazing but it felt like it at the time one morning we arrived during our first week and all the work we'd produced so far had disappeared into the ether somewhere it was however a simple problem and solution IT just changed the way they backed up our server but you know there was a few heart attacks that morning this however wasn't the end of our computer wars one day our 600 gigabyte Swanson Woods folder had disappeared in its entirety suspecting the worst that had been deleted we rang IT and they searched and they couldn't find it and so they were able to restore our data so everything was restored by the next morning so if you think about that like 600 gigabytes of data more heart attacks so yeah having an amazing server is worth it and it's already paid its dividends but you know it looks like the issues and trials we've had might outweigh the triumphs but those trials are small fry in comparison to the massively rewarding outcomes from digitising the collection I mean just look at the amazing images we get to digitise we're starting to connect to the collection in a place like a lot more than I thought we expected we see things that make us laugh and you know particular triumphs of ours include learning about people in the collection for instance this is Merve Luke a cyclist from Timaru who won the Round the Mountain Race in 1946 and one woman rang me up to tell me her son had won the exact same cup in 1997 what she then took to the pub filled with beer and then scolded um another triumph is just how quickly we're working despite the trials we're having we really had to keep that in mind as we're challenged by the various trials of the project we're also working out quicker ways to do things even on Vernon when we would have copied datis and now do XML imports and exports and there's now potential to apply these methods across the collection in lots of other ways and another major triumph is the day to day problem solving and finding solutions for it but I think above all the biggest mahi is when someone from the public is able to connect to the collection because of the digitisation work we're doing because that's what it's all really about so um yeah I'll hand you back to Andrew yeah so um Millie's led into that very nicely that you know we now are faced with the challenge and the ongoing challenge of what to do with this amazing resource that we are in the process of creating so you see the quote there from Jeffrey Batchan we couldn't agree more that we need to do things with this collection we can't sit on it it's important that we whether we take a scanning approach or not I guess so we are doing a number of things with the collection digitally and otherwise we're using the newspaper and the themes of Artifact of the Week and also a Can You Help Us column so these are two different ways of connecting the collection with the community we're getting great the Can You Help Us is just asking for identifications on a photograph each week and the data news and we get a huge response from that so normally the phone rings pretty hot on a Wednesday morning doesn't it Millie and we get sometimes a lot more information than we bargained bargained for which the team we treat each thing as a real gift and it actually lifts us sometimes I guess the first call might lift us more than the 50th but nevertheless that's all part of the process and we really value that engagement we record that information in Vernon and update the record of course you'll see there the Inglewood Dramatic Society in full flight there that refers to a series of digital exhibitions we run around the Taranaki region this came out of some sponsorship from the Taranaki Electricity Trust initially and it's a series of rotating digital exhibitions where we feature a lot of locally relevant content from the collection and again we're getting identifications through that and amazing community connections we're actually touring a part of the Swanson Woods exhibition around the region as well yeah so that's part of it we do like Swanson's themselves at the Winter Show we do hold exhibitions as well we've had a very successful one which those are, you saw those cutouts were from which Millie was modelling so well before yeah so we've had that been a great way with really giving the community ownership I had a question raised before to me like well is everyone really interested in those photos of weddings and babies and actually the answer that we've had so far is a really resounding yes people take huge ownership in this collection and it's got to grow Jacob here looming a little menacingly behind the light box is promoting our behind the scenes tours that we're running as well we've had a demand for that and yeah we've been well subscribed so showing people what's actually involved obviously we're getting things online as Millie said on effectively a daily basis perhaps not counting today seeing Millie and I are here while the team is still hard at work but yeah there'll be some big uploads coming later in the week and part one of the things that this has forced us to do Millie alluded to this collection is effectively stretching what we're doing in other areas so we've started using the Swanson Woods fresh feature which is a weekly summary of the freshly digitised items and we're getting people checking back weekly and sometimes daily I think on what the team are uploading so another thing that Swanson Woods collection has made us tackle is start to tackle commenting directly on our browser as I've mentioned people are wanting to engage with the collection, identify it and otherwise make comments so we've added the function there together with some great work from Vernon thanks Paul added the commenting function there which basically is very easy to do it's just a matter of an email address and name and your comment in there and it's been working amazingly well we've been getting a great range of comments the flow has been coming on everything from you know John coming in from the hay panic there for the photo and not too keen simple identifications through to some amazing detail that we've never thought elsewhere so we've just recently changed the flow to start with there was enough for one staff member to keep up with that and respond monitor and update the reports but we've had to switch to a team approach because we're getting a big response now so the team are needing to chip in to make it manageable of course our friends at Digital New Zealand I had to mention them are part of our digital strategy over the years so every record with an image attached is harvested now to Digital New Zealand on a weekly basis just another great window in to the collection and obviously we have some tremendous stories of engagement that are coming out it was difficult to pick what to talk about but really I couldn't go past talking about Palmer here briefly as an example she's obviously a beautiful woman from Australia and was lured to Taranaki this bloke here Rex Rex Hopkins who's a farmer from around the coast and they were married in New Plymouth at St Mary's Church in December 1955 so I mean obviously a pretty amazing story in some ways or quite typical but the thing that really brings in a life for us is this contact now this you may recognise him from the previous photo he's hardly changed but I told him and he's the kind of guy who laughed when I said that as Rex so Rex is now over 80 but an amazing character and he had contacted us previously when he saw or had been made aware of the photo of his wife and he wrote us a lovely letter basically quite a touching letter really about how he was so thrilled to see it in terms of it being shared and treasured and was obviously incredibly proud of his wife who has contracted Alzheimer's in 2002 and is now in hospital he can't care for her but he visits her daily except he spoke very touchingly when he visited he came in and basically had a very short notice dropped in to see the project and we gave him a quick tour and I don't know Milly was talking about problems with dust previously with the project and I think there was a lot of dust in the air that day because they were rubbing their eyes quietly as Rex was recounting the importance of this photograph to him and showing his appreciation for the project and I think you could count for a lot of things when you get stories like this sort of starting to emerge and Rex then lessen the next day popped in with a bottle of bubbly but this is all about not trying to gloss over the problems this session so while we have numerous examples like Rex's there's also worth acknowledging that we have problems as well I guess one that I wanted to raise is we can feel a bit lost in the ethical woods like Pinocchio here because this collection was never created as obviously a public record it was a collection of private studio photography we're running into quite a contemporary collection sure we start back in the 1920s but we're running right up into the 90s and we have had instances where people have not been as thrilled as others when they found themselves or something related online we've had instances of people whose marriages have ended often the way they would want and then they see their wedding photos online obviously we've had issues where people have raised people's past criminal records who are featured online as well so what we need to do we're basically developing a case law for want of a better term we're dealing with these on a one-on-one sort of a basis where we basically consider the case while we're considering the case which somebody puts forward we look at it carefully and then we explain our reasons obviously we're all about access for this collection but we're operating within constraints and wanting to respect the community so we really look carefully at it and we'll then explain our reasons for the decision and either put their image back online or perhaps leave just as a text record or take it down completely it's something that I can't give you answer on exactly how to deal with every case but I'm confident that over the time we're going to build up a pretty substantial we want to be consistent and open with people basically so that's how we confront that we do have digital limitations like everyone this bloke I actually used to pay rugby with I was delighted to find delighted to find him in the collection he had a very good sides here but basically yeah we've got a great I think I'm really happy with the progress we've made with our digital presence over the years and together with working with Vernon and Digital New Zealand it's been great but I'm conscious that there's still a lot of room for improvement our search function could be improved our image size our flexibility there are a lot of things which we're going to continue to work on possibilities for the collection looking to the future pretty limitless to be honest we could do things like letting the artists in and we're going to continue a huge focus for us will be that bridge building to the community but that's got to happen in various ways and can never stop really for us so I'm really interested seeing Chris's presentation before lunch in terms of the names and matching other data sets because we're going to have a huge data set here and we'll be really interested to see those sort of possibilities what we can do but really like this this beel rabbit here you could never predict that this sort of image would be in the collection and here it is just like a big fluffy rabbit on top of a polished pedestal we don't really know what the future holds for this collection and what really lies underneath that we haven't discovered so I'm really looking forward to carrying on with an open mind to be honest so that's ripped that from us we've got a huge amount of work ahead of us I should say I don't know if we actually mentioned but since the digitisation project was underway we've got an excess of 25,000 negatives digitised but as Millie alluded to we're just in this phase of getting colour off the ground which is going to be a whole another set of challenges and we've done a lot of the easier parts of the collection hats first so it would be great to keep that up but I can't imagine that pace will continue so I'm happy to take questions to either myself or Millie if we've got some time I'm not sure how we're placed so around copyright then you've got to keep the copyright on all the images so you have the rights to republish all the stuff that's out of copyright I guess obviously a vex tissue for everyone I don't know if there's really a blanket answer in terms of when we get requests in terms of taking an image down for example if somebody is in that image then that would be a key thing for us here and you're asserting copyright over the digital the scans that you're doing you can promise those under my term incredible at the moment it's similar I think in a way to where Nelson's at we do like we're processing well you know we'll provide images people can, anything that's online there just so long as they provide a link to it we'll let them use it in terms of we'll be processing images through the image service as well for the high res things we've looked at creative commons but we haven't looked at instituting it yet Genie would sign the creation over to actually sign the copyright as well so I guess what we want to do is navigate the somewhat murky water in the best way we can but that was an important pre-condition before we would take the collection back from 5000 more things could cause problems how do you get around that do you have a sampling thing to check the quality we do now we didn't think we needed it but then we found out via that incident that we did so now we go forward and check


Hello everyone, I'm Alex and today's topic will be how to secure both your build and your cloud by utilizing OIDC tokens in your pipeline. So let's start with the agenda. Before diving into any solution, let's start with understanding the problem. Let's start with discovering how modern Sdlc pipelines are working, how they're built and why there could be a possible issue with cloud authentication. After understanding the problem and that OIDC could be the solution to several of these issues, we'll understand what is OIDC, OpenID Connect, what is its concept and how it can be used in CICD environments. Then we will build some very simple real world scenario which will go through the slides and finally we'll show you several demos and how you can build a more secure authentication to your cloud environments using OIDC. Okay, who are we? I'm Alex Ilgayev. I'm Head of Security Research in CICODE. Previously, I led the Malware Research Team at Checkpoint. We're doing a lot of reverse engineering for complex pieces of malware, discovering campaigns for cybercrime and APTs. And nowadays in CICODE, we're researching vulnerabilities in software supply and security and hopefully also mitigations for these vulnerabilities. Elad? I'm Elad. I'm Security Research at CICODE used to do API security and IOTs before I came to CICODE. Okay, so in short, CICODE is a cybersecurity company based in Tel Aviv that are doing complete software supply and security for organizations in all various kinds of security, both in searching hard-coded secrets in your code, securing your pipeline, misconfiguration, cloud security, and many more. So let's start with the problem. So after investigating and understanding how most of the modern SDLC pipelines work, we can divide it to several parts. The first is a developer, whether it's a contributor, a maintainer, collaborator, it doesn't matter. It's the actual person that pushes the code. The second part is the SEM system, source control management, mostly Git-based. It could be a GitHub, GitLab, Bitbucket, Azure DevOps, it doesn't matter. And most of the code is pushed through one of two ways, either direct push, which is usually not recommended, or through a pull request or manager request, depends on the system, where you suggest a piece of code that should be reviewed by multiple developers before it's been pushed to your code repository. And whenever you push a new piece of code, usually, which is the most important part in the recent years, usually there's some trigger event that creates some autonomous procedure in some CI pipeline, in some CI system. So there was a plenty of CI system nowadays, GitHub actions, GitHub CI, Circus CI, Jenkins, and the list goes on. And usually these pipelines are doing predefined procedures, taking your code, checking it out, compiling it, packaging it, pushing it to some artifact registry, some container registry, it doesn't matter. And also doing the deployment phase, creating resources in your cloud, and actually creating your production environment. So to create all these complex pipelines, you need a list of first-party integrations in your CI CD pipeline. For example, it could be artifact registries, PyPI, Maven, Gradle, NPM, Docker, it doesn't matter. What could be also cloud providers, Azure, GCP, AWS. And to create these procedures, you also need to authenticate securely with these providers. So the popular way to do that nowadays is mainly through tokens, tokens, which are similar to username and password, but tokens is like the popular method.  So you could access this securely from within your CI. And how popular is this method from simple search in GitHub for accessing to these secrets? There's like hundreds of thousands of occurrences of these access to secrets. It is suggested in like almost every best practice paper. It's better than hard coding the secrets, of course. And we can safely say that this is like the most popular method nowadays from in your CI pipeline. So access some different services. So you could think yourself, what is the issue if the best practices suggest this method and they are encrypted and they're not hard coded. So what could be the possible issue with that? Well, it's better than hard coding them, but it's still it's not enough. And the first reason is Circus CI Bridge. In January 4th, Circus CI, a really popular CI system, announced that it was going through a security breach. They discovered after one of its GitHub token that was saved in Circus CI system that belonged to one of its customers was misused, maliciously used. And then they understood they were going through some security breach, which means that all the tokens that saved in the system are actually compromised. And so immediately when they discovered that, they announced and told all their customers to reroll all their tokens, which means that they could be compromised. Furthermore, when they finished investigating this breach, they went with several best practices. And one of these best practices, they said that to use IDC tokens wherever possible to avoid storing long-lived credentials in Circus CI. This is the first case. The second case, which is more popular, which is the CodeCov Bridge, happened two years ago. The CodeCov is a really popular code coverage tool that usually runs inside your CI system. And two years ago, the installer of CodeCov was compromised.  So why it's relevant to the secret? Because usually when you're using secrets inside the CI, they're stored as environment variable. So it's another reason why we need to improve the security of authenticating inside the CI. So what is the solution or maybe the solution? OpenID Connect, OIDC. So let's understand what is OIDC. So it's built upon on the off 2.0 framework, which is a widely popular framework in the web authentication. And it actually extends its capability. It mainly extends it by allowing a third-party application to verify the identity of the user in the authentication scheme. And behind the scenes, it's using JWT or JAWS, which is a JSON web token. So both OIDC and OF using the concepts of tokens and scopes. So token, which is this JWT, is similar to a train ticket that you could show it to do something. It allows you to do something, right? And scopes, it defines what the user can do. For example, you can use this train ticket to board a specific train. So how JWT looks like. So one of the benefits of OIDC is that it's standardized some of the claims and some of the fields in this token. So the most popular one is a subject, which is the identity of the user or maybe the machine. It could be used to grant you some permissions. And an issuer, which is the authority that issued this token. It also contains the token issue, time, expiration, and many more fields. So another very important fact that all these JWT have signatures that were signed by the issuer. So they are signed rather than being encrypted. So let's see how OIDC can be used in web authentication. Let's say I want to consume some resource on some web application and I can click on this login with Google button on the application. So it will forward me to the identity provider of Google, which will raise me some authentication consent. This small window that asks me whether I'm authorizing this application to use my identity. And when I accept this, so Google issued a new token, a new JWT token that's signed by them, containing my identity. That is passed to the web application and the web application can use that to understand who I am and grant me the proper permissions. So you can think why this mad web application because we're talking about CI CD. So let's see how OIDC can be used in CI CD. So it's not a coincidence that in the last month or so, most of the popular CI CD systems started to support OIDC natively. Furthermore, GitLab even in the past weeks even extended its support to the OIDC by allowing you to define a custom audience in your pipeline. So how it works. Let's say I'm some CI system and I'm creating a new job, a new job that doing something that related to my development pipeline. So in that job I'm able to request the identity provider of the system, let's say GitLab or GitLab, to request a new token that contains the identity of the job of the pipeline. So I'm requesting it with the identity provider. It signs that token and give it back to me. I'm the job. And then the job you could use this token to pass it to some, for example, cloud provider to STS, STS security token service of all the cloud providers have this service. And they could use this identity to issue me a short-lived credentials for the cloud provider. It could be AWS token, GCP credential, Azure, it doesn't matter. And then I could use this short-lived credentials to access the resource I want in the cloud. So this is at a high-level schema. We soon will see how to implement this in details. So to do that, we created a really simple example really to explain the concept. This example we will have a GitHub and GitLab. We show how to implement it in both. And we want to authenticate with GCP. And then we want to access a really simple resource in GCP that will be GCS. It's just a cloud storage of GCP similar to S3. And we showed how to implement that both in credentials-based authentication and in identity-based authentication. So I will pass it to Elab. Okay. So in the simple flow, we'll upload a configuration file from GitHub and from GitLab to GCP bucket. So let's start. Firstly, we'll create a service account. The service account will have a permission to upload objects to the bucket. And we'll export the key of the service account. So we have now a long-lived credential that we will have to put in our CI system in order to authenticate. So let's start with GitHub. A common workflow will look like, will authenticate to GCP using the JSON-creditation file and will upload the configuration file to GCP. Next one, let's see the GitLab workflow. This time we'll use the Gcloud client. But this time, the best practice for GitLab is using the Ashikov vault. So if we don't have Ashikov vault, we'll have to save the GCP as a protected or masked variable. When we will navigate to this tab and add the GCP secret, we'll get a warning that says the regular expression does not match to the JSON. There are some workarounds to that. We can base 64 and code this JSON, but it's not the preferred method. And pretty much every website we go, it says that we should authenticate using different methods. And that's different methods. Currently, it's the YDC, meaning we'll not have to rely on long-link credentials, but we'll use short-lived credentials instead. So how do we do that? Firstly, we'll create the identity pool. The identity pool will have two providers, the GitHub provider that will contain the default issue for GitLab. Next, we'll create the GitLab provider that will also contain the GitLab issue. So what do we have until here? We have the identity providers of GitHub actions and GitLab. And also we defined providers for GCP and dedicated for GitHub and GitLab. And we still have the same service account we defined before, but this time we'll not export the service account secret key, that long-lived key. We'll use the OIDC method. Let's start with GitHub. The first thing we see is the permission. The permission is changed and we're telling to the GitHub pipeline to ask for OIDC, the ID token, to be used. Next, we'll use the identity provider full path and the service account email to complete this authentication. And then, as before, we'll upload the configuration file to cloud. As we can see, the main thing that changed here, we are not using the secret we used before. So, where are the secrets? They're gone. Let's see a little demo. We have the same workflow we defined earlier. We will rerun the workflow. Let's go to GCP cloud and we can see our identity pool and both of the providers in this time we'll see in GitHub with this default issuer. We'll go back to GitHub and we can see we have uploaded the configuration file. The workflow has succeeded. And when navigating to our bucket, we can refresh and see that our configuration file is done. And all that without credentials, without the long-lived credentials. Next, GitLab with the same flow. But this time, in GitLab, we'll use the ID tokens keyword. The OIDC token will be saved under the OIDC underscore token and will be used in the same way, but this time, we'll use the GCloud client. So, is that it? We defined our identity pool. We defined our providers. But it's not it. It seems that the default way, without configuring any mechanism to filter a request, any signed OIDC token will be accepted. Meaning that if GitLab, CI or GitHub action will sign the OIDC token, it will be accepted and will grant the service account permissions. So, we can see the identity providers and service accounts are all over. So, we need to use that mechanism. And that mechanism will be using attribute conditions. So, let's dive into the OIDC structure. Both GitHub and both GitLab define some custom claims, in addition to the standard claims. And each one of them defines its own particular environment attributes, like their repository path, the ref name, like the branch name, and the emails and many more. So, we'll have to choose which one of the standard claims or the custom claims do we want to trust. That will be the mechanism that will filter a request to our cloud account. In GCP, we'll use CER, context expression language, that will allow us to deny or accept connections and to choose what environments do we trust. Do we trust a certain repository? Do we trust a certain email? Do we trust any of that? And we'll have to choose. So, an example to strict conditions are conditions that use IDs, for example. The repository ID, the subject, are very strict conditions that cannot be malformed. An example to wide conditions and easily bypassed are conditions that includes the start with, contains, that can easily be tampered by a attacker to create an repository that contains a certain word and bypass the attribute condition. So, let's move on. In this case, we have the same workflow, but this time we'll add a simple thing. We'll add an actor ID, an attribute expression that filters and certain users. And this time, the actor ID will be 100. My ID is different from 100. So, let's rewind the workflow. So, again, in this time, it requests an IDC token from the identity provider and giving it to the cloud provider. But this time it failed. It failed because it says that the attribute conditions denied this connection. And it will deny all the connections that will not contain in the IDC the ID we defined before. So, let's look on a high level what happened in this video. We ask the CI system to give us an IDC token. We send the pipeline send the IDC. And the STS checked the attribute conditions and all the other stuff and saw that the attribute condition returned an false expression, meaning the attribute condition failed. And it returned a return then deny message to the API that says the attribute condition did not match to the IDC signed token. Thank you a lot. So, it seems like this is like a perfect technology. And there isn't a single reason why not every CI will use it nowadays, but it's far from the truth. We showed you examples for GitHub, GitLab and cloud accounts, but many services nowadays are not supporting IDC-based authentication. One of them, a really popular one, is Docker Hub. There is even an open issue for Docker Hub to support this. And until that, every login, every authentication to Docker Hub in the CI would look like this. It should require you to create tokens and access them in the CI. And this could lead to handling many tokens in the system. Imagine you have different tokens for each type of CI with the different privileges. And this could create a real mess. There is a pretty good solution to handle that as well. It's called the External Secret Manager. There's a very popular Secret Manager. One of the popular is Hashacop Vault. We will show you how to implement this also through the GCP Secret Manager. And so in this schema, it's similar to the previous setup, but we will create this Docker Hub token. We will save it in a GCP Secret Manager. And then we will have a service account that will define it to access, to allow it to access this Secret Manager. And the service account will be exposed through the identity pool and the providers that allowed how to define previously. And how to do that? In the GCP, we just access the Secret Manager and we're adding the tokens there. And we're just defining this service account so it will have the permission to access these secrets. So the code is pretty simple. This is the case with GitHub Action. We could use a really simple action that developed by GCP that's called the Get Secret Manager Secret. And in the syntax, you just specify the path for the token in the Secret Manager in GCP. And the name of the variable that this token should hold. And then for the subsequent steps that you want to access Docker Hub, we just mentioned this variable that you found previously. It's pretty simple. In GitLab, we recommend to use Vault because it has a native support for Vault. So you could, you just define the token, the IDC token. In this example, it's called IDC token. And then in the secrets part, you just define the path the secrets is in Vault and the environment variable that you want it to be called, for example, Docker Hub user or Docker Hub passwords. And then in your script, you just, you can use this environment variable that was fetched from the Vault and you could log into any service you want. In this example, it's Docker Hub, but it could be NPM, PyPI, or any other service. So the great benefit of using Secret Manager in this case is that instead of managing tens or even hundreds of different tokens, you can even create a single token. For example, in Docker Hub, 17 Secret Manager, and you could reroll it periodically to secure it from breaches. So this is only the tip of the iceberg in the IDC token's usages. There are many more. Some of this I'm mentioning here. For example, every really popular usage is authenticated to Kubernetes cluster through IDC. Let's say I want to access the Kubernetes API server. I need to do some authentication and login to the API server. There are many methods to do that. The most popular I think is through certificates. But I could also define it to use my identity to log into the API server and receive the proper privilege for my identity. There's plenty of tutorials how to do that. It's out of scope of this talk. And additional use for our IDC tokens is to access cloud resources from within the cluster. Let's say I have some part that needs to upload some configuration file to S3 or to Google Bucket. So I could create a similar procedure, but instead of trusting the GitHub or GitLab issuer, I would need to trust the Kubernetes service account issuer. And I will use the identity of the service account to access to the cloud. A little bit more complex scenario that we could implement that is through Spiff-Espire. I'm sure you heard about Spiff-Espire in this conference. There were several talks about it. And the third use case also very popular nowadays is to use a six-store or a cosine. Six-store is a great framework to ease the container signatures. And you can sign containers using your identity, either personal identity through some Google authentication or the CI identity through the similar steps that we previously showed. You can also sign commits through a Git sign, which is also a great tool from the six-store ecosystem. Okay, so let's recap this talk. So we started first with explaining about the problem, how modern pipelines look like, what is the importance of CI-CD systems, and how many, how they are using these third-party vendors for the workflow. And the popular method nowadays for CI-CD system to authenticate is through tokens, because it's easy and it works. And we showed us it could be a problem because of the and the latest breaches show that. Then we explained about IDC, OpenID Connect, why it's so important, and how CI-CD systems nowadays use that. Then we showed you the steps how to configure GCP and GitHub and GitLab to create this complete flow of IDC authentication. And then we also showed you what to do with providers that don't support native IDC authentication. And that will be through Secret Manager, like GCP has one, Hasekov Bolt, AWS has one, and many more. So thank you very much. You're welcome to check the full technical details of this talk in our blog. You're welcome to scan the QR, it will take you to the blog. Or you can check any other technical information in our blog. There's plenty. Thank you very much for listening. And that's it.


Aaron, just what did you think of Cole? He obviously looked very good. He looked as good from your advantage one as he did from up here. Yes, I thought he was even a little bit crisper this time out. I thought his fastball was playing a little bit better. I thought he did a good job with it in the strike zone. And then running it up in the strike zone when he wanted to. I thought that was really effective while still maintaining the command with the secondary stuff. That was, again, excellent. So another really good step for him to get up over 80 pitches and get through six innings. Yeah, I thought he was really impressive. Meredith, go ahead. What's the plan for Cole? Will he pitch in the exhibition, or will he not? Probably not. Well, right now, we're keeping him on that fifth day. So he would actually go Friday right before the exhibitions. But that's something that will also keep a little bit fluid and monitor and, again, see how he bounces back tomorrow. See when we want to take the sixth day. But we'll probably use it heading into the opener. So as of right now, no. But I guess it's possible that could change. You had mentioned prior to the intra squad game that Aaron Judge was getting treatment.  Yeah, we're not inter-squadding or anything. Right, we have a lighter day tomorrow. So we'll see. I'm hopeful that he'll be ready to go for Tuesday's inter-squad game. But we'll just see. Again, I don't think it's going to be something that keeps him down too long. But most of us have had that kind of neck where you get it wrong and makes hitting tough. So we'll be smart with it. We won't push it and see where he is coming in tomorrow and then go from there. Sweeney Murdy, go ahead. Hey, Aaron, at any point will you start using these games to practice any of the extra inning stuff? We'll pick some spots where we'll do some situational stuff. So I guess the answer is sort of yes. We're trying to pick situations where we can try some things that don't necessarily have to happen in the 10th inning or whatever. We'll pick some spots where we do some things where maybe we'll have a guy bunt in a situation that maybe sometimes we wouldn't. Particularly with your late inning relievers, like would you use Britton or somebody to just have him start his inning with a runner at second, kind of work that way? Yeah, that's possible. And one of the things we've been emphasizing with them is a lot of our PFP work, our PFP work the other day was with relievers for those kind of situations where we've added a little more plays than we would otherwise do during the regular season because of that rule. So we're trying to prepare the guys for those kind of situations. Thank you. Next question from Christie Acker. Christie? Hi, Erin. Just a quick question. Is Cole at a point where you want to keep building him up? Or is this something you want to maintain with him and let him go into his regular season where he's at? No, we'll build from here. Chances are we'll add to this pitch count the next time out. That would be the plan as of right now. But you also got to see the outing unfold to a degree too. So I think there's a chance he could still be built up. Is there anything to the fact that you will be playing the Phillies in the Mets a lot during the regular season to not having them see your pitchers in exhibition games? Not really. In fact, that's certainly a question that always comes up. And when we were in the process of scheduling these games, I put a premium on the game action. And whatever competitive advantage you might lose by a guy seeing somebody, I think in this situation, that's so be it. I think there's value in playing some other teams for a few games that you've got to take what you can get. And finally, just another topic. What's the benefit of having umpires here for these games? Well, I think for them, it's a benefit. Certainly, just for them to get the reps. And I think those guys were really excited to get out there today and start working. And it's their spring training, too. They're getting ready for the regular season, too. But also, for us to have a few major league umpires out there, it just keeps it more of a legit called game, even though Radley and Julio, I thought, did a nice job. It's nice to have the real pros out there. Thank you. Next question from Max Goodman. Max. Hey, Aaron. Just a fairly quick one for you. Do you consider Estevan Florial in the same category as those competing for a spot in the outfield for an opening day roster spot? And then just as he's the top rated position player prospect that's among this group, what have you seen from him so far? A nice throw today.  He's been lighted up in BP. Yeah, you know, we love Flo. We think he's got a chance to be a special player.  So, you know, that's hurt his development a little bit. But we still love the person and the tools and the potential. And there's no question that his ceiling still remains incredibly high. And I think there's a lot of value to him being out here. As far as opening day, look, if one thing, 2020 and this virus has shown us that you got to be adjustable in your plans. And so he's here with the thought that if something happens, he very much becomes in that mix.


So Madden23 just came out today, and it's already got some wild glitches. Another one, Dalton Schultz. The Dalton Schultz I know has a high motor, a lot of grit. This Dalton Schultz, hey, he's swaggy, he's got a lot of athleticism. I'm not sure what happened here.


I did it! Again, safe! For real safe! Fire! Are you coming?  Alright. I'm on this list. I'm gonna, but, hey, are you a part of me? That's what I'm supposed to be. I'm wearing a shirt. Look at that. Hey, I'm gonna tell y'all some fun facts at this point, man. So, the assicili- assicili- squarely face the threat. This is that kind of wind, uh, get a gauge or where to put your weapon in when you come out. That's it. That's it. That's it. That's it, man. Shot! I'm gonna need a- Nope. Lay out.  Put all your empty bags in the car. Dude. You wanna hit it? That makes a-


Samuel the prophet was instructed by God to anoint a replacement for King Saul, whose reign was coming to a chaotic end. The prophet was instructed to go to a man named Jesse, one of Jesse's sons, was to be king. While examining the sons of Jesse, the prophet heard God say, The Lord seeeth not as man seeeth, for man looketh on the outward appearance, but the Lord looketh on the heart. Jesse presented the sons he thought most suitable, but God rejected each one of them. The prophet asked, Are these all the sons you have? There is still the youngest Jesse replied, but he's out in the fields watching the sheep and goats. That son in the field was David, the shepherd who would become king. When you feel overlooked, remember, God is the one who anoints. The mantle doesn't come from man. The mantle does not fall on titles or entitlements or ability or skill. The anointing isn't passed by way of family ties, social standing, or the means of man. When others reject and misunderstand you, God has the final say. You're not forgotten, you're set apart.


Today we'll dive into six easy systems that will help you with better decision making. These systems won't only help you make better decisions but they will help you make them at the right time and be more confident about them even if the impact of these decisions is huge. Now I get that making decisions can be really hard especially at Birk. We are social animals and we want to be liked and we want to be part of a group so we often search for consensus and from input from others. The systems we're going to talk about are going to make you more confident when making decisions and thus make them more easy to make. First system we're going to talk about is the QB system. It was developed at Voice which is a completely self-managed organization employing 150 people. Because they are fully self-managed they need to be able to make decisions themselves and thus needed an easy framework to do so. This framework has four elements. How certain am I about making the decision? How urgent is this decision? Can I go back on the decision and how big is the impact of the decision I'm about to make? Let's start with urgency and certainty. If you're certain about making a decision urgent or not so urgent just make the call. A good example of this is I'm often asked to join a board but I'm very bad at that. I'm bad at reading financial statements, I'm bad at meetings so I'm not the right guy for the job so I can say with certainty that it's going to be a no. If a decision is low on certainty and urgency just park it. There's no reason to worry about it now. If a decision is low on certainty and urgency just let it go. Let your future self worry about it. I'm often asked how I'm going to spend my summer holiday and I don't know yet. We've got a great camper van, we need nice weather so we're going to decide on the location at the last minute. My future self can worry about it. If certainty is low and urgency is high we need to move on to the other two parts of the framework. If the impact is small and I can go back on a decision I just make the call. If it's not the right decision time will tell. We need to take the leap and see how reality reacts on our decision. If the impact is small and you can't go back a lot of people ask for permission but it's way better to ask for objections. A good example of this is the voice spending policy. Anybody in the organization can spend up to 5000 euros by just announcing it in a channel. By announcing it you create both clarity and the opportunity for people to object to the spending. Now let's look at decisions that have a big impact but where you can go back on. The best way to tackle these is to run small experiments. A good example of this is your company pricing strategy. You can't change the pricing strategy for your entire customer group overnight but you can run small experiments with new customer groups and new pricing strategies. The final decisions are huge decisions where you can't go back on. The only way you can tackle this is to raise certainty. A good example of this is switching jobs. It's very difficult to get a feel for a new organization by reading up on them online or doing a job interview. So if you want to switch job it's a huge decision it's very difficult to go back to your old job. What you can do is ask for a day where you can work in the new organization to get a feel for the organization so you get more certainty about the switch you're about to make. Now let's look at five other systems which are a lot easier and can support the system we just talked about. The second decision system is very simple. It's either a hell yeah or it's a no. It's a very simple one but it helps you out in a lot of situations. For example look at your inbox. A lot of them are questions from other people and you can see for yourself if it's either yeah I love to do this or it's a meh and if it's a meh it's a no. Now there's one important ground rule here. If you wouldn't do it tomorrow you won't do it in two months either so if you're asked to speak at a certain event and you think I don't really like it but in two months don't say yeah. If you don't like to do it tomorrow you won't like to do it in two months either. Thanks Derek Sivers for this nice mental model. The third system is an iteration on the system. It's a default yes and a default no. The default yes applies to my inner circle. If my kids ask me to help them out with their homework my default answer is going to be yes. My brother asking me to babysit their kid my default answer is yes. My friends asking me to go on a weird adventure we're gonna do it and if my colleagues ask me for their help the default answer is going to be yes. The default no applies to anybody outside my inner circle. Saying no to them by default protects my time and creates space and time for the important people in my life. System number four is the whole body yes and this is a really important one. First off I can reason with my mind is this a good decision on an intellectual level.  What does my gut tell me? When you have a whole body yes the mind the heart and the gut say yes. Now let's look at the difficult decisions you know you need to make but are just really hard. For decisions like these the system is very simple don't chew on poo don't postpone it don't delay it decisions like these don't get better over time and the consequences often do. I know it's hard I really do but get over it don't chew swallow. Finally system number six and this one is for the most difficult decisions in life. Starting something is really easy but knowing when you need to stop is a very difficult thing to do. Luckily Stephen Barlett created a very simple flowchart for these situations. If you're thinking about quitting it's very good to ask the question why? If it's hard look at the potential reward is it worth it then continue if it's not just quit. If something sucks the question is can you make it not suck? If the answer is no quit and if the answer is yes I can just try to make it not suck.  If you want to learn more about these six systems please follow the link in the video description. We've written extensively about them including all graphics for all these models. I hope these six models really help you out. Thanks for watching and thanks for voice for supporting these videos and I would love to see you in the next one. Cheers!


Earlier today, a crowd gathered in Prestonsburg for the ribbon cutting of Pikeville Medical Center's new primary and urgent care clinic. Lunch was provided and tours were given to show the community what the new center will offer. We're going to have physicians that are going to be on staff here. We'll have extended hours coming later and we're all excited to get that up and going. Basically, you're going to be able to treat anything in an after-hours urgent care that you would normally go anywhere else. Your coughs, your flus, rashes, those kind of things, you know, certainly not trying to open up an emergency room, but trying to open up an urgent care just to serve those needs of the population. Right now we're starting out 8 to 4.30. We are going to be extending that to an 8 to 8 and are going to be open on Saturday. Not on Sunday, but we are going to be extending hours to Saturday in the future. PMC officials say the new primary and urgent care clinic was a win-win for both PMC and the city of Prestonsburg. I think they wanted us here as much as we wanted to be here, so, you know, we've worked really well with Les Stapleton and I was able to pull this off just exactly the way we wanted to. I don't think you could have enough health care services. And you know, the biomedical center has come in here and got local doctors in. And I think it's going to increase a lot of traffic in this in the town, which is what we need for people to see what we do have here. Sure, there's already people looking at different businesses that are opening up in the area now. They're already contacting us about, for me, it's last and zoning and all that. So that's a great thing.


Annihilape is the brand new evolution of primate and is a fighting ghost type. Here's how to get it. Step one, catch a manky. Here's the spot where I got it. Step two, level it up to 28 and it'll evolve into a primate. Step three, level it up to 35 and it'll learn the move Rage Fist. Step four, use Rage Fist 20 times in battle on various Pokemon and then level it up by 1 and it'll evolve into the awesome Annihilape to help complete your Pokédex. Subscribe and tell someone that-


How do I do it?   I'm prime Vaughn Miller right now, bro.  I actually own you give us a shot I got a shot football fusion a.k.a. Roblox football. Tell me why Six-year-olds on Roblox built a better football game than electronic arts. I also love their description here This game is copyright free and any minor resemblance to any leagues is accidental and fair use Yes, I'm sure what I load in as the Miami Dolphins. That was accidental It's got good ratings 260 K thumbs up 40 K thumbs down and I have played football fusion before still trying to get the Hang of it, but it's actually fun Johnny sins you already know Why am I wise to say water boy? Yo, oh wait, we're on. Oh, oh, we're losing.   Oh, I guess that I guess that is a Kansas City chief.  That was actually kind of elite I'm not even mad at my team anymore. I got a block. I got a block for the boy. I'm sorry son. Oh good kick kicker Let's see the heat. Hmm. All right, let's go.  Yeah.  Oh, she's still got it Oh, there we go. I could be the past fresh guy. I'll stay on to here QB. He's definitely looking at it He's got nothing. That's me. That's me. It's not me Oh Who's on him bro 47 Dude, just feed me the rock though. All you got to do man. Just a little drag over the middle. Come on Just pick up clean yards, buddy Come on buddy Pro gamer you're not a pro gamer. You just threw it to double coverage.     Oh I'm I'm prime von Miller right now, bro. I'm Ed to tall Jones. I'm Johnny sins.  Is this actually a strategy? Come on dive. I'm trying to hit X dive, bro. Now you want to dive Johnny? Now you want to dive Johnny? Oh, I was right there dude.  That was all me. Good block.   Come back.  What a part return.   I know I missed the first pass, but I was just warming up I'm gonna go run the nastiest route they've ever seen Right down the seam We take that we take that we take that I'm not even mad. I'm not even mad. Can you type in this game emotes? Emotes are disabled Also a huge thank you to Raycon for continuing to sponsor my videos This is one of my Raycon earbuds right here and there's a reason they've been my go-to for the last two years Now Raycon's wireless earbuds headphones and speakers offer premium sound awesome features an amazing Comfortable fit and up to 54 hours of battery life and it's the holiday season right now It is the perfect time to be grabbing a pair of Raycons as a gift for somebody in your life And they're the best gift ever to because Raycon start at half the price of other premium audio brands My personal favorite part is the fit they sound incredible But they do not pop out of my ear and every other premium audio brand I've used Especially when I go to the gym running errands they fall out of your ear and with the holiday season They have something awesome for the next month Raycon will have a countdown to Christmas with the new pop-up flash deal For you to take advantage of every single day So you can find Raycon's in stores now like Kohl's and Walmart But for the absolute best deal you can go to buy raycon.com forward slash MMG as always there's a link in the top of the description you can also get 15% off site wide with the code holiday again That's buy raycon.com forward slash MMG to get 15% off site wide with the code Holiday check it out and enjoy the rest of the video Dude Jets are about to choke this lead. They have 14-point lead when I got in here.  Look at this blitz.  Let's get a safety He's gonna drop back to the right. Yep.   It's all tight Bro, I do not just make the defense.  Oh, they got a couple down there. Nice tackle. That was big.  Oh, I Should have blitz Yeah, right here, buddy right here Joseph Joseph Come back. I'll take it. I'll take it.  That was halftime. Hey, well gentlemen. Let's talk it over. Let's get this shmoney All-time QB rusher. No way.  How are they that open? Okay? He heaves one deep Why is only one guy there?   Oh my god This guy's this guy's actual in-game name is fortnight best. The other one is bussin bussin.  You got the first take it buddy.  Well, you want more than five yards of separation. Where are you throwing that? Where's that going illegal touch? Are there really flags in this dude? Fortnight best bussin bussin has the ball, you know, we're fucked. Oh My god, I've realized that I'm yelling at six-year-olds, but I don't care dude.  I'm just gonna say hi to bro because I'm butt naked wide open They literally have a defender not playing hit me either of us I'm molding it.  Oh Oh, oh, how is this that dive? Why couldn't I dive? I'm spamming X I am tea. Let's go defense.  Like how am I not diving? That's great defense.   Do we got you with the blocks? Just cut back. Yep. Yep Yep, how are you in the back corner of the end zone? He went for it. I respect it though. I respect the QB I'm gonna give him a post corner post corner. Oh, I'm just wide hopes. I'm hopes. I'm hopes QB Can you get it here? Oh, where is that? Where is that? Where is that? Oh?    I'm a hawk.  That was a lead. I know where he's going.  Let's just check it down Joseph. Yep I Don't know if that was to me or to the guy behind me Joseph, but that's a big overthrow. He see Bob is going back Let's go balls right back in our hands. Nice. I am T. Nice. I am T I see what he saw but he need to put some more air under that. That's why he's a pro gamer. Yep. I Think that's on me. I'm sorry. Joseph that one's on me.   I don't get why I can't die, but we can I and see that we have so many bodies back there I think this I think their QB sucks right now Got him. No. Yes. Let's go third and 14. That's easy one more big rush. No Bob get out of here Bob This is my job. I'm too good at it. Let's go just box him. Yep safety. Hey, that works.  Let's go. We get the ball back. All right guys Let's get it together start of the fourth without by just a touchdown.  I am sitting here. Hi. I think I'm butt-naked. I am and that's what you're gonna throw Did I not catch that? Right here bussing bussing. Let's just get the first buddy. Yep. Give us a shot.   I am T I am T we're gonna score. We gotta get we gotta score get a stop get another score Look at me. Look at me on him, bro. God. I'm like glue. Wow bussing bussing behind the head, bro Cut it.  You believe in me, right?  I'm so sorry Kansas City defense recovered. It's our ball Wait, what like a muffed punt? Joseph just run it in bro.  I am so open though Whips it to the dirt Joseph I hope you started me in fantasy, baby That's two touchdowns 70 yards two receptions dropping a 20 bomb right now easy Pates is big oh, we're going for two. We gotta we gotta go for two. Joseph. Just hit me again, bro Joseph half their team isn't playing just hit me again.  Joseph, bro 41 to 41 and I joined this game the chiefs were down 22 to 7.  Why don't we have three people? Where's our team? We're three people. Who is error? Dude, they've got four receivers We've got two db's and we just picked him off with pro gamer.  What are you guys doing over there? I see you Joseph. Oh my bad, Joseph. I gotta jump there. Oh good ball. Is that tutty? Is that tutty? Fortnite on them, bro. For us. Hit the orange justice.   I'm Lawrence Taylor with edge threat and you're in poverty. I'm too quick. Oh, no Come on. Come on. I assume you can't dive at the qb is what I'm learning, huh? You don't know what I do is six-year-olds in my house. Come here early Lawrence Taylor Let's go boys set up the wall build the wall. They're quitting.  Come here. Come here. Come tackle me bud.  I actually own you. I actually own you. Oh my god I can chew clock like this. Wait a minute. I could chew clock. I could win the whole game like this. Oh, no I need a block though gentlemen. Come on Joseph Let's go Joseph. We just we run the clock out. We win the ball game Somebody get this guy a map. He's six years old. He probably haven't even learned to read yet No, he's reading dr. Seuss right now.  That's your first life lesson. It's free watch.   I'm gonna cut. Oh my god. Where are you?  Oh, right. Yeah, he's not the chiefs you guys Kansas City Cherokees have won best rusher was not me granted I came in late, but I think it should have been me, bro. I had a safety How are you all of those things bro?  I had a safety I had us force fumble in a touchdown. That's the fattest stuff I'm possibly gonna get I logged in not knowing what was gonna happen in football fusion one game one dub That's all she wrote. If you guys want to see more football fusion by the way, it's actually so fun So let me know it was an absolute blast and I'll see you guys in the next one. Peace


When random people approach me on the streets and say, Adam, what is cinema to you? I look at them and say, please don't talk to me. I'm better than you are. But then I also respond with Jet Lee's The One. Much like Jean-Claude Van Damme and Double Impact, Jet Lee has to face his toughest rivalry yet. Himself. Make no mistake, The One is a pretty bad movie.  Yet, it has an almost bad, it's good charm to it. I can't turn away from, and I revisit this every once in a while for both a good laugh and to just kind of be entranced by everything happening in this film. If you thought the multiverse was a new concept, oh man, this film was doing it way ahead of the Marvel game. Maybe not the comics, but the movie was. I love when a movie takes a straightforward concept and throws it in a crazy situation. In this case, it's Jet Lee, jumping to different universes and killing variants of himself in order to become the ultimate being, the most powerful, the most God-like, The One. I also love when movies say their own title, and this one does that as well. Jet Lee can be heard saying, I am The One, or I will be The One multiple times. I eat it up, love it. Yum, yum, yum, yum, yum, yum. The visionary mind behind bringing this to the silver screen is none other than James Wong, the legendary filmmaker behind Dragon Ball Evolution. Delroy, Lindo, and Jason Statham are both in this as time cops. They can jump to the different dimensions using a convoluted watch system thingy-ma-bobber. I don't know, it's a bracelet or something. It does the trick. These characters have names, but I don't care. Gabe, I think, is the good version? It's just Jet Lee. That's all you need. The movie's like an hour and 20 minutes long. It has zero interest in diving far into the psyche of these characters or slowly playing this thing out like The Matrix, which came out just before this movie. Clear inspiration was taken. It has about the same runtime as Men in Black, and I'm thankful for that. They don't waste their time getting to things. I just want to see some action, want some cool music, want some cool effects. This gives you a little bit of all of that. I mean, it gives you a lot of it, but most of it's not very good. All of it is 100% entertaining, though. Since this movie came out in the 90s, it's a requirement to have a hot female in there. This is no exception. Carla Gugino's here playing the love interest. It works. It does the trick. She's not annoying, she's used properly, and then we get rid of her when the story says we should.  He thought it was better than The Matrix, because of course he did. It's super fast.  God's smack or corn or some random thing will come out, and it will be like a mid-song, and it will just harsh cut. No fade-out, really. No build-up. It's just there, like, ah! Stand alone! And Jetly's beating guys up in slow-mo speed-ups, which is the best part about this. We got Jetly, hidden dudes with CG bikes, punching guys who suspend in the air while he kicks another dude, and then thrust punches a third. I love it all. The film does blow its load early with one of the cooler sequences where some SWAT team members are in a parking garage. Evil Jetly comes out, takes out a handful of them. He's like... Pshh! Guy suspends. Ba-ba-ba-ba-ba-ba-ba. Mwah! Pshh! Dude's got the gun. Pshh! Pshh! And the film's really touted as a cage match, where it's Jetly versus Jetly, and it doesn't disappoint. The final 20 minutes is an epic battle that actually goes a lot longer than I originally recall it going. They fight in a warehouse. There's sparks that come down in slow motion while they're attacking. At one point he grabs an axe and throws it, catches it. Pshh! Pshh! That stuff's pretty awesome, and they do a good job with the body doubles. I didn't even notice when he's not there and when he is. Although it is Jetly, so it's possible he really did somehow split himself into two for this film. I wouldn't put it past him. If nothing else, watch this for the final moments of the film where Evil Jetly is transported to the underworld dimension, AKA hell, and he's fighting atop a pyramid. Different bad guys yelling, I am the one!  And then boom! The title comes up and we're ready to go play some paintball and have some pizza afterwards. It's a good time. Again, this is not a good movie, but it's a fun watch. It's something you can easily put on while you're having a long lunch break or something and just get it done. There's actually some pretty sweet effects work and for the most part, it holds up pretty well. The music, no, that's embarrassing.  We'd use some copyright songs, spackle it on top. It would make no sense in the sequence, but it's there and it's cool and we like it. So there it works. I'm a big fan of Jetly playing villains. He was great in Lethal Weapon 4. He works well here. I like the dynamic between the two versions of himself, battling it out. Good versus evil. Day versus night. It's the greatest matchup in the history of the world. Lex Luthor Jr. had it wrong. It's not Superman versus Batman. It's this freaking Jetly versus Jet Lee. So those are my thoughts on the one. Do you remember this film? Do you have good memories? Let me know in the comments below if you liked it. Feel free to subscribe to the channel. I post tons of movie and TV show related content here all the time. Would love to have you stick around. Make sure you hit the notification bell if you are a member so they show up in your feed. And hopefully I'll see you soon.  Cause this is what it's like in the world's collide. Ooh, ah, ah, ah, ah.   Let the body sit the floor. Let the body sit the floor.


What's up, everyone? It's your girl, Kenzie here from Leighton Sports Cards, and I'm ripping 22-23 Panini Contenders. Basketball, hobby, 4 box, break number 21. Pick your team. Got Adam K. Pistons, Ali S. Hornets, Andrew G. Thunder, Boss S. Cavs, Chang S. Celtics, Chihuan C. Magic, and Blazers. Chunwei W. Mavs, Earl S. Lakers, Edward P. Heats, Ziko M. with the Eclipse Suns, Nick Sixers, and Nets. Harper B. Kings, T-Wolves, Human H. Pacers, Josh B. Nuggets, John M. Bucks, Kosuke K. Wizards, Luke R. Jazz, Mike Y. Grizzlies, Ryan L. Pelicans, Ryan S. Rockets, Scott N. Spurs, Raptors, Tony Y. Warriors, Young S. Hawks, and Yusung J. Bowles. Alright, best of luck, everyone. Here we go. Watching some XFL over here. We got football coming up next. Four teams left. Again, we got our 4 box breaks of prism football. Here we go. Aten Russell. We've got Chris Middleton and Tony Parker. Steph Curry on the superstar die cut. We've got out of 99 playoff ticket, a Patrick Baldwin Jr. for the Warriors. Dubbs with the first auto. Brogdon and Suggs. Westbrook, James Harden. We've got Blazers, the finals ticket to 49 and for any Simons. Ricky Deere, Dyson Daniels, Luke Donchich, Sweet Shots. Giddy, Sabonis, and Paul George. Mitchell, Bagley. We've got Keegan Murray on the rookie ticket, Kings. I'm not sure who's playing. Dang, Ricky Deere. We've got Sweet Shots, Robinson, next auto up. We've got Jalen Williams for the Thunder. Jalen Williams. I end Jalen Williams. Conley and KD. Got to see who's playing after the commercials, Travis. We've got D'Angelo Russell for the T-Wolfe on the playoff ticket to 249. Ticket to the Hall, Mary Stottemire. Lottery ticket, Jabari Smith Jr. We've got Chris Paul, Kat, and Jamarant. There's two Jalen Williams can. There's an Ian and Ion. The Ian is the better one. Trayman, Kominga. We've got Mitchell, Hari Eason, Die Cut, Trey Young for the Hawks. We've got Legendary of Eddie Curry for the Bulls. It is 16 of 199. That's probably why you think you're here in so many Jalen Williams. There's two different Jalen Williams for the same, ouch, same team. Forzingus and Iodosunmu. Yeah, Andrew. Ingram, Murray. We've got first round ticket to 199, Nurkik. D'Way, CJ McCollum. We've got Wiseman, Hardaway Jr. and Dearon Fox. Westbrook, James Harden. We have Caleb Houston on the Ricky ticket. Yannis and Dirk next up. We have Season Ticket Hollow, Kauai Leonard for the Clips. Bogdanovich and Markel Foltz. Trey Young. Someone called this earlier. Jalen Brunson. We've got a gold vinyl, y'all. Oh, come on. We've got Zion to 99 Pelicans. Work of the Year, Andrew Nembard. Rudy Gobert. Got a gold vinyl auto. Kate Cunningham and Anthony Edwards. Gold vinyl auto coming, y'all. Oh boy. Rookie. We've got H. Ed Holger. Andrew G. Oh my god. I'm hearted like beating out of my chest right now.  I'll wipe my hands off. All right, Andrew.  There's insurance link. Please buy some insurance on that. If you're not going to fly down to come pick it up. Oh my gosh. Where are you? It's kind of far drive from up there. Oh my gosh. Last contenders too. I'm about to take a picture and send that in the group chat right away after this break. Okay, see Josh Giddy to 249. Palo Bancaro Rookie of the Year. Oh my gosh. We've got David Roddy on the Rookie Ticket Auto. Hands are kind of shaking. I'm trying to keep together here. Got Bob Donovich and Markel Foltz. Shengun Holiday. Call Anthony Town semifinals to 99. Someone literally said earlier, you're due for a gold vinyl. I'd say so. Egg Bajilato Ticket. Cade Edwards Porzingis. Andrew, I'd have to look at it. My mind was all over the place when I pulled that. I can look in a second for you. Wow. And we've got another case at Cumminga. And oh, I thought that was Chet again. I was about to say dude. Still a nice one though. Permanent to dominate. Short print. Dang, Andrew. Too bad your name's not Daniel.  Back at it again with the way Ben's Daniel. Johnny Davis. Halliburne, we've got Redemption. Christian Braun Rookie Ticket Variation Season Ticket. Braun is a Nugget. Nuggets. Zach Levine Tobias Harris. I don't know about that, Greg. Angrel. Murray. Forreston. Even Lillard. Kyle's been pulling crazy stuff over on drip lace recently too. Green. Same with Sam. KD on the superstar die cut. God, Donchich Van Vliet and Lamello. Matt with the baseball brace.  Last box here. Ludor Tyler Hero. We have a tie tie Washington Junior Rookie Ticket.  We've got KD. And a cracked ice Andrew Nembar Pacers.  My gosh. Indy. That's going to Human H. Nice Nembar there. 16-25. Julius Randall. John Wall. By Anthony it did. My hands are still kind of shaky. Gosh. Jamal Murray. Cam Thomas. We've got cracked ice Kauai Leonard to 25 Clippers. LeBron James. Lottery Ticket of Jalen Duran. A.D. Zion and DeMar DeRosen. Chris Middleton. CJ McCollum. We've got Anthony Davis. Demi and Lillard. A.D. Joe Chin Rookie of the Year. We've got Optic Rookie Ticket Auto. Musa Diabate. Clippers with a nice break. Rudy Gobert SGA. Last box here.  Cole Anthony. Jared Jackson Jr. T-Wolves. Rudy Gobert to 75. Chauncey Billips. Jason Tatum. Recap time. We've got Diabate Clippers. David Roddy Grizzlies. Eddie Curry-Volves. Jalen Williams, the I.N. Williams Thunder. Baldwin Jr. Grizzlies. We've got Christian Braun for the nuggets on the season ticket. Cracked ice to 25. Nembar. Dang on the permit to dominate. And card of the day. If not the week so far. One of one. Hulgren.  Congrats again on that one, Andrew. My gosh. What a hit. What a break. Thanks again. Bye.