The worst thing the narcissist can do to you. There are many horrific things that narcissists do, but there is one thing that is worse than anything else. The narcissist will manipulate you. They will condition you into adjusting to them, into achieving their desired fit, appearance and result, into being more effective and suitable for them. Instead of you adjusting to what your needs are, to the things you must have for a satisfactory life, you're not attending to your own needs. Because you've been programmed to adjust to them, you have no limits to how you're dealing with them. So you're not looking around and seeing how your situation has become aggressively worse, to how you're becoming worse in character, quality and value. It's bringing you down, it's making you depressed, but it's under the radar. So you may not notice it initially, but the longer you stay with them, the more bits and pieces of your life start to disappear, which will never be found again, which will never see the light of day, and it's never going to get better. Because they don't have your best interest in mind. They're only worried about their own needs. So when you're with them, you're damaging yourself and after a while you begin to lose your enjoyment and pleasure for life.  You're not benefiting by being with them. They're not giving you an advantage. So it will begin to affect your life. It will affect you financially. It will affect you sexually. You will develop all kinds of health problems. You will become depressed, especially when it's over, because you've been with them for such a long time.   So you haven't got the strength to pick yourself back up again. You've lost all of the passion you once had for life, all of the love you had for relationships. You've become shy and timid. You feel nervous and uncomfortable in the company of other people. You're easily frightened. You're extremely self-conscious. You're not at ease with other people. When you used to be strong and confident, you could talk to anyone. You could deal with things efficiently, but now it seems like even the simplest of things are a difficult task. You don't know how to deal with life anymore. You don't know how to be yourself because you've been who they needed you to be for such a long time that it's hard for you to get back to being who you were before.  It's like a distant memory. All you have are things that you remember from the past. Because when you're dealing with a narcissist, you lose all of your money. You lose your career. You're left lacking good qualities. You're at the end of your resources. You're reduced to a state of financial ruin.  So now there's no incentive. You don't have any motivation or enthusiasm. You've lost those feelings of energetic interest. Those feelings of excitement and desire. You've become just like them. You've become depressed. You're no longer happy with anything because it's hard for you to get back to being the person that you used to be after everything they did to you. All of the mind games, the manipulation, the lies.  It's affected your state of being comfortable, healthy and happy.  You're miserable. You're depressed. You're lonely. That's just how it is now. After you've been dealing with them for such a long time. But no matter how bad it gets, you just keep holding on. You keep trying to maintain your condition and position with them. You continue to do something difficult while waiting for help because you think that someone is coming to save you. Well, I can tell you right now that once you've given all that you have to give, they're not going to be there. They're not going to stick around. They're going to ghost you. They're going to end their relationship with you suddenly and without explanation. They're going to withdraw from all communication. And you're going to be left stuck without any support. Without any means to rebuild everything that they had destroyed. That's the loss that you're going to take. And it's a significant loss. But it's no loss for them because they were never in it for the long run. They saw it as something temporary. It was nothing more than recreational use. It was for their own personal enjoyment, which is why they never invested anything into you because they weren't trying to build anything with you. They were just with you for what they could get. Which is why once they've gotten all they can get, they're out of there. There's no two ways about it. There's no hidden meaning to their behavior. There's no other reason for them leaving. They got what they wanted. And now they're gone. Many of us overestimate our own abilities. We think we can overcome anything that narcissists do to us. But sometimes you just have to look at it for what it is. Some people never recover what they have lost. They never bounce back. They never return to their earlier condition. Because at the end of the day, we're all human. There's only so much damage that we can take. And sometimes we end up broken beyond repair to where there's no going back. There's no recovering what was lost. And those are just the effects of dealing with narcissists. But it doesn't affect them. Because they can move on. They can forget about you. And they will be fine.  They've messed your life up. Which is why many of them move on and they're good. They don't have any worries or problems. Because they know the damage they've done to you. They've left you any condition where you're not going to be good for anyone else. And they know that. So what do they have to worry about? Your life doesn't affect them. They can move on whenever they choose to. And that's exactly what they're thinking in their minds. They know that they can walk away whenever they want. And you're going to be the one who is left stuck. You're going to be the one who is left unable to fix things. Because they know the damage they've done to you. It was preordained from the very beginning. They already knew what they were going to do to you. So they know the mental condition that they have left you in. They know. And they know how hard it would be for you to compensate for their faults. Once they've turned your life upside down. They may have robbed you of your qualities and virtues.  And maybe you can't recover what was lost. But you can recover. You can return to your normal state of health mind and strength. Which is something that they're never going to be able to do. They can't recover. Because they don't think there's anything wrong with what they do. That thought doesn't even cross their mind. So they're always going to be this way. They're never going to get better. But you can. It may be hard for you to recover. But it can be done. Some people never recover. But a lot of people do. It's not definitive. It's not a guarantee. You're not just going to quickly return to your previous condition after dealing with them. You need the right type of help and advice from someone who has already been through it. And while I am not a doctor or a medical professional, I can guide you through this process. I have coached hundreds of clients over the past four years. Including psychologists, psychotherapists, lawyers and even some celebrities. And the most powerful thing that I can offer to you is my belief that you can recover from this. I believe in you. I believe in your future. I believe that you have something to contribute to the world. And that is why I am willing to invest everything I have into you. I see something in you that you may not be able to see right now. You have light. You have power. You just need to find the motivation within you. And it all begins now. What you do now will determine your future. It will dictate the outcome and results. There were times in my life where I felt like giving up. There were times where I did give up. But then I got back on my feet. I kept pushing forward. And that's what you need to do now so that you can get past this hurdle. So that you can move on to greater things. And that is why I offer my one-on-one coaching program to help you to do just that. But you need to have that motivation. You need to be ready or it's not going to work.  I invite you to buck a one-on-one with me. Head to my website. It's narksurvivor.co.uk. Buck a time and day that suits you. And let's talk about it. Let's make a new beginning.


All right, well, it's great to talk to you all here. And I just prepared some kind of general comments. So I'm an associate professor in psychology in the Center for the NeuroBase Cognition. And so I publish both in psychology, neuroscience, and in medicine. Maybe I will put this here. Can you guys hear me OK in the back? So I can speak both about my experiences in terms of being a plus one editor. I'm happy to answer questions people might have about the plus journals or about maybe I'll say a couple of things about the behind the scenes of the editorial process. Because I think that's maybe one of the advantages to some of these open access journals. But I think to frame the broader discussion, I think we're in an interesting space right now in time where we're seeing a sea change in terms of how we go about publishing our research. Lots of journals, there's all sorts of new open access journals that are coming out that are solely open access. What we're also seeing is lots of journals now that are offering an opportunity, so existing journals that we publish in, that are offering opportunities to pay a fee for articles and to have that then be immediately open access online. So I think we're going to see how this shakes out. I imagine if we did this again next year, we're going to have a very different conversation about the kind of evolving nature of how open access is going to inform our, it's sort of, I think, becoming increasingly a reality for how we're going to go about publishing our work. But as it currently stands, we have a number of really, I think, hundreds of open access journals that are out there now. One thing you do need to think about, I think, is which open access journals you're sending your work to. There's been a lot of kind of concern and some media that's come out lately about how there's sort of discredited journals and sort of obscure places in the world that are basically encouraging people to submit their science and pay outrageous fees to submit that science there, when in fact, these are not really well-recognized journals with rigorous peer review standards. So I think my recommendation, generally, to folks is if you're thinking about open access, talk to people in your field about what open access journals people are looking at. Two of the ones that we look at a lot are the PLOS journals and also the Frontiers journals. And I think those are sort of making their way into all sorts of sub-disciplines. In terms of PLOS one, this is a general science journal. We were just talking about it. It seemed to have a fairly high impact factor. And I've now published two papers there, and I serve on the editorial board there. And I think that there are some real advantages that I see, particularly with the PLOS journals. And more generally, I think this is true of these open access journals. And that's that there's a very quick peer review process in terms of the actual review of your manuscripts. And there's a very, very quick turnaround moving that paper from an accepted paper into kind of a copy edited final proof. And that's then appearing immediately online. So if you're, you know, you have students or you or yourself are really interested in getting this workout quickly, these online types of journals can be very effective for getting your workout. As far as behind the scenes go, the editorial process, at least at PLOS one, has been a really nice process. We still, there's kind of in this debate about publishing and kind of open access journals. You know, people sometimes label it as sort of pay to play type of journals. And it's sort of put in more of a kind of a stigmatized category. And I think the top open access journals, there's just an equivalent type of peer review process. The one advantage to open access journals is typically we require our reviewers to turn around manuscripts in 10 days or less. Which is in contrast, at least in psychology and classic social psychology journals, you can be waiting for four to six months for the reviews to come in. So there's kind of that much faster turnaround. But still the same types of peer review standards are held at PLOS one in terms of getting multiple and well-known peers to review the work. So overall, I think it's a really exciting time. We're seeing a real shift in the kind of landscape for how we publish our scientific research. And I think that there's some real advantages to these open access journals. I don't know if people had a chance to look going on to a place like PLOS one or Frontiers. They're all about sort of putting up metrics for kind of determining your impact. Everything from people kind of posting this on their Twitter feeds to Facebook posts. And so you can track not only the social media, but also the number of people who are downloading as well as sort of bookmarking and citing your work. Which I think is exciting and can be kind of a fun way to track the impact of your work. And I guess the last thing I'll say about open access, which is kind of the most fundamental piece of this. And that's that it provides an opportunity for the whole world to have access to this work immediately. We're sort of in a very privileged place being here in the United States at an elite institution. We sort of take for granted the fact that we can get most journal articles that we're interested in. When in fact the rest of the world doesn't have that type of luxury. And so you can see your work quickly get into the hands of people who are gonna be policy makers in other countries, to people who need this work and can translate it into their daily lives, health and well-being. So that open access I've really found makes a huge difference in terms of just your overall impact. So with that I'm sorry I can't stay longer. This is I think an important discussion. I know my colleague Mike Tarr is gonna talk about his own views on, oh you have to leave early too. But can I answer any questions? Maybe it might be most helpful for me to answer questions related to the PLOS journals. PLOS one is just one of a couple of journals that PLOS stands for Public Library of Science. And how many articles are you saying are coming out? 30,000 this year. 30,000 this year in PLOS one. So they're really trying to get a lot of, the criteria of PLOS one by the way change a little bit. It's not about the kind of perceived impact of the work of PLOS one, it's really about the quality of the work. So there's always some concern during editorial review processes, is this work that we're reviewing, is it good enough for science? Or is it good enough for nature neuroscience? Those criteria are downgraded at PLOS. The goal is really to get the work out there and to make sure that it's quality reporting and quality science as opposed to perceived impact. Okay, yeah. How many referees are you using for each article and are you doing double blind? Yeah, so I'm not doing double blind. Yeah, our field has never used double blind criteria. There's a couple journals in our field that use double blind but no, we use basically a single blind approach such that the author of the article isn't knowing who the reviewers are but the reviewers do know who the authors are. It's sort of hard in our field to kind of get away with a good true double blind. You can usually figure out who it is pretty quickly. So that was your first question. Oh, how many referees? It ranges at PLOS. The minimum is usually two plus an editor. I've been really impressed with the PLOS administrative staff. They always make sure on my papers to reach out to get a statistical consultant. So they've been really good about saying, hey, David, do you wanna also have a statistical consultant on this? We'll get someone for you. So on average with the papers that I review, I usually get two reviewers as a statistical person and then I like to read the article. So I really think of that as three and a half reviews. It ranges though. I've seen four and I've seen two at times. The deal was the reason behind avoiding the stain that science did recently. It was one of the ones that successfully turned the article away. Yeah, so are you gonna talk about the sting? Yeah, so let's save that for the next presenter because Mike Tarr, maybe it's time to turn it over and you can say a little bit about your impressions of the sting and the debate. I know you're critical. But anyway, thanks for having me and hopefully we'll have this again in the next year or two.


Oh, sorry, I was just catching up on this Facebook debate about whether it's best to record at 48 or 96 hertz. You know what, I think I may have been doing it wrong. I may go back and re-record my whole back catalogue in fact, which of course I haven't actually got around to releasing yet. Hi folks, I'm Mike and I hope you're well. I wanted to thank my cousin Gary for allowing me to use his office space here for this video while I'm away travelling. I did tell a little lie in the intro, however, I have actually released most of my back catalogue through the sponsor of this video, DistroKid, link in the description down below. What I didn't lie about was the fact that I am often distracted by ultimately useless debates in social media about various aspects of music production and I think most of it is down to a very human condition needing to be right. So I want to make perfectly clear that what I'm about to say is in no way based upon any scientific research or studies. This is merely the meandering observations of a 55 year old man. Talking about men, you may have noticed there's an awful lot of us in music production. And one of the currencies men seem to trade in apart from physical strength or financial success is knowledge or knowing stuff. Whether it's how to fix a car or how to cook a sausage on a barbecue, I've noticed that men determine their pecking order often according to who knows the most stuff. And there's an awful lot of stuff to be known in music production. But here is the thing, knowing is no substitute for doing. Let me give you a scenario that may sound familiar. John here has just finished building his first home studio, complete with RGB lighting and foam tiles. In a moment of pride, he takes a photo and posts it on a busy Facebook group. Along comes Barry. Barry informs John that his foam tiles are as useful as a chocolate teapot. And the answer is broadband absorption. And don't even get Barry started on bass traps and on how if you don't have them, your mixes are bound to underwhelm even your own mother. Then along comes Trevor. That's you. Trevor reads this interaction and it's firmly implanted in his brain that Barry is the alpha male. Now, what's often lost in this scenario is that John here writes incredible compositions which often move people to tears. While Barry, despite his extensive knowledge of broadband absorption, has never really allowed himself to become vulnerable enough to create the kind of music that people can really connect to. Now, don't get me wrong. I definitely endorse the use of good sound treatment in your studio. But I'm afraid to say that bass traps are not a doorway to the soul. Now, whilst there's quite a number of topics debated on social media about music production, there's a few that seem to do the rounds again and again. These include 44.1 or 48 versus 96 Hertz for recording or which door is best, or Mac versus PC or hardware versus plugins or studio monitors versus headphones. And now, Atmos, don't get me started. The problem is that whilst you've won that Facebook argument with your superior knowledge and you've emerged as the alpha male, in the meantime, that mix on your hard drive hasn't improved even one little bit. And that vocal arrangement you were going to record, which was going to draw listeners in and give them a sense of completeness, hasn't progressed even one bar. But that doesn't really matter, right? Because you weren't going to complete those projects until your new mic preamp arrived. And those plugins that you're going to get in the Black Friday sales. Scientists have recently discovered that there's a direct correlation between how much time you spend on social media and how much gear you think you need for music production. Actually, that's not really true. I don't think scientists have got time to research that kind of thing. But let me ask you, do you spend a lot of time on social media? Do you have a growing feeling that you need more gear and plugins? Let me know in the comments down below. Of course, you need that new microphone, right? Your favorite YouTuber said so. Well, probably they didn't exactly say that. They probably showed you how that piece of gear could slightly improve the sound of your music, but they don't usually imply that you absolutely need it for success. The reality is, you don't need to spend that much money on gear these days to get great results. And I can promise you this, no piece of gear or plugin can replace the experience you get from actually making music. Not only do I recommend getting on with recording your music, but I recommend completing it to the best of your ability at this current stage and releasing it to the world. Releasing it ensures you won't keep going back to tweak it. There's only so much experience you can get from one piece of music. Now, when you do release your music, I highly recommend that you use the sponsor for this video, DistroKid. It's really easy with DistroKid and it's very cheap. You just upload your music and your artwork and DistroKid does the rest for you. Follow the link in the description down below. So, of course, there's great value in social media. It gives us access to knowledge and opinions that otherwise we may not have had. But be careful with opinions, whether they're someone else's or your own. Opinions don't make great music. Just ask Barry, his music is crap.


It is the 21st of June 1990 and an operator is called out to an irradiation facility at Sarek in Israel. He notices a problem. The transport mechanism of the irradiator has gotten jammed. Based with the workload pressures and confronted with two conflicting indications on his control panel, the operator decides to try and clear the jam himself. The safety systems on site should prevent him from entering the irradiation room, but a known exploit of turning the system on and off multiple times releases the lock to the room. He enters to inspect the blockage. He leaves to retrieve a cart and then enters again. Within minutes, feeling his eyes start to burn, he flees the room but it was too late. He received a full body deadly radiation dose. Despite intensive medical care, he would die 36 days later. Today we're looking at the radiological accident in Sarek. As such, I'm going to rate this subject here free on my disaster scale but also free on my legacy scale. Although fairly unknown, the event shows the importance of safety procedures and the risks you are exposed to if ignored. Sarek has been the centre for Israeli nuclear research ever since the 1950s and the construction of the country's first research reactor. An irradiation facility in Sarek was built in the late 1960s. The project was a joint venture between the Netherlands and the Israeli Atomic Energy Commission. Although within the Sarek site, the facility is operated under a separate company by the name of Sorvan Radiation Limited. The radiation facility employed a model JS6500 gamma steriliser designed, manufactured and installed by Atomic Energy of Canada Limited. The unit uses Cobalt 60 as its radioactive material. The facility is used to radiate and thus sterilise prepackaged medical products amongst other items. Irradiation of an item can take many hours as it is passed through the machine in steps. Packages to be irradiated are packed in cartons and two or three of these cartons are stacked and taped together for passage through the irradiator. The boxes move through the machine via a roller system similar to the ones used on other types of production lines. Except in this case, the items move past the radioactive source multiple times in a Z-like shape to receive the required dose over two levels. To achieve movement of the carton boxes, pistons are employed at each changing direction. The amount of time the item stays in each position is controlled by a timer and when a preset timer is passed, the piston is activated. Like with all radioactive materials, its safe movement and control are vital to the overall site's safety and SREC was no different. As personnel may need to enter the irradiation room and being confronted with a whole load of Cobalt 60 would ruin most people's day. The Cobalt 60 was mounted on a source rack consisting of six modules containing multiple pencils of the radioisotope made up of two source elements within. To even out the dosage, dummy pencils were also installed in each module, totaling 42 pencils per module. When not in use, the rack is stored in a water tank and this shields staff from gamma radiation. To raise the source rack to its irradiation position, cables and hoists are used, powered by a pneumatic piston. As a fail safe, if the piston runs out of air, then via the power of gravity, the rack is plunged back into its water pool. The state of the rack is indicated to operators on the control panel via a simple micro switch, but this needs regular adjustment to give the correct information. During the 1970s and 1980s, similar systems had experienced blockages and jams. As such, the manufacturer issued a notice to install a metal shroud. However, at Sarek, this was not done. So how was the system made safe from any unwitting intruder to the irradiation room? As you don't want something like the Hanoi radiation incident to happen again. The operators controlled the system via a control panel outside the irradiation room. There are three key switches for power on, source raise and machine on. The first two control the movement of the source and the third allows movement of the transport mechanism while the source is raised. The irradiation program is interrupted and the source automatic lowered if any of the following occur, being tripped by a safety interlock or if sensors detect high temperatures in the irradiation room, low pressure in the pneumatic hoist system or misaligned cartons jamming the transport mechanism. If a product jam stops the source rack from returning to its pond, then an alarm should sound to the operator. To enter the irradiation room, a key switch that operates the door lock solenoid is linked up to a radiation monitor. Need is to say if radiation levels are registered above background, then the door cannot be unlocked. To gain access to the room, the operator first has to press the monitor test button. The radiation detector checks the reading in the room. If OK, the button can be released. Then this is checked again to make sure the room is at background levels. After this, the lock will be released. All of this is also interlocked with the source rack position sensor. If not in the pool, then the door also cannot be released. I should say, also if the radiation alarm is going off, then the test cannot be attempted as the lock to the door is completely de-energised. Once entrance to the room is granted, the operator must make their way for an area called the maze. Finally, entering the irradiation room. There is emergency cut-off pool string attached to the wall of the room, which if pulled will drop the source rack back into the pool. Of a total workforce of 20 at Sorvan, there were four operating staff, a senior technician who had worked at the plant since it was built in the late 1960s and three technicians. Each had been certified and had at least one year's practical experience, which was a requirement to operate the facility. Due to the equipment being from Canada, much of the operating manuals were in English. Only a short list of routine operating and safety instructions, including the procedure for entering the irradiator, had been issued in Hebrew. This led to some confusion as not all the operators were very proficient in English. The irradiator was often in operation 24 hours a day due to the high workload, but it was only staffed on a regular day shift. The conveyor was long enough to hold five to seven hours' worth of cartons. Before leaving, at the end of the day shift, the staff loaded the input conveyor to its full capacity and completely unloaded the output conveyor. At around midnight, an operator would go to the facility to reload and unload the conveyor for the night. Due to the facility being unattended, the source rack down indicator is hardwired to the emergency control centre of the SUREC Research Nuclear Test Centre, and is staffed 24 hours a day. In the event of a malfunction, the on-call operator would be requested to attend and rectify any faults. This leads us onto the summer solstice of 1990 and a jam occurring at the irradiation facility just after 5pm. At around 5pm on the 21st of June 1990, a jam occurred in the transport mechanism in the irradiator room. This caused cartons on other parts of the conveyor to burst open. One carton was pushed towards the source rack. The overdose timer detected the jam and the control system automatically initiated the source rack to be Displaced cartons on the lower conveyor stopped the rack from lowering back into the pool. The micro switch on the source hoist malfunctioned and incorrectly indicated that the source rack was fully down. The product jam was registered at the emergency centre at the SUREC Nuclear Research Centre and the SOARVAN duty operator was informed at home by telephone. An unqualified staff member silenced the alarm by disconnecting it from the control panel by 5.35pm the on-call operator had attended and reconnected the alarm. On the console the product jam and source down light were illuminated. Confusingly the radiation alarm was sounding indicating a high level of radiation. These were all conflicting indications for the operator. The situations like this two operators are required to be in attendance but strangely he decided to deal with the issue alone and this is most likely due to production pressures. Based with conflicting information the operator decided to ignore the radiation alarm and believed the source rack was safely in the pool. Little did he know but the vital micro switch used to prove the source rack location had not been adjusted correctly and was thus defective. To silence the alarm the operator went behind the console and disconnected the cable from the radiation monitor to the alarm and control circuitry. This should have meant that the door to the radiation room could not be opened as the radiation monitor test would automatically fail but there's a little knack to bypass this. The key from the machine switch can be removed and inserted into the power switch which if cycled on and off several times while pushing the test button tricks the monitor into thinking that he's reading background radiation. After bypassing the interlock the operator entered the maze. He took with him a small radiation monitor but did not calibrate it. As he entered the room he should have been greeted with the blue glow from the source rack in the pool caused by a Cherenkov radiation. Not noticing that he still continued in the side. The operator left the room to fetch a cart. After re-entering the room he began to remove the damaged cartons from the conveyor.  He fled the room and contacted at 5.45pm who's superior the senior technician and explained what happened.  The senior technician telephoned the emergency centre at Sorek Nuclear Research Centre. An RSO from the research centre came to assist and after being explained on how to gain access to the room went into the maze with a dosimeter. His reading was at 0.5 cv. An hour. The 32 year old operator was transported to the Ichilov Medical Centre in Tel Aviv where he was examined by a physician 2 hours and 15 minutes after exposure. At this point it was thought that his exposure was 10 to 20 grey over a period of around 2 minutes. As a note 4 grey has killed people before. For the first few days he vomited regularly each day and continued to fill nausea. By day 4 he was given a bone marrow transplant. The white blood cell count continued to drop rapidly on day 5 and by day 22 the symptoms continued with a fever of 40 degrees centigrade. Liver function continued to deteriorate in testing and the sickness increased. By day 34 he was confused and bedridden. At 2 am on the 27th July 1990 day 36 the patient died. It was found during the autopsy that death was linked to his radiation exposure and GVHD graft versus host disease. This happens when after a bone marrow transfer the white blood cells from the donor start attacking the recipient which ultimately can cause organ failure. After the accident the source rack was returned to its safe position later that evening on the 21st of June after taking advice from the suppliers headquarters in Canada. Investigators set out to find out why the operator acted as he did. As noted in the IAEA reports that a properly translated manual for the operators could have helped with fault finding as well as stricter training by properly configuring any portable radiation monitors before entry to an irradiation area. Moreover if the operator had followed the rules and requested another member of staff to assist then the dangerous path he went down likely wouldn't have happened. It was also found that entrance security to the irradiation room was easily bypassed by playing with the console by repeatedly cycling the key in the power switch. Also the micro switch needed proper adjustment was found to be faulty leading to the incorrect indications on the operator's panel but essentially preventing the jam from the start would have averted the radiation incident. If the company had heeded warnings in the 1970s and 80s and installed the recommended shroud then the jam and the source rack might not have happened at all. Needless to say these were key recommendations given from the IAEA to the facilities management. It is a shame that pressure to get production running again led the operator to undertake actions that turned out to be pretty deadly but as they say rule books are written in blood. This is a plain default production. All videos on the channel are created commons attribution share alike licensed. Plain default videos are produced by me John in the currently raining southeastern corner of London UK. Help the channel grow by liking commenting and subscribing. Check out my Twitter for all sorts of odds and sods as well as future hints on videos. I've got Patreon and YouTube membership as well so if you fancy supporting the channel financially you can check them out. And all that's left to say is thank you for watching.


Hello and welcome to the Ed Hodl show. I'm Greg Royce showing here by Stevenson head football coach at Hodl and coach last Saturday played Mr. Cordia and Had a big 65 to 7 win. I'm just talking a little bit about the victory. It's good team win made a couple plays in special teams Obviously 674 yards of total offense and eight touchdowns was Quite impressive, you know, we scored on 11 of 12 drives. We didn't punt to the fourth quarter You know, obviously to have that type of offensive success. You've got to have some defensive success as well And once we settled into the game plan, I think the guys played particularly well And you know, it's a good team win for us and good to go into the bi-week after a performance like that Yeah, despite even like you said you scored on 11 12 drives We still didn't really feel like you felt like they were moving the ball a little bit and really until it started Second half when you guys scored like three times in the first eight minutes They really feel like a comfortable working margin, right, you know, again I think and I think we talked about a pregame what they do offensively is is a bit of a challenge and you know We had to really really fine-tune what we were doing defensively and get them off the field and get them off schedule So as we got into the actual game and then we're able to make the adjustments It did have a little bit of a different feel and hats off to them You know that that's a program that's you know, we feel like is on the rise and doing a nice job Yeah, obviously Dan Williams another big day almost 400 yards passing five touchdowns You know program record for yards another record to kind of flew under the radar a little bit as Ian Gould your freshman kicker I'm 17 points three for three up field goals eight for eight on extra points hasn't missed the PAT this year Talk about what he's meant so far to the program I mean the biggest thing that Ian's brought to us thus far is crazy consistency in the kicking game You know, he's he's perfect on PAT's like you said and the one miss the one field goal miss He has you know, we put him in a bad spot 45 yards out with the wind in his face and you know when we're playing Kings So, you know, he just brings this consistency. He's not an emotional guy He's a guy that just goes out and does his job and you know That's really really refreshing to see a young kid be able to go out and no moments been too big for him yet He's just goes out and does his job and He's a remarkable student and a really really good guy to have in our program and we feel like you know The future is very very bright for him. Yeah And obviously with with the win you were able to get some different guys in and some different guys scored as well Sebastian that quad hill was it was it nice to get some different guys in the ashing in some different guys involved It is you whenever you can get varsity snaps for your younger players. It's huge that's the one thing that you can never replicate in practice and and Really becomes a commodity as you work to develop players is those varsity snaps And you know having those guys have an opportunity to go out and have success on Saturday is is very exciting And it's really fun to watch our sideline when when the younger guys get a chance to Score or make a big play and to see the older guys being you know as excited as they are for the younger guys Is there is a really really cool thing to watch. Yeah, absolutely Now you've got the bye week this week I was probably one of the primary goals is to get healthy not just not just guys that aren't playing but guys that are maybe a Little banged up. I know everybody's a little banged up this time of year But just get some guys maybe closer to a hundred percent in the off-week. That's the key is is you know I left them with yesterday post practice was you know use this time obviously academics are going to be really really important But but getting off your feet getting so much needed rest and getting those extra treatments in the training room and getting back to as Close as you can be 200% and you know you look at where we are in the conference We're you know we're tied for second and I anything can happen as it often does in the Mac and you know We've got to stay focused week-to-week and and this week the focus is Rest and get better and get caught up on your schoolwork, and we've got to win this week as well It's you know just because we don't have a game on Saturday doesn't mean the mentality changes at all for our players and you Know after yesterday's practice, you know, we feel pretty good. It was it was an up-tempo practice I don't know if they were excited to be a practice yesterday, or they were excited that they didn't have to get up at six This morning But it was there was a lot of energy out there and then the guys seem focused Yeah, it's probably a little bit of both on that one. Absolutely. Well coach. Thanks for your time Enjoy the rest of the off-week, and I'm sure we'll be back next week to talk about a love valve. Thank you All right for Ed Hoddle. I'm Greg Royce. This has been the Ed Hoddle show


Well, hello everybody and welcome to the GitLab 1111 kickoff meeting. What we'll be talking about some of the features that we're releasing in our upcoming release. This will be the one next month. So what we're going to be doing is going through each of the categories that make up make up the GitLab DevOps stages and talking about the individual features from each of the product managers that are going to be presenting those. So again, my name is Jason Lenny and I'm product manager here. And to start things off, I'll turn it over to Jeremy for Manage. Thanks a lot, Jason. I really appreciate it. So this is I'm Jeremy Watson, product manager for the Manage stage of the DevOps life cycle here at GitLab. So Manage stage is really all about helping enterprises and large instances really prosper with strong configuration. In this release 11.11 we're really focusing in on access control and enabling some of that configuration in order to help instances stay more secure. So here to talk about like four really exciting premium slash silver level features that we're adding in 11.11. The first two are related to LDAP. So what typically large instances will do who are aligned at LDAP is they'll use that as a single source of truth to not only help determine identity but also access control by using LDAP group sync. Well, one issue that we want to solve is that LDAP doesn't allow you to use it as an immutable source of truth. Group owners and group maintainers are still able to add users to the group outside of LDAP sync. In 11.11 we're going to be able to enable locking memberships to LDAP sync and also enabling group owners optionally by from as an option from that's enabled by GitLab administrators to allow group owners to manually add members to that. So LDAP can be a very secure and immutable option for maintaining a single source of truth for your users. In addition, we're also enabling a configurational option to only allow non-adminced archive projects not delete them in GitLab. Deleting actually is deleting and some instances require a data retention policy that only allows or will allow non-admins to actually archive projects and delete them. So we're enabling that more than 11.11. And the last feature that I'm really excited about especially for GitLab.com is allow restricting group members by a domain whitelist. Sometimes you want to make sure that a group in the lab can only be accessed only certain members can be added to it. And in 11.11 you'll actually be able to specify a domain mask to only make sure that certain members who match a email pattern can actually be added to the group. So this is especially useful for groups on GitLab.com when you want to make sure that your membership can be tightly controlled and you're only adding certain members potentially employees of your organization. Now you can do that and make sure that your group stays secure. So that's what's going on in Manage. Jason, back to you. I think some really nice features there that are going to help with managing users. That's for sure. Victor, over to you for plan. Thanks Jason. For plan we're working on a couple of things. We're going to continue pushing in the realm of portfolio management. So Jason if you don't mind click on the first link there view epic tree and epic. That's something we've already started in a previous release in particular 11.10. What we're doing is we're going to be able to see child issues in your current issue or let me correct myself where we're already able to do that as a couple of releases ago. But what we will be shipping in a couple of weeks is the ability to see the roadmap view inside the epic. So if you're an epic and you have children epics you can see the roadmap the Gantt chart as it were of those child epics inside the epic page itself. And for this particular issue we're not only going to be able to see the roadmap page or roadmap bars. You're also going to be able to see the child epics formatted in a tree structure. So similar to you know Windows Explorer or finder on Mac where you can see you know your directory your files in a tree structure you're going to be able to do that here as well. So that's something we're really excited about from a work breakdown structure perspective and something we're really excited about. The next feature I wanted to talk about is scoped labels. That's the second link Jason if you don't mind clicking. We're actually shipping that again in a couple of weeks in 11.10. Last time around we call this a key value label. So scoped labels is the same thing we just renamed it to something that that's a little bit easier to understand. And so what we're shipping in a couple of weeks will be functionality to have mutually exclusive scoped labels. And this issue of what we're going to do is make it a little bit easier to understand by styling it a little bit different. So what you see on the screen there you see DevOps plan DevOps is the scope it's the key as it were and plan is refers to that value. So something we're really excited about we're going to make a couple of other changes to scope labels as well but this one is definitely the highlight for this iteration. And then the last two are things that we've been working on in the past couple of releases. We had some technical underpinnings that we needed to fix. I'm excited that we'll actually be able to ship these very soon. So go ahead and click on them and see those designs at your own time but I wanted to turn it back to Jason. Thanks Victor. That epic tree and epic wine is really cool looking. And I like the way the styles look on the labels. Over to you James. Thanks Jason. If you click through onto the first issue about resolve discussions a few releases ago we introduced the ability to suggest changes to a merge request if and at the moment when you apply it you also have to click resolve discussion to mark the discussion as resolved. And in most instances that is the typical behavior that the user is expecting and would like. So what we'll be doing is removing that second step and making it a one-click action to apply and resolve the discussion with the suggested change. So that should be a really great improvement for people who are adopting that. And we're also in a separate issue hoping to make the feature more visible and easy to find. Thanks Jason. The next item to highlight is around WebID workflows with forking. And you can take a look at the design on that issue. At the moment when you open a you can't open projects that you only have read only access to because you won't be able to commit your changes and we don't want people to make changes and then realize they don't have permissions to commit them. But in 11.11 we'll be adding support for forking workflows in the WebID so you'll be able to open a read only project and then in the commit interface create a fork and commit it to that fork at the same time. Also related to forking we're excited to be getting what we hope to reach general availability for de-duplicated forks. So when you fork a repository we make a full copy of all the data in your fork. And that uses twice the disk space means that creating a fork is relatively slow because we have to copy all the data. And we're hoping in 11.11 to de-duplicate that data. So forking won't necessarily be faster initially but the disk storage requirements will be essentially zero when you first create the fork and only the difference as the fork diverges will be stored. Next up is improvements around LFS. So we've had mirroring features for many years in GitLab and great support for LFS but we didn't support mirroring and LFS together and that creates a bit of a problem for projects that want to use both features either for a project maybe stored in GitHub and they're using GitLab CI or you have multiple GitLab instances and need to mirror the entire project from one location to another. So we'll be adding support for LFS objects. And finally we'll be making our first iteration on group merge requests which is allowing merge requests across different projects to be related together and then enforcing merge order. So making sure that a service that needs to change first doesn't merge after something else that depends on the change. So making sure that that relationship is expressed and that'll really help large monolithic projects with lots of microservices that need to coordinate the order of merging do that efficiently. Thanks Jason, back to you. Thanks James. I love the suggested change workflow in GitLab and it's cool to see that we continue to iterate on it. Brendan over to you from Verify. Great. Yeah thanks Jason. My name is Brendan O'Leary and I'm a product manager for the Verify stage here at GitLab. Verify covers both CI which is continuous integration as well as automated testing such as unit and system testing. Today I want to talk about two issues. As you can see there are more than two issues here but a few of these are left over from our 1110 release including the vault group of concept integration as well as the windows container executor and cross project upstream options. We're really excited to see these as well but if you want to learn more about them check off our kick off video for GitLab 1110 for the details on how those features work. The first issue that's new to 1111 is visual review apps. This will be our first step into a new category usability testing which is part of our 2019 product vision. So this feature will allow users to look at and comment on a review app directly from within that review app. Those comments then become discussions in the associated merge requests. This will help designers, product managers and other stakeholders review the visual and UX changes to an application just as easily as their development leads can review the code changes right in our request. The second issue is about renaming trigger to downstream. Trigger is what lets you decide what project should be built after the current project's pipeline is run and today that's the word we're used for. To go with the upstream triggered by option that we're adding in 1111 will be renaming triggered downstream to kind of avoid confusion about what that exactly means. And so big shout out to our UX research team who helped out with this, helped us to understand kind of with data how to name this feature and make it least confusing for our users and customers and other stakeholders that all contributed to that research. Yeah, so back to you Jason. Great, thanks Brendan. The visual review app item really has a ton of potential. I'm excited to see how that can enable teams who do review workflows using review app. So thank you for that. And then the next two items are mine. So the package team is responsible for repositories for the various kinds of artifacts that you either depend on or build as part of your release process. And we'll be finishing up the group level dependency proxy MVC in this release which we also talked about in the 11.10 kickoff. And then two new things that we're adding are a template to build and push to the MPM registry as well as one for the Maven registry which will show you how easy it is to get this set up and working. One more item that we're also looking at is ensuring that the registry registry garbage collection task deletes all of the blogs that it's supposed to do. We're continuing to focus a lot on making sure that the cleanup and maintenance of the repositories is also easy to do with GitLab. Then for the release category which is all about continuous delivery and the things that support it. One of the most exciting things that we're doing I think in this release is merge trains from merge request pipelines. So what this is going to let you do is queue up a series of merge requests that can all run in sequence and merge in an ordered fashion into master. And there's some optimizations and efficiency hacks that we can do there taking advantage of that pipeline to make sure that everything comes in as quickly as possible without using too many compute resources but also in a way that keeps master green. So I'd encourage you to check out that issue give us feedback on how you see that coming together. It builds on our merge request pipelines feature that's been out for a bit now and we've been continuing to iterate on. And again it's one that I'm super super excited about. Another interesting one here is adding type or extensible environment variables. So what this is is being able to set an environment variable in your project that has a type associated with it and so this may create a file on your file system. It may be a certificate and the benefit of us knowing the type of the variable is that we can do a lot of validation. If you've ever had a situation where you've had an expert space and a certificate and everything is failing and you can't figure out why you don't understand why this validation can be really really powerful. We have a few other items here that are nice but I'd encourage you to take a look at those on your own time if you're interested. They're great features but we'll move on for now. So with that I'll move things over to you Daniel for Configure. Thank you Jason. I'm Daniel I'm the product manager for the Configure stage here at GitLab as we have some exciting things that we're going to work on on 1111. The first item comes from 1110 though and we're just going to get it over the line and that's disabling Kubernetes resource creation. So as you know when you use the Kubernetes integration today we create a namespace and a service account dedicated for that specific project so we want to give users the ability to manage that on their own. That is GitLab will no longer create those resources for you but you will be able to manage those in a more fine-brained manner. Then the second thing that we're going to work on here is the ability to provide separate namespaces for each project as part of the Kubernetes integration. As you know every name space or sorry every environment deploys to the same name space that is created for that project. So let's say if you want to deploy to a different name space for staging versus development this will be now supported with this feature and this will be great because the ability to run different environments and different namespaces allows you to do more things around security and appointments. Then the third thing is that we want to allow users to uninstall the apps that they have deployed through the GitLab Kubernetes integration. So let's say you deploy the runner as part of your GitLab integration but then you want to stand it up in a VM and no longer in your Kubernetes cluster you will be able to uninstall the runner from your Kubernetes cluster. Then we move on to validating the Kubernetes credentials that you provide when you create a cluster. So when you add an existing cluster we ask you for a couple of things such as a certificate, a token, and an API endpoint. So right now we don't validate those so if there was a problem with any of those you wouldn't know until you deploy something or you make news of your cluster so we really want to make sure that the data that is being entered by the user is valid and we let you know that early to minimize problems. Then we move on to instance level cluster configuration. As you know today you can create a cluster at either the project group level with this feature you will be able to create a cluster at the instance level so all of the users for your instance can take advantage of Kubernetes. And then the very last thing is around serverless so that is the ability to use the GitLab serverless features with an existing k-native installation. That is when you bring a cluster that already has k-native installed on it we can't currently make use of the great features that we have around GitLab serverless and so this is all about enabling that if you bring your own cluster that already has k-native and that's it for the configure team back to you Jason. Thanks Daniel some great improvements there over to you Josh for Monagre. Jason I don't think Josh is on right okay let's come back to that Fabio do you mind going that way secure? Yes Jason thank you for that so for secure in 11.11 we are planning to work on a security reports API so we have security reports that will give you the list of vulnerabilities that is affecting your software and this list is used in the GitLab UI to populate the security dashboard of the merge request widget. We started it at the beginning as regular artifact but then we make it more first class and so now they have a specific format and they use a different syntax this will prevent the JSON files created by the security tools to be available as raw artifacts. We know that there is a need to download this information in a machine readable format like Jason because teams I mean the security teams want to automate security on top of these results so with this iteration we'll provide a new API and point that will make available this information again and it will improve it so now you can define multiple jobs that will create multiple reports for the same kind of vulnerability for example SAST. The API will aggregate all of them and will send you a polished version with the exit list you want to take on this API so this is very very important it has been a requirement from customers but also from our internal security team so we're very happy that we can work on it now. We also want to provide an option to enable active scan for this for dynamic application security testing at the moment DAST is out of the box doing passive testing and so it's not fully finding all the possible vulnerabilities that are affecting your application we thought about that we consider different options and we figured out that enabling the active type of scan for DAST is very valuable it will give you more results more information and it will not be so invasive anyway we will not do it by default and we'll allow users to define an environment variable in case they want to switch to the active scan model based on the feedback we'll get on this we'll define if we can have a better default or if we can consider different situations for example we can run active scans on review apps that are disposable and there is no way that can provide they will provide a problem production and the actual passive scan on production only so we make sure that this scan will not impact availability of your website. The third issue we want to work in 11.11 for the secure stage is to add an optional reason when dismissing vulnerabilities we add a very strong feedback from customers and analysts saying that collaboration between security teams and developers is better if security teams know why a vulnerability has been dismissed by a developer so that's the reason why we are considering adding a reason the reason will be optional so it will not create any friction to developers if they don't need if they don't want to go through this path but in case they want to add a note so other people can see it when looking at this miss vulnerability it will be possible and that's all for secure back to you thanks Fabio I love that the collaborative feature there of making sure that the information is flowing back between the teams in a natural way it's a nice one look over to you for fulfillment yeah thanks Jason um so in 11.10 we introduced the ability for users to buy additional CR run-of-minutes this is only added to paid plans so in order to iterate upon that we wanted to add the ability to buy CR run-of-minutes for free plans so that that was a little bit more complex to include in the first iteration so breaking it out and we'll hope to continue on this next one thanks Jason that's fine thank you Eric over to you for distribution geo and then monitor that one as well yep absolutely thanks Jason so postgres 10 brings about a number of performance improvements but namely aggregate pushdown support which would really benefit our geo product and so for distribution we're planning on shipping postgres 10 in the omnibus package alongside postgres 9.6 in 11.11 users will have the ability to manually upgrade postgres 10 fresh githlab installations will still have postgres 9.6 and if you upgrade from 11.10 to 11.11 we're not going to touch your existing postgres version so we're really excited about the performance improvements that postgres 10 will bring about in the future the other interesting thing out of distribution is is we're working on automatically importing an enterprise license on githlab install so this will help on a lot of internal users to essentially apply a license against your githlab installation right after it's right after it's brought up without a manual license application but the primary use case for this is for our marketplace images and so dovetailing into the third item in the list we hope to have a an official supported amazon marketplace image of githlab ultimate supported by 11.11 with a license automatically applied when that am i is deployed to an ec2 instance moving on to geo so i'm also really excited to announce that we're planning on supporting a geo for kubernetes in 11.11 so this is adding support to the githlab helm charts for geo and then moving back up to monitor there's a number of improvements for monitor that we're doing so one of the first things is we're adding new unicorn metrics so we're going to add process stop and start time and also the number of unicorn workers that are being tracked we're replacing the m tail metrics with our native unicorn metric code for stability we are also planning on adding instance metrics type to the usage ping allowing us to get a little bit more information about who's using these these metrics and in githlab instances and then the last thing to to make a note of on monitor is we added monitoring for the integrated githlab registry recently but we didn't yet add the metrics to the omnibus dashboard and so in 11.11 we're planning on adding those metrics into the dashboard and so those are the ones we wanted to highlight from monitor there's a few other ones there take a look please comment on the issue if you have any comments back to you jason thanks so much eric so many great items in this uh in this release it's uh it seems always be the case but i love working for a company where we can touch so much of the dev ops pipeline and deliver so many great things to so many different kinds of people uh every time i'm always blown away as we tend to say best release ever i think this is going to be another one thanks everybody for for watching feel free to reach out to us on the issues we always welcome contribution collaboration and we'll talk to you soon


In this video, I'm going to show you how to align your laser to your material in three easy steps. My name's Jim and this is the edge of tech.  Well, I can tell you that in three easy steps, I can show you how to do that using Lightburn. Now Lightburn is a software you can pay for, but you can try it for free for 30 days. The link is in the description below. I have no affiliate with them or anything. I just really believe in their product. It's an amazing product for lasers. So today, using Lightburn, I'm going to show you how to create a frame. I'm going to show you how to center that frame on your material, and I'm going to show you how to see the frame on your material. Then if you stick around, I'm going to give you one more bonus tip. So in the interest of keeping this video short and getting you up and going faster, let's do it. So Lightburn is open. And at the top left, you notice we have Lightburn version 0.9.20. And that is an actual brand new version of Lightburn and updated last night. But this should work going backwards. It's all about the same. So step number one, grab your square tool here, come out, hold control on your keyboard and draw yourself a square.   What I want to do is make this the size of the material. In my case, let's do four inches by four inches, because I'm going to show you a tile today. So I'm going to lock this so the ratio stays the same if anything gets changed. And then I'm going to come into the center here where it gives you the crosshair. And I'm going to move this down to let's say about right there. It's not quite center of the bed, but it's close, maybe maybe right there. So you put it on the bed or on the surface wherever you want to do your burn at. In my case, I'm going to do it right there. Then what I want to do is make this an actual burn layer. I like the color blue. So I'm going to use the blue layer number one. And if we go to the right, we'll see that this is a fill layer. I use 3000 speed. That's millimeters a minute and 50 power. I'm using the Artour laser master to 20 watt version with the G8 lens. That's just the power I used before. So once we have it in the blue, you can really see it. Step number two, what we need to do is find the center and align our work. So I like to go over here to the job origin on the right side, make sure it's in the center. You can use the top right, top left, whatever you want. In my case, I'm going to use the center. And then I'm going to go to the move tab. And I want to make sure I have this fire button right here. If you do not see this fire button, we have to back up and do the next couple steps. So you should see this if you're using a diode laser. If you do not, here we go go to the top left where it says edit, go to device settings. And on the right side here, you say something called enable laser fire button. Make sure that's green. If it's off, turn it on. And what that's going to do is it's going to test, it's going to enable the test fire button that's used for focusing diode lasers. And it can be incredibly dangerous for CO2 lasers. If you use this, be extremely careful and use as low as power as you can. That's a disclaimer from lightburn. So once that's enabled, hit okay. And if you did not have this enabled, and if you did not have it enabled originally, you'll have to close lightburn and reopen it for that button to come.  And we're going to do that now to find the center of our work. So what we want to do after we have our fire button enabled, and we have the center origin shows right down here is we want to click this little button right here. And what that button does is it sets the laser position by clicking on the page, you can click anywhere on your build surface, and the laser will move there. This is the same in a CO2 laser.  That's about the center of our project. And you hit go. And you'll watch the laser move to the center of where it wants that project to be. When we find the center, I'm going to hit this fire button. And when I hit that fire button, the beam is going to come on. And I'm going to place my tile about in the center of where that beam is. So let's try that now. So I hit the fire button, the beam comes on. I can take my tile, and I can place it about in the center of where I think the center will be. So I'm thinking somewhere in about right there. So as you can see, the beam is right in the center there. I have my safety glasses on just in case always where your safety glasses when your beam is on. And then this is the center of your tile. Now some people will come down and mark center, and they'll mark center and draw lines in and put a dot with a pencil right in the center of their work. That's a very good idea. In this case, I'm showing you on a piece I already burned. So I don't want to do that. But just so you know, you want to try to find about the center of that work. So now we're back in light burn. Once we found about the center of our work, we're going to turn off that fire button by clicking it again. So after we turned off the fire button, we'll go to step number three and the final step of aligning your work for your laser. So if I hit this frame button, what it's going to do is go around the perimeter of our tile at four inches. So I'll show you what that looks like on the camera. If I hit this, you'll see the laser move. And it goes around where it's going to burn. The issue with that is is we can't see exactly where it's going to burn on the bed or on our material, because there's no dot, there's no laser guidance or anything like that yet. So what we want to do is I'm going to turn this up a little bit so you guys can see it on the camera. But I'm going to hold shift key. And I'm going to hit that frame button. And when I do that, you're going to see the laser go in a frame again. But this time, it's actually going to fire the laser at whatever percentage you have it set at, keep it as low as you can. In this case, I just turned it up so the camera would catch it better. But I only shift key, hit that frame button and watch what happens. Perfect. So it goes around the outside of the laser. And we're pretty close. So at this point, what you want to do is look at that. You'd want to hold your shift key down, hit that button again, and kind of watch where it is. It looks like it's a little bit far to the right. And a little, it's about right up and down, but a little bit far to the right. So we're just going to move it over to the right, just a hair.  And then once we move it over, hit shift again, hit that fire button, and we should see it just about perfect. That looks great. And that's it. Once you have your material framed, anything you do will be lined up. Now you want to make sure that it's straight, that if you're watching your laser go, it's not drifting off up or down or anything like that. Make sure everything is straight inside of that frame. So that was the three steps in getting your laser aligned with the material you're working on. And it's very easy. Once you do it a couple of times, you'll get it going. Now sometimes it takes five, six tries to get that thing lined up.  So here's a bonus for you. Right now we have this highlighted in its blue. I like to do this around almost everything I burn. You don't have to do this, but this is just how I like to do this. Come down here and hit the T1 or tool one button, and that'll change everything to orange in our square. So if I go look at the cut and layers tab, it's now a tool layer. Right now it is on, I can turn it off by clicking this button, I can turn it back on here. Also this frame button here will enable or disable the layer when computing the origin and framing operations. So if you leave this on, it's actually going to frame around this when it's computing the origin and where everything goes. So what I like to do is create my path just like I showed you, change it to a tool path like this. Then I like to go find a project to put inside of it. I'll just use this, I need coffee because it's early. I'm going to put it right in the center of my project and here's a little secret bonus tip number two. If you have your project outlined and it's a tool path or another path, if you go right to the center in light burn, you'll see the crosshair come up. If you grab that crosshair and drag it, it should find the center between the current layer and the layer that you're putting it into. In this case, they're both four inches or darn near four inches and it centered it perfect. So as you saw, it snapped in. If I drag it out, you can see that again. Ready? Snap, just like that. I know that this is perfectly centered in that tile we already aligned on the build surface. So now all I have to do to check that is hit my shift key, hit this frame button and on the camera, you can see exactly where it's going to frame and it did not change anything. Now, what I obviously what you need to do is change this to a tool path that's going to work. In our case, we'll use blue and it says it's an image. I like to use vector files, but that's a whole nother video. Once it is in there and you see this is your blue layer, there's an orange layer underneath it. You have it you have it to your output here and you set your settings to wherever you need them and you hit go. So the cool thing about that, so the cool thing about this is we know that this image here is going to burn in the center of the tile we already aligned. It can be any size that you make that in this case was a four by four tile. And as long as your tile is aligned on the build surface over on the laser, you're going to get a straight aligned image every single time. So there you have it. I showed you how to create a frame and light burn. I showed you how to position your material on the build surface of your laser and I showed you how to show where that laser is actually going to burn on the frame. Also, I gave you the bonus tip of putting your image, your file or whatever you're going to burn inside of that frame. So you make sure it's centered every single time. I hope you learned something today. I hope this video helped. And as always, keep burning. Hey everybody, I hope you liked the video today. I hope you guys learned something. If you did, give me that thumbs up, hit that subscribe button right here and the bell right over here to get notified anytime we go live on Monday nights for hot makes or anytime a great new video comes out. I really appreciate you guys watching these laser videos. You guys rock.