Now we're ready to do the power supply. We have the bottom cover off. We did that in the last video and you'll be able to find that video here if you need to know how to do that. But what we're going to do is remove the power supply now and we're going to swap this with a brand new mean whale one. Let's do it. So while it's still laying down, this is the offender right here. This is what we're going to be replacing. This is our power supply and we're ready to take the power supply off. There's four bolts right up here. You're going to grab your Allen wrench and remove these and be careful and hold this because the power supply is going to come down. So I backed the camera up a little bit and I got this last bolt out and I'm holding the power supply very carefully here. What I want to do is set it down just like that. We'll leave it right here sitting just like this and we're actually going to swap it to the new one and it's super simple. You take your new mean whale power supply and you set it right in front of the old one. And the reason I do this is I want to point out that all of these here are going to match up in the same spots on the new power supply. The best way I found to do this is to loosen one from the back, take it out and then you'll loosen the mean whale here and you'll push this fork in like this. Once you've got it in there, just tighten it down, give it a little tug, make sure it's good and then we're going to do that for all of them and this is the easiest way to do it. Just note the location in case you get one out of whack, but you should be pretty simple. Loosen them up, move them over here and then we'll go from there. As you can see, I put the old one in front to show you that there's a height difference in these. That means the bolt patterns are going to be a little bit different on them. So we'll take this one away and you can see all of these are in now the way they're supposed to be. And I pop the cap on the top to protect them right here. That just snaps back down. Now what we need to do is actually reinstall our power supply. To do that, we're actually going to go right over the top of these cables. So this power supply actually holds those behind it and kind of keeps them secure like this. So take your power supply and put it up, match the bolts up in the front here. Remember that the bolt patterns a little different on the new power supply. So you're only going to use two bolts right here. So get your bolts started and tighten them in and then you'll be done installing the power supply. Now you can see it's all installed very nicely. It's held up by these two bolts and it's in here pretty dang good. It is hiding the ones behind it like the old one did. Now we should be rocking and rolling with a brand new mean well power supply. This thing is going to be awesome. Now that the power supply is in, if you are here just to install the power supply, you're done.  That's all you have to do. You're good to go. Don't forget to switch the little switch up here to make sure you're on the right voltage, either 230 or 115. I have it set at 115, just so you guys all know. And you can put this back together and rock and roll. If you're here for the series, we have one more video in the series and at the end of that video, it's going to show everything together and working. The next thing we're going to do is get rid of the touchscreen, put a regular screen on this thing, put the TH3D firmware on it and rock and roll with that. Well, that's it for video number two in this three video series. We successfully installed a brand new power supply in the Ender 5 Plus. It is a really simple. If you did this from start to finish, it's only a maybe 15 minutes or less to do. And it's a real nice upgrade for the Ender 5 Plus. The link will be in the description below for the power supply. So you can see the model number I used and get it straight from TH3D. If you want to, I think I'm really happy with this upgrade. It was really easy to do and it's really going to help this Ender 5 Plus. Don't forget, you want to make sure your bed is level again, just like you would do in the very beginning. Make sure everything is straight because we laid that thing on its side. You never know, it'll shift. You may even want to do a manual bed leveling, even though you have to be able to touch on there just to get it really close. And then from there, you should be good to go. Well, I hope you learned something today and as always, keep printing. Hey, everybody. Thank you guys so much for watching. Don't forget to catch us live on Monday nights on our live show called Hot Makes. We do that every Monday night at 6pm and you can catch us there. Also, we're going to start putting out videos every Thursday. So stay tuned for those two. So Monday night, 6pm, we do a show called Hot Makes. Thursday, we'll put out a video for you guys.  If you haven't subscribed yet, please do that. Hit that subscribe button. And if you want to be notified when we go live on Mondays or when the videos get released on Thursdays, please hit that little bell. It's right over here somewhere. And that'll notify you whenever we go live or we put a new video out. I really appreciate you guys watching. And I hope you got some value from these videos.


ake a motion to approve The amount that was discussed after four and 65,000 For the emergency purchase of replacement Pump truck I second that Okay, motion did made and seconded Any further discussion Seeing none hearing none all those who wish to approve say hi Hi. Hi. Hi and um for the Because we're still targeting to have a special meeting I think it would be helpful if you could get an estimate Because somebody else is going to ask how much would it cost to fix that tank? No, no, I will I will have that information and To select and I can talk about it and you know, I mean I was thinking that the You know My comment before could we fix the tank and make it last five weeks? Well, even if we could make it last two years and then one of the other trucks you could extend two years You might be able to get on in every five year schedule Um So it's worth knowing I think for this truck though Because of the the demo deal I think I think maybe we should think about extending the next ones because I think if we end up We can spend 489 for the one that we're talking about in november versus 537 all right 512 remember So yeah, 512 453 you made the mistake of saying take two trucks and make one good one I think you can take two trucks and make one that might get by So gary one other question there, uh typical warranty on these things I hope I'd like to hope it was more than a year, but yeah, you know Even though sometimes we find things Um, the rescue truck as an example we've had it for four or five years We have found a couple little places where the the paint is bubbling Um, but he's going to fix it At no cost to us Yeah, so um, so that warranties is is expired, but he's He takes care of the truck city cells and he's going to fix that Uh paint job But typical warranty a year. Yes Yeah See because of my situation here with my equipment. I'm I'm squeezing these guys for three years because you know Yeah, I got enough equipment and only a certain number amount of operators and it doesn't get the Use right Okay, well, thanks for coming in here and having us out with this and thank you very much Thank you So the next item on the manager's stand Oh, thank you If we have to have a special town meeting do you want to include the roadside more on that? The last meeting we talked about I'll just figure out a way to buy it Was this specific to a mower that became available? Is that still in play or is that one gone? No, that one was what we talked about was buying the mower that we've been And It's still out there being used and it's probably going to be available in november And we the last meeting you basically said we're going to buy I think there's a general consensus that I don't think we should have a special town meeting because it's it'll be expensive and Let's just buy it and we'll tell the voters in the spring what we did and why we did it and People from the conservation commission were here. They supported buying the mower And now we have a meeting it seems Should we be upfront with the voters and tell them We want to buy this that's a lot smaller purchase than what we're doing that. Yeah I think it makes sense to me part of the point was that the um, it helps control invasives and No, no, I'm not talking about whether we should buy it what I'm asking is Hey, we're going for broke we might as well throw our jump over the cliff while we're at it till Might as well throw that Everybody's said yes Yes Um Bill can you um, maybe just to have it have it At this special meeting or email it out. Can you update this balance sheet with The um, I guess maturity dates or the dates that these loans are going to come off. Um, And also maybe include the I mean, I guess we can count it I can You know what I'm saying? So which ones are coming off which ones are coming You know like because we're adding they would be nice to know which ones are coming I can easily do that. I've got a whole different spreadsheet. I just thought just before the meeting I said I can at least show them what we owe now and what's coming off and you know We paid off You can see I knew there were a couple that I think the storm drain one is zero We paid that off in 18. We're going to pay the highway bond off this year Do you know what those were yearly? The storm drain was 20 And this the pilot ride was 10,000 a year and the other one was 20,000 years of 30k of the potential 200 Okay, is there a reason why some of these numbers are on the left and some of them are on the right? Yeah, just just Do with okay What that means is that The $75,000 number We're going to pay off 12,500 dollars this year and it's going to go to 62 five And then the next line I just wanted to be able to get it beside me and my rating is not I can't wait so small. So I just alternated sides just so Okay The important thing jane is that at 2018 We owe five million six hundred and seven thousand dollars at the end of 18 It's going to be down to five million 142. Okay We're getting there Till we borrow more Right. Yeah, I'm going to say they seem to come on faster than they come off Okay Parking ordinance enforcement Okay We've got parking ordinance. We don't have any means to enforce it. Well, should we enforce it? If so, should we put something in the budget for next year? We can talk about that very honestly I don't even know if we ought to be dealing with this you soon till after the construction's over with because right now Parking is hell no matter at pretty what, you know, so it's Difficult as it is 25 cars at 51 south main street by nine o'clock this morning. Good. Hey, that's great. Yeah Yeah, so that's a lot of should be full. That's where we want to wear this out So they're starting to get okay. They're starting to catch on and we keep can we permanently keep the flashing parking here discuss next week meeting? I think we've already been may end up with a So a quicker meeting. When do you want me to deal with this morning? It's going to be this week I can no matter where so it doesn't matter to me. Yeah, my schedule is all over the place, but I can try and make it Well, it could be early in the morning like Is it eight o'clock meeting nine o'clock meeting? I could do an eight o'clock meeting That might be my morning Yeah, morning. They're tough for me too I can do I mean, we need three to sign I mean, I'll come no matter what but Unless it's after the hour Afternoon will be best for me Thursday Yeah, you can't know Yeah, which day across from me Thursday. I can't do it on Thursday. Oh, well, maybe by the fourth I might If you were lying upon me, I would say no I could do it later Wednesday For shortly So, okay, I could do that At four Yeah, I could I'll sign up and then if four of us say yes If one of us can't make it So Wednesday at four To hand four people No, that's no good Well, it's no good because we it's not really an emergency. Can we do it over the phone? Or at least one, you know, you could do you could recess this meeting until Yeah, instead of adjourning tonight, you can just recess Yeah It'll stay warned to me Of to make Wednesday work Yeah, because you're supposed to warn of Select what meeting 48 hours in advance and we for a four o'clock Wednesday We had to post it at four o'clock four o'clock Can we set a time on Wednesday when we all email you our answers? You're gonna have to sign this meeting No, we can we can recess it till then Are you the only one that can't make it Thursday? I can make it Thursday, but probably It would be later like five I could do that's Thursday is going to be better for me Personally I can make it once there at Thursday. All right. Why don't we save Thursday at four if you can't make it? I'll try if I could get if I can get released As long as three of you get here so we don't need to recess that I Again, I don't want to take a chance And then somebody freaks out that we shouldn't have done that so Thursday at four, okay All right, and the last little note that I want to make before we adjourn is uh Sorry, oh the reason why that's on there though discuss meeting day Is because the next regularly scheduled meeting is supposed to be October 21st And I'm going to be away from here from the 19th of October until I think the 31st so You won't just wait until Do you want to meet without me is the question? I certainly don't have no problem if you meet without me, but I don't know what what there is to hash out. I mean Budget seasons right around the corner, right? So when we get but when you get back we'll Start doling into that So you want to just build over fourth the next regular schedule meeting so cancel work 21st I think that's what I'm hearing. Yeah Maybe you can email us about the issue with the flashing Traffic sign these people are concerned I'll find I'll look into that and I mean I'm assuming that if the If the state says that they'll reimburse us for it. You just want me to put it up for sure I'll just do that. You don't need to make the motion. Okay. I kept it just if you're of your request When you so I'm also looking to import a bunch of speed bumps to see where you get a few of those When you say flashing is it the one that has the speed on it? It's the What do they call it? Your speed Lashes over a certain speed The speeders down so anyway the 21st regular meeting on the fourth, right? Yeah, okay. All right and just Food for thought The other day heard on radio or tv or whatever that New York was holding a seminar on Well, they call it the Adirondack Champlain regional salt summit and over 150 businesses Were attending it to talk about what to do about reducing salt use That's impacting and I have yet to have the time to sit down on the computer and Look this up to see what took place, but I plan on doing so Everybody had what happened. They just had it. They just had it. Yep. And um so I guess Somebody asked here if any other town so I asked other town Even the bigger cities of town if anybody had policies on salt and sand spreading Got a couple responses back Um, the most interesting ones though were from towns that said They are in You know designated impaired waterways and uh What the agency of natural resources has requested of them is to Reduce or eliminate if possible sand use and use salt for Because the sand is washes into the river carries the Carries all the pathogens and all the bad stuff and sills up the The bottoms of the streams So that was from St. Albans town. So they almost use no sand They they use sand if it gets below I don't know 15 degrees or something like that when salt won't work But otherwise they're all salt No sand at all You see a lot of upstate new york a lot of towns you see signs. They're no salt zones You know, you're entering most most generally for In watersheds Exactly from st. johnsbury lindenville is You know reduced salt because of uh, but you see there's a lot in the adirondacks Anyway, I'm just saying there was there was no Really great policy that I know. I mean my discussion was about Perhaps reducing both if it's possibility I've been giving up on it. Yeah, just let you know So having said that I'd take a motion to adjourn and we can get the hell out of here All right, second All right, all those approved like Thanks, and


and Terry we have a real fine line up. There we go. Alexis Roberts of the Bahamas in one. Marissa Thomas of Guyana in two. Deccanel Thomas last year's bronze medalist of St. Kitsonivus in three. Nastatsia Fletcher of Jamaica in four. Kezra Thomas of the Bahamas. Faustist in qualifying goes in five. Tyra Fenton of Antigua and Barbuda in six. Trisha Lee Sutherland of Jamaica in seven. And Kaya Heisen of Trinidad and Tobago in lane number eight. And joining us at this time we have Alianne Pompey. Great champion from Guyana. Alianne, thanks for joining us this evening. Let me just get you on there. There we go. My absolute pleasure to be here. Especially now that the 400 meters is on the track. And before I say anything else I would like to point out that Guyana has at least one athlete in every 400 final tonight. We've noted that, Alianne, we've got you. Even if it's the first thing you said right before I said it I was going to say it again. Yes, well, well observed and certainly some fine work being done by the Guyanese team. Five finalists amongst the four finals. What's behind all that? Are they just inspired by Alianne Pompey? I don't know, but I do believe in representation. And if you see someone else doing it, especially someone that you can relate to, then it's inspiring. I know for me, June Griffith, who was our 400 meter national record holder before I started competing, was very inspirational to me. So I don't know. You'd have to ask them once they pick up their medals. We certainly will. We'll see what colors they are if they do indeed get amongst the medals. Thomas of the Bahamas, fastest in qualifying, personal best, 53-74, goals in lay number five. Fletcher of Jamaica, 53-82 in qualifying, goals in four. Those are the two favorites for this final. Stand up, stand up. 3-14 year olds, K.S. Thomas, one of the three. Fenton from Antigua and Barbira and Sutherland from Jamaica. This is, of course, the under-17 division. So you will find that there are going to be 14, 15 and 16 year olds competing on fairly even footing. But a great experience, especially for the younger ones, whether they are able to get amongst the medals or not. Green card all safe for the under-17 girls 400 final. On your marks. The big two. Fletcher of Jamaica in four. Thomas of the Bahamas in five. Deschanel Thomas of St. Kitsonivis, bronze last year, ran a season's best, 55-97 in qualifying. Off they go. Does Thomas reproduce what she delivered in qualifying this morning for the Bahamas? The Jamaican, Tricia Lee Sutherland in lane seven goes out quickly. Already makes up ground and Heisen of Trinidad and Tobago in eight. Her teammate getting into her running as well. Nastasia Fletcher, middle of the track. Deschanel Thomas also going well. The Bahamian has gone out pretty slowly here. K.S. were Thomas over the first 200 meters and moving really well. Tyra Fenton from Antigua and Barbuda. Fenton looking really good. She looked good in qualifying this morning as well. The Jamaican steps forward. That is Nastasia Fletcher. Fletcher leads it to the straight away. Fenton of Antigua and Barbuda in second. Batalon for bronze. The Bahamian comes forward. That's Thomas. But it's going to be Nastasia Fletcher. Thomas leaves it too late and Fletcher strikes gold. Surely that time cannot be correct. That was on the clock. No, that stopped a little bit earlier. That stopped about half an hour ago. Thomas timed it to perfection earlier. She struck with about 100 meters to go there. But this time Fletcher, no let up, ran all the way through the final 100 meters and did not let her foot off the gas. Your thoughts on that race? It shouldn't be said enough. This is why we run. The athletes that were the top coming in didn't necessarily aside from the winner finish that way. Great run by Antigua and Geneva. And Bahamas there, sorry. 54.32. The time for the winner. Not as fast as they ran in qualifying earlier this morning. There is Kezra Thomas fourth in the high jump. Gets the silver medal here at 400 meters. 54.69 for the Bahamian. And a well-earned bronze for Tyra Fenton of Antigua and Barbuda. Here's another look at the closing stages of this on the 17 girls. 400 final. Fenton out in the number six for Antigua and Barbuda. Knew she had to go out hard. Knew there was danger behind her. And Nastasia Fletcher you rightly pointed out. Terry easing up in qualifying this morning. No let up in the final and although Kezra Thomas finished well, she didn't finish well enough. Fletcher looking a little bit untidy in qualifying, a little bit untidy in the finals but enough to get the job done and really good. Again, we can't say it enough. Just very powerful and athlete Kezra Thomas. She's strong, well-built and she comes across very well in the last 100 meters but not enough to get over that hump. That is Nastasia Fletcher. Here we go. Nastasia Fletcher of Jamaica 54.32. Gold medal performance. Kezra Thomas of the Bahamas 54.59. And Tyra Fenton of Antigua and Barbuda 54.89 taking the bronze medal. Deschanel Thomas of St. Kitsa Nevis who had a bronze last time finishes in fourth at 56.19.


Crafting everything in Wizard101 part 10. Today we are crafting draconi onions that cost 1200 gold. You need one firecat treasure card, one glass vial and 10 hatch peppers. This recipe is obtained from talking to Dr. Peru and the pet hatchery. Firecat treasure cards can be bought from Harold Argelston in the Wizard City library and also the Bazaar. Glass vials can be bought from reagent vendors across the spiral, I prefer the one in Celestia. Hatch peppers can be obtained by offering your pets in the hatch making kiosk. This rank 8 pet snack can be crafted in the basic crafting station granting 5 will, 10 intellect and 10 power. Yummy yummy.


With record breaking travel expected over the weekend, the Minnesota Department of Transportation is reminding travelers to plan ahead and check road conditions before they go on their trips. AAA predicts one-third of Americans will travel this holiday season, which would be a record breaking 112.5 million people. Travelers heading to the Twin Cities will see detours on Interstate 35W and I-94. For us in greater Minnesota, Highway 14 and 15 in New Olm is under detour all winter long. MnDOT says everyone should allow extra time for unexpected travel delays. It's also important to be aware of snow plows on the roads. MnDOT says you should keep at least 10 car lengths between you and any snow plows while traveling. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Here everybody, Dr. O'Hare, we're going to continue on with our series of the protein synthesis inhibiting antibiotics. So just a reminder that we're going to talk about the macrolide antibiotics today, very very important ones. So they are going to impact the 50s ribosome primarily. Let me go ahead and show you. So the macrolides, they were first discovered in I believe 1952. They found them in the streptomyces, which is very common. About half the antibiotics that exist today come from that streptomyces family. But it was streptomyces erythrius, I believe, so 1952. The first one discovered was erythromycin, so we can talk about that. But the really, really important one is going to be azithromycin. But first, how they work. So these are these really large complexes, and they gum up the works basically as you're making new proteins. And certain combinations of amino acids can't actually form as long as this drug is present, which means that you're going to stop protein synthesis. Because if you can make, you know, protein synthesis will halt that there's any one combination that can't be used. So it is going to inhibit protein synthesis. These would be bacteriostatic drugs. So I talked about when it was discovered the erythromycin is an important antibiotic, but it's only useful against gram positives. It isn't as broad spectrum because it can't enter gram negative bacteria the same way that azithromycin can. So let's talk about this one because azithromycin you've probably heard of it. It's the Z-PAC, right? The advantage of azithromycin, much more broad spectrum than erythromycin, but the real advantage is it's half life. So if you compare the two, erythromycin has a half life of one and a half hours. And azithromycin or the Z-PAC formulation would be 68 hours. This means that you can take one dose a day and the Z-PAC is what, three days? So a total of three pills, whereas with other antibiotics, you're taking pills every few hours and for a much longer period of time. So azithromycin or the Z-PAC formulation, super important because of that. Every time you ask a patient to take another pill, there's the chance they're not going to take it and the longer the treatment takes, the same kind of thing. So the short, sweet treatment protocol that the Z-PAC gives us is very important. So we have a broad spectrum antibiotic. It is effective against gram negatives, unlike erythromycin. And then that sweet long half life is what gives the Z-PAC such a good advantage. All right. So those are the macrolide antibiotics, including erythromycin and azithromycin, the Z-PAC formulation. Have a wonderful day. Be blessed.


Those are medieval robots. Remember last time when I managed to dig up the HS tape of that signal intrusion? There was something in the exposition that I actually neglected to mention. The Chipmunks got a whole theatrical movie towards the end of the show's run, known as, The Chipmunk Adventure. It was about the main characters, Alvin's gang and the Chipmunks, being tricked by two German diamond smugglers into traveling around the world and doing their dirty work for them. For most of the film, they're under the impression that it's a contest, and that the winner will get $1,000 in cash. But towards the end, they discover the scheme, initiating a chase scene. The song that plays during this moment is, Diamond Dolls. You may be asking yourself why I bring up this specific song, and what it has to do with the last incident. But everyone, it happened again. It was roughly around four in the morning when I heard my doorbell ring. I was jolted awake by the initial noise, but soon fell back asleep. The next morning, I woke up bright and early, walking to the front door to collect the paper. Here I found, another VHS tape. Looks like this mysterious perpetrator took a few notes from last time, distributing stuff underground and all. The tape was covered in mold like the last one, but now also reaped of decomposition, which was strange. I saw from the last tape that the person making these wasn't the most hygienic though, so I just put the tape in my media player. It booted up with a scene from the chipmunk adventure, the part where the two groups have a battle of the bends in the Greek ruins. But right in the middle of the song, the girls of rock and roll, the scene is, well, off. When it showed Brittany, Jeanette and Eleanor ascending a staircase, Jeanette suddenly looks behind her, breathing heavily. Text appeared over a shot of her eyes widening. She was merely an animal to be hunted. There was then live action footage of someone running through the woods, tripping repeatedly over their own feet. As they fell to the ground, a pair of pinkrimmed glasses landed in what was either snow or dirt, unsaturated due to the camera's low quality. The audio had been silent for a little while, but it suddenly cut back on with a voice, sounding like a teenage boy going through a voice crack and a grown man all at once, yelling something to her that I couldn't decide for. Text appeared yet again. You know what I want Simon. Another cut in the film, Jeanette danced around, the animation was superimposed over a photo of an empty gray-scale bedroom. She didn't seem happy about singing or dancing however, as her face was emotionless, I suggesting that she had been crying for a while due to their redness. We don't have to do what you tell us to do no more. You get what you need and you don't want it anymore. We don't cry now, we don't know how. The vocals were isolated and sounded almost desperate at some points, like Roger Waters during the end of Hey You. It was like the voice actress was about to have a panic attack as she sung. Then Jeanette paused, standing still. The text returned, this time with a heavily distorted, ately supernatural narrator. So, you draw them as shitmunks to cope? Yes, sir. I do. The teenager-like voice returned. The footage reverted to live action and cut to a man loosely resembling Simon from the original tape, this time way more disheveled, with longer hair and glasses that made it impossible to see his eyes. He quietly sung the bridge of Diamond Dolls to himself. Silver, platinum. I pass on them. You can have them. I know what I want. The young man suddenly turned towards the viewer, or myself. I could see his eyes. They were white, pure white. Tear-stained, lost looking, like a doll left in the rain by their child. He's the one on the run. The boy with the Diamond Dolls. I loved her. Why did she leave me behind? Why did she leave me to rot in the unforgiving Wisconsin snow? Why did she leave me to fend for myself? The oldest gets all the praise, the youngest gets all the love, but what do I get? I got intelligence, but no praise. Sympathy, but no love. I'm just another case in the files, another kept gone missing. My name is Larry Lawson. But you can call me Simon. Mechanical worrying interrupted him as the tape and wound in the player, seeming to self-destruct. Right at the end though, there was footage of the woods yet again. I saw Larry, or shall I say, Simon, with someone standing behind him. Their hands were white like gloves. They'd come to snuff all who he bonded with, everyone he knows. And I may be next.


Welcome. Yeah. Hello and welcome. We are having a round of lightning talks, four talks after one each other. We are starting with a shorter, faster way to performance, making the cache run in shorter than 12 parsecs with faster in triple eight. I'm Fabian Franz and this is Doc Velco, and here we start. This is us. This talk got condensed down from 45 minutes to an hour to 15 minutes, so that's why we're gonna be rushing through a little. We cut a lot of stuff, but it's still got a lot of slides to go through. So this is us. Let's talk about varnish real quick first though. So varnish is a HTTP reverse proxy cache, which breaks down in three things. HTTP, we all know. We love it, we use it, et cetera. But the reverse proxy is, it means that it sits in front of a web server. And the cache part is, I hope you guys are all familiar with that, is new to Drupal 8 with the full page cache internally. Varnish is like that. Why do people use it? It's fast, it's flexible. It allows you to do certain things like this. This is a really quick thing. If the URL of the request starts with slash search, then lowercase it. It's just a little programming language that you have to configure varnish, called VCL, the varnish configuration language. And it allows you to do a whole lot of simple things like this or slightly more complex things like this. This is to deal with origin and cores and all that sort of thing. It looks at what the origin is, saves it, looks at what it is, and then depending on whether or not it's the right origin it sets the course headers, et cetera, et cetera. This is just a quick example of what the power of VCL can do for you. The advantage of this, Paul Henning Kamp, by the way, is the original author of Varnish and he still runs the project. It's sort of like a printing press for books, but for websites. So the main problem with Drupal performance and the reason why the page cache was introduced in Drupal 8 is that if you have to rebuild the page every time you have to bootstrap, it takes a lot of time. Was it 100 plus milliseconds? Just for a single request. So if you don't have to do that, if you don't have to write a page of every book by hand, but you can just print it much faster. So that's what varnish does for websites. The problem is however, if you go global, say you have a newspaper instead of a book, you have to start doing this.  It costs a lot of money, it takes a lot of time. It delays the newspaper getting to other countries. So, you know, not ideal. Instead of an airplane though, you could also use one of these. Who's familiar with this ship? It's the Millennium Falcon, don't you know? It did the Kessel Run in less than 12 parsecs. It took a chunk. Exactly. The thing is though, Lucas got a little flack for this because parsec is a unit of distance, not time, et cetera. And then he went on to explain on the blue right, like, oh no, no, no, no, no. The thing is, Han Solo was a smuggler and the Kessel Run was, you know, not a straight line. And you could take shortcuts. And he did it with a really dangerous shortcut and that's why it was less than 12 parsecs. Shortcuts, very important. That's actually, you know, the problem with web performance on a global scale is that we're bound by the speed of light. This thing wasn't, but we are. The speed of light threw fiber around the world. So, you can't really cut down latency with any sort of trick other than making the path shorter. Well, that's what we did at Fastly. We put the printing presses all around the world. So, Drupal 8 has a built-in page cache. Fun. We have caches all around the world that you can then link to Drupal. Fabian's gonna get into the details of that. We have some more features, but the key one is key-based curging. Gonna go into that real quick. Basically, what you do is if you send a response from your origin server to the CDN, you can put a header in there with keys, circuit keys, and those objects that we have in our cache are then tagged with those keys. You do then a purge command based on that key. All objects, no matter what object it is, if it has that key on it, it's purged. Looks a little like this. This is the headers of two different responses. They're both the same article. I had just grabbed some random values. You can see the article ID here, but they have two different templates. Now, normally, if they have different URLs, like one could be for mobile, one could be the regular site, so m.example.com and www.example.com. And then you would have to, if you wanted to purge them both, you would normally have to send two purge commands, et cetera, et cetera. If you just send one purge for the article in 1938, both are wiped from the cache, and if users then request that page, fresh copy is grabbed from the origin. However, if you make a change to the template of the mobile site, at this case, all you have to do is purge template three. Boom. Everything related to that template is gone from all the caches globally. You're done. So, but what about Drupal? In Drupal, what we have to do in Drupal 7, our support was pretty basic and Fastly mostly works for the expire module in expiring that. And then Dries made this blog post to making Drupal 8 fly. She's, I really have been trying to do, women, me to really make Drupal so fast, where we have this much more precise cache invalidation using cache tags, which is the same as surrogate keys. So, and we have this cache tags, and because they are surrogate keys, the Fastly module kind of only has to do, and that's why we can remove so much stuff when it was ported to Drupal 8. It really only has to support those translation from cache keys to surrogate keys and shortening them a little because Fastly has a header limit of 16 kb, and we are done. So, this is now one of the most simple, easy modules put in your API key, getting four quick dashboard, but in reality, it's one even subscriber, and you're done. Okay, so you have very good fetching support and the Fastly plug-ins, and it synergizes incredibly well. But there's more in that supporting cache cons. I'm gonna go a little more into the detail there, and so the common scenario we usually have is we have a web server, we have varnish, we have a web server, and it's happy because it doesn't get much blood on it. And with the CDN, it looks a little different because we have, again, two happy web servers, the varnish, and we have all those CDNs around the world which take the majority of the traffic, but then one day someone had a very, very bad idea. They put a product into a shopping cart, and then this looked like this. The side is slow, the web server runs away screaming, and it's really unhappy, so that's not a good thing. So my solution I've been working on, together with BigPipe and the other thing, this can be the other side of the Drupal caching system, is a 8X prototype I've done, and the idea is we can authenticate the user with a varnish, we can store a mapping of the session ID in the cache context because we have a cache hierarchy, and then we are gonna have a happy web server, obviously. So that sounds pretty complicated, but overall it's not too much, because the nice thing is because Drupal 8 was designed in a special way, there will be just one VCL file to rule them all for all authenticated user caching. Can a no configuration needed plug-in be happy? Out of the box in Drupal 8, and obviously will work with Fastly too. So the vision here is to really be able to run 80 to 90% of the read-only authenticated traffic completely from varnish into CDN too. So how does it work in a little more detail? We have like a shopping cart and it's user cached, and we have a normal block which is per permissions, and the main page content which obviously we all cached, and then what we're doing is we're just putting a placeholder in, and while in Drupal we are putting that very late in that, here we are putting an ESI placeholder, then we are putting a cache text max age, when to invalidate, that we have all available as information, we have the cache context, what to vary on, which is very similar to the HP header, and the variant example very except, and placeholders make all of that possible, and Drupal has auto place holding, which means it can detect what can't be cached, it can detect what's high frequency cache context, and it can automatically ESI those as well, and we also have those lazy builders. So one static VCL for our cases, enable ESI module, combine those placeholder strategies strategically, the web server is happy, we are happy too, here's some resources for you, and remember, as fast as in Drupal 8, you can also make some cached run in less than 12 parsec today. So questions, we have one question, give some mic if someone wants. A few more, we have this, but apparently there can be more than one. Good questions now. Deep, deep, deep, deep, deep, deep, deep, deep, deep. All right. Okay, if there's no questions, then I think we continue to the next session. You put your full screen, like enter full screen mode, try it? Oh yeah, that's fine, cool. All right, hi everyone. Today I'm going to talk to you about the largest Drupal 8 websites on Earth, and how you also can do it. I'm not the one who said that the website I'm going to talk about are actually the largest. The one who said that, I think you have all heard about the guy, he said that Lothon, which is a Swiss media news website, probably is the largest websites built with Drupal 8. This is this website you can check online, pretty big websites in the Switzerland. But I'm also going to talk about another website which is called Swedish Fights, built by another company, which is also a very big website in the news industry in Switzerland, and another one called Willis Arbota, also in Switzerland. Why am I talking about those three websites? Because those three websites have a very strong particularity. What makes them so special? They have all been launched before Drupal 8 was actually released. So those major huge websites have all been built and launched before Drupal 8 was released, as a stable release. I'm actually pretty cool. But also they are built out of the same distribution, the NPA distribution. And they are also all hosted on Platform.sh, which is a hosting solution that I'm working with.  You have three competitors, big competitors in the same country doing the same thing, working in the same industry, and they all launched their website with Drupal 8, they all launched their website before Drupal 8 was released, and they are also all using the same distribution for building their websites. And the only solution that was available for them was actually to work together to solve the same issues they were all having. They all have the same issue. They all need to fix the same problem and to answer the same questions. So they decided to actually work together to resolve those problems. And that's how NPA came out. NPA is a Drupal 8 distribution that I'm going to really present now. And the two actual founders of that distribution was a company called SoMedia, very big, big media agency, and Gassman Media. So, I think SoMedia is behind Swedishwise, but they have a lot of website that they are all migrating using that distribution. And Gassmedia built the third one that I presented, release our bot. And they are also all migrating all their website with Drupal 8, with that distribution. And who built that distribution? It's a company in Switzerland called MD System that you might have heard about. So you have those founders that put a lot of money together to build that distribution. You have MD System building that distribution. And now you also have Lothan, who is using that distribution. What is that distribution? It's a really fully functional news portal distribution, fully built with Drupal 8. Some features that I'm highlighting here, like publishing all the community, social management, third party integration with payment getaway. You can do multi-platform, multi-channel. It's built with best practice, fully test coverage. It took one year of investment for MD System to actually build that distribution. They have contributed 42 modules. They have ported a lot of modules to Drupal 8 in order for that distribution to be built. They have packaged 15 custom modules and features that are inside the distribution.  I'm sure you've heard about Behat. It's a big investment.  This thing with the distribution, and you're going to tell me that it's a bit weird, if you want to use it, you have to pay a buy-in fee. But you're going to tell me that license with Drupal is GPL, so I get to also give the source code with the distribution. That's where the fair partnership policy come into account. If you put a lot of money to actually use the distribution for all your websites, you're not going to automatically share it for free. You're going to also be able to resell it. So if you want to actually use that distribution or at least test the distribution, you can either come to our booth at Platform.sh and we're going to be able to put you in contact or you can directly contact MD System and they're going to figure that out for you. What are the tools that they're actually using for those big websites? So the first one, of course, is the CMS. It's Drupal 8. Why have they chosen Drupal 8? For some specific obvious reason, like the WYSIWYG, the new inline editing, which is very important for all their, how do you call that, marketing people or the people writing the news, the reporters. But also what they just talked about with Fastly, the new caching system for Drupal 8 and the services integration that were made super easy with Drupal 8. The new caching system is super important for them and I'm going to talk about Fastly right now. No, into slide, okay. We're going to come back to Fastly. Also the hosting, they have chosen Platform.sh for all of their, to host all of their website. One of the big reason was the high availability. They wanted to be able to deploy major feature all the time without putting the site down. That's what we propose with Platform.sh. We have triple redundancy for all of your service, which means like if we do, if you want to do a down upgrade, upsize or downsize of your service, you're expecting some big traffic because you're on TV or something or you have breaking news, you want to be able to very quickly without any downtime, upsize the resources that are serving your website. And also it's 100% Git-based development workflow so you can use multiple applications inside the same repo and some modules that's what they're using. And we also had very early support for Drupal 8 which was important also for them. The CDN, that's a big coincidence that they just talked about Fastly. You already know everything about it. I still want to mention that it's a pretty cool solution because of the instant purging and propagation of updates. Not sure if you've ever used the CDN. I'm not going to give any name, but you know that if you do a change in the configuration, it can take hours to actually see the change in some node somewhere. And if you're testing your configuration or if you've done a mistake, you don't want to wait four more hours to actually get that fixed, right? And instant purging is pretty interesting. And also the key-based purging that they just presented. So the reflection is that... And I think that's my last slide. Yeah, the reflection is behind that. Is that a good idea to actually build a distribution so that it can serve multiple purpose and it can serve all your clients' needs. If you have multiple projects, that might be a good idea and Drupal 8 makes it easy now. Thank you very much. That's a bit less than 50 minutes. If you have any question, I'm more than happy to answer them. Do you use features as... I think they use only CMI, but since they sent me the number of features, they might have some features. But I'd say it's only CMI, but you can check. Any other question? All right, thank you very much. I think that's the next one. That was one question I had too, if you want to answer it real quick. So what's the story behind the astronaut? Our motto is now deploy to the moon. We are behind Platform.sh and we think we can deploy your application everywhere and the next logical step would be to deploy your application to the moon. So we are already working on that. The moon cache context, that's a good idea. I think it's gonna be hard to get instant invalidation. I don't know what the round trips are all the way to the moon, but that one's kind of far. All right, I think we've been doing a blistering pace here so far. We've had at least one talk that was condensed down from 45 minutes. So this is probably the best value per minute of any session, I would say, because we're already at over one hour. So in effective time. So my name is Dan Keebrick. I'm gonna be talking about distributed tracing for performance monitoring in Drupal-based applications. I did notice a trend in the first two talks. I'm just gonna get this out of the way at the beginning. Disappointingly, there are no references to space in this entire talk. And in fact, the outline is here and that kind of proves that. I'm going to introduce and motivate distributed tracing. Explain what it is and why I started to care about it a couple of years ago and why you might as well. Talk about some different approaches to it. I think a lot of this will be motivated by some of the work that I've been doing for the last couple of years with Appnetta, but there are open-source tools and different types of approaches for it and it's pretty interesting. And then I'll talk about some of the challenges that we face when we try to introspect applications this way and some future corrections that it might head. So where this journey started for me was in 2008. I was working for a website, a company called AmyStreet.com. I mean, you probably haven't heard of them because they were competing with the iTunes store. And the goal was to sell independent music online with demand-based pricing. And this was kind of a cool idea that if people hadn't really downloaded something much, if it wasn't that popular, it would be cheaper, which would incentivize you to buy it. And what this meant, it turns out is you need all these kind of crazy features to support that, which I'll talk about in a second. AmyStreet eventually became SongZo, which became Google Play Music. So there's maybe some small part of this still surviving, but I think it's probably changed quite a bit since then. And I had a really good time working there because all the people that I worked with were smarter than me and very adventurous. And so we built a pretty cool application. It started as a PHP-based, kind of monolithic web application, LAMPstack, like you do. And then pretty soon we wanted to have Search. And so Search, you don't want to do full-text search in the database, so you use something Lucene-based, now say Solar. Back then it was something that was Lucene-based that one of the engineers on the team had made. The dynamic pricing, that's an interesting one because you kind of want to maintain state based on what pages people have seen. So let's say that a new album drops on Tuesday, like they do, and you go there and you see a price and it says, this is only gonna be 10 cents per track. And so you listen to a couple of the tracks and you hit buy, and it says, oh, you got charged a dollar a track. And what, that's not fair. Well, what happened was during the time that you were listening to, deciding whether you wanted to buy that album, the prices went up, and so sorry, it's stateless, the web stateless. Okay, so what we need is a pricing service that gives you a little ticket based on what you've seen and remembers that you've seen that and keeps it around for a certain amount of time, and you could probably do this in a relational database. Again, we had some, you know, pretty, I had some really smart and interesting coworkers, and so this was written in Erlang using the amnesia, kind of in memory database, and again, communicating over Facebook thrift, now Apache thrift, you know, to talk between languages. And so pretty soon there was just more and more cool services that built up around PHP, and so it was like this kind of whole tree of things, and I actually have a little map here. And so this was also heavily influenced by like the live journal stacks, so we had Brad Fitz stuff, so we were running PerlBowl and Memcache, and there was actually MogailFS to serve all the MP3s and stuff. And so we had this kind of topology that looked like this, and it was really fun to work on. I mean, you know, to get paid to write Erlang code, that's hard to do. And so, at least for consumer web. And so, I told you this was like 2008 timeframe, and it's been almost a decade, and so you might wonder like, you know, why does he remember this so well? That's kind of creepy, and my memory is actually not that good. The answer is PTSD. So I got a promotion, what I considered an awesome promotion to the ops team while I worked there. And what I started to realize is actually like some of these awesome ideas that we had were like a little bit weird to have to maintain. And we had an actual colo, and it was much cleaner than this, but that's not how it felt when there was a problem because this is what we had. So we weren't flying blind.  Now it gives us for alerting. Based on our thrift services, we started to realize, and this is a problem I'll talk about more in a second, that when things can go wrong and all these different processes, it's good to have a way to query their health. And so we make a health endpoint and then we made a webpage that would query all the different health endpoints and then you could have Nagios hit that and grab for whether the text looked good or bad. And there were of course lots of logs and every process on every machine had logs. And so this is kind of what the debug workflow looked like. And the story version of it is say, Elliot, one of the non-technical founders of the company runs into the room and he says, guys, the website's really slow or it's white-screening. Okay, Elliot, do you have any other clues? Well, it happens one in six times. It's probably one of the app servers. Oh, it happens one in two times. It's probably one of the databases or one of the pricing servers. So like, that's not really good. If that doesn't immediately tip you off or to investigate that, you tail the logs of every service and every machine. So you didn't really have Splunk. There weren't all these kind of cloud logging things. And so you would have a bash script that would tail all these logs in parallel. Maybe you wanna check the database process list as the agent and poke around. For slow stuff in particular, this was really hard to track down though because maybe it was something about like you're looping over a certain query or a query's taking a long time, but not long enough that it's running for like 60 seconds and you catch it. And so you're actually gonna insert some logging based on where you think it is and do a new release. And it takes like a full day to figure out what's going on. And eventually you're just Googling it. And so this worked. It managed to solve the problems, but it wasn't like a super efficient use of time and we would keep adding more metrics and stuff around common problems. And I had some co-workers leave and one of them called me up one day and he said, I was looking at this cool academic project called Xtrace and I think we could use it to solve some of the problems that we had at Amy Street. And okay, well, what's Xtrace? Well, the idea is if you could just follow all those requests through the application and see what they were doing in each tier, then you could kind of take that data and it's more structured than logs because you actually build a map from process to process and if there's concurrency, you'll send a unique identifier through and you'll just associate that with every little bit of data you gather. And I said, well, yeah, I think if we got traces of a lot, a lot of requests and then start mining it for data, we could probably figure out what was going on, but that sounds like a lot of work because if you think about what you'd want, let's imagine that each one of these kind of red dots is like an instrumentation point, say, we'd wanna see when the request comes into our application and maybe even in Perlbell in our previous example or Nginx, maybe like people would use today. And then when it gets hand off to the application, then maybe some stuff inside the application code and then whenever it makes a call out to an external service and this is gonna be a lot of work because we're gonna have to add all these instrumentation points, so the approach we ended up taking was basically that and I'll talk a little bit more about how it works. I wanna actually show some examples first to make this a little bit more concrete and so what I wanna show is actually based on kind of what we've done at Appnetta and also a TraceView Drupal module that was written by some people that use our software who wanted to kind of take it and add more data that's specific to say different hooks in Drupal 7 and we actually have a Drupal 8 port of this in beta right now that starts looking at some of that stuff. I don't know if this is gonna work, if not I took some screenshots of it but if the internet is not like super bad then we can actually just, it's always harder to type than someone's watching. So I thought maybe we could just walk through one of these and look at like an actual trace and just to kind of map it to what we just saw behind the scenes we're collecting all these different events and they're kind of in like a graph so we attach this unique identifier at the top level and we propagate it around and we have all these events that we generated and in this case it's pretty linear. There isn't kind of any fan out or anything crazy going on but what we do have here is a web request that's being handled by a demo Drupal 8 application that we have set up and it's pretty simple request.  We've got some kind of summary notes about it but the interesting thing is the path of that request through the application because this took a second and a half and I'm not super impressed with that performance so I wondered what's it doing during that time and from left to right we've got the timeline of the request and from top to bottom that's kind of where we were in the execution so the critical path is really this thing along the bottom. If you are used to looking at front end web performance and like a waterfall chart then we might think about it more this way and so we've got kind of, we spent a lot of time in HTTP kernel master request, fair amount of time in rendering the views themselves so we'll dig into that. This view is a little bit more compact so it's nicer for kind of projecting here and if we're just stepping through this the request starts off being handled by the Apache web server here. It's not doing much work, it's just passing that request along basically proxying it through to PHP which is where we actually start to get into stuff we probably care about. We've actually also done our first distributed system thing which is potentially go from process to process and as we start to walk through this the application code begins to, there's a spaceship outside, that's the finale. So the first kind of interesting thing that we're doing here in our bootstrapping is set names UTF-8, that's actually not that interesting and then the second thing is not that interesting either so we've got these queries very fast like 200 microsecond queries, they're running against the database and if we see where this is coming from we're still in the bootstrap and zooming out a little bit we see there actually is maybe a little bit less than 100 milliseconds of bootstrapping stuff before we actually get into the master request handling stuff and start running this and I got the five minute warning so we'll keep a pretty blistering pace. A lot of this request handling latency actually happens inside rendering our views here and in particular we can see maybe what different twig templates are taking a long time and what kind of views, subcomponents, those are pulling out as well what database queries get involved in this particular theme so pulling the settings for that. The nice thing about this second and a half page load by the way is hopefully we're running varnish in front of it or a CDN even on top of that so that we have this kind of like Russian nesting dolls type setup so that we never have to actually generate these pages but when we do we want them to be very performant so they scale well and so being able to break this down is kind of interesting. Here's something else I saw that I thought was super weird we've got some latency in Apache after PHP is done like that's kind of weird. I think what it is in this case the we're generating traffic from an Australian data center to request pages here is that could actually just be downloading our kind of our big heavy page here for that last 100 milliseconds or so across that internet we can't break the speed of light. Okay, so I'm gonna go back to the slides now and I also had a Drupal 7 request here it's pretty similar we're seeing bootstrapping in this case there's something super weird which is we're using Memcache but Memcache is being super slow when we talk to it so that's not the most exciting thing in the world to see this is Drupal 7 so we're seeing kind of different structure as far as how the CMS is evaluating different parts of it it's actually using views as well. Now this was like what I would call minimally distributed, right? A LAMPstack is basically the smallest level of actually interactive application we have on the internet there's a lot of static sites now but I'm not counting those when we start to get into a more complex application this is again getting back to my Amy Street use case then it becomes a little bit more compelling and so to give an example of that let's say that I'm making a curl call to this particular service and maybe that's like some payment processor and in that case if it takes a second like this then I just say okay well I'll try to not do that too often or that's the cost of making money but maybe it's to an internal service tier or a search service and so I might actually want to be able to figure out what happened during the processing of that request and so with this review tracing I can actually kind of jump across the wire there and see what's going on there now while we were working on this just because we happen to read this paper we weren't the only ones Google was working on it because they're ahead of everybody on everything Twitter ended up open sourcing something that they use for this called Twitter Zipkin Etsy talked about doing something similar to this in 2014 right now I'm working on a project with some people called Open Tracing that's kind of starting to plant the seeds for this there's some commercial offerings like my company as well as some that are for application performance monitoring maybe not as oriented around distributed I wanted to talk through some of the really interesting challenges related to this but I don't want to run over so instead the slides for this will be available and I will be around afterwards in case anybody wants to talk so thank you I found the thank you slide and I appreciate it any questions? Thanks for coming out I'm going to be talking about the risks of going headless a lot of people have done a lot of really technical sessions about this subject so if you're interested in the technical details of going headless this isn't the talk for you I'm going to be talking from my perspective so about me that's what I look like my name is Mark Farie I'm the director of engineering at chapter three so I managed a lot of developers I've got my fingers in every one of our projects and so I'm going to be talking about what I've seen go well and what I've seen go wrong and how we try to manage that with a couple of headless projects that we've worked on and if you want to talk to me MRF on pretty much everything where you can find me so a little bit of background high-level overview of what headless means thank you Dries for preparing this diagram for me so this does a really good job of explaining what is called headless or decoupled and sort of what that relationship is to your Drupal site so if you look at this diagram you've got your traditional Drupal site on the left hand side and that means Drupal going all the way back to I don't know Drupal 4 is when I got involved and it looked just like this then and Drupal 8 if you use it out of the box is also exactly the same and what this means is that your theme layer is tightly coupled to your system like everything that Drupal does assumes the theme layer is going to be there and you're relying on that theme layer and so what that means is you need to be a Drupal expert in order to wrangle this whole system so if you want to work in the front end you need to know a lot about what the back end's doing it and why it's doing it I've found the best front end developers in Drupal also are really good site builders they know how to build views they understand the data structures and they understand why Drupal is doing what it is on the theme layer like sometimes that theme layer can be a little bit impenetrable it's like an area of expertise so one solution that people come up to this they've seen this as a problem it's hard for Drupal if you have to be such an expert in order to make it look beautiful so they've decided to hack off the entire visual side of the site and call it headless or decoupled and so the example on the right is the front end no longer has any tight relationship to the back end your front end is just going to make API calls or use some other method to pull the data it needs out of Drupal and so the reason this is called managing the risks of headless is all of a sudden you've made your project a lot more complex so step one is distributed teams so what we've just said is that our Drupal team doesn't actually need to build the whole site we've just introduced the possibility of bringing in an outside contractor or a team of Angular devs that happens to work at the same company to build the entire front end they probably don't know anything about Drupal and they might not have any desire to learn anything about Drupal so all of a sudden from my perspective it's we've introduced a potential communication problem that we need them to clearly describe what they want how they want it formed how they want it structured and they need to ask those questions in a way that makes sense to a Drupal developer even if the data structures they're describing don't really map well onto Drupal so we all of a sudden have these difficult conversations that we've inserted into the equation which is why can't you expose it to me this way it's like well it's hard or why is it hard you have to explain two thirds of Drupal in order to explain why it's hard so right there we just introduced a risk for a project because clients and end users they care about how it works and how it functions on the front end and they don't really care that this layer of complexity is there or not like all they want is a fast, beautiful experience on the front end so you should think about what your team looks like a lot of the big success stories I've seen and I've heard from are where you get either ex-Drupal developers that have learned a framework and have done the front end or you have people on the same team so they're in the same office they can throw a pencil across the room when they have a question that seems to sort this out but I've seen when you have distributed teams or teams from two different companies that this can get really tricky really fast duplicate functionality so made this one myself I'm not the best at building graphs as you can tell so there's a lot of things Drupal can do and there's a lot of things your front end framework can do and what you realize is both systems are actually doing the same things Drupal has a templating engine Drupal has in Drupal 8 a really awesome cache layer Drupal has a lot of things that your front end framework of choice is also going to have so you really need to start asking yourself is why am I not using native Drupal like what's the business need what's the technical need like what is my strong motivation for this project and you know there's a lot of reasons you would want to go headless you know maybe you're sending the API out to four different sources like a really good way to test an API you know that you're building is try to build the entire site off of that API because then if somebody's building an iPhone app off of it if you're distributing that API for external devs to use you know it's really solid because it builds your entire front end so it has everything there that anybody would possibly need so that's a really good reason to go headless maybe it is the structure of your existing team maybe you don't want to hire front end Drupal devs maybe you don't have any front end Drupal devs you just got one Drupal backend guide that doesn't know CSS from a hole in the wall so you know he wants to still build the backend in Drupal you know and he can say I'll get the Angular team anything they need they just need to let me know and I'll make it happen so Drupal still gets to be part of the equation but you really if you're a Drupal shop and you're looking at a headless project you really need to think like what benefit is this bringing my client you know like what are they getting from chopping up the head and we just added a new layer of abstraction I was going into that a little bit in the previous you know examples but the worst kind of abstraction is unnecessary abstraction so you know right here we just created a layer where we actually have to think about everything we're serving up and how we're serving it up did we think about caching those requests you know we just heard a lot about Fastly and these distributed architectures like what happens to my front end when Drupal can't serve my request fast enough like all of a sudden Drupal is slowing down my awesome Node.js front end because the request aren't getting served fast enough so your server architecture just got more complicated I hope you have a systems team and your whole project just got a lot more complicated you also introduced a single point of failure so this graphic is getting a lot of use in this presentation so right here this gap can be the size of the Grand Canyon so you introduce communication issues you introduced a whole spec that needs to be written which is what needs to be exposed out of Drupal to this other application D8 makes some assumptions there there's a couple of different modules you can use for D7 that do this really well but they all make their own set of assumptions and those may be entirely wildly different than what your front end team is expecting to see so are you prepared to actually go and build exactly what they want are you prepared to go negotiate with them to convince them that what Drupal sends out by default is what they actually need so you've got a new single point of failure and if that caching layer goes down you might stop serving content to your front end like and that's another reason why you want to avoid a single point of failure so there's been a lot said about Headless I wrote a blog post about this so decapitated Drupal you just need to enter that into Google and I'm number one for that I feel like there are really good, really strong reasons why you would want to build a Headless site but I feel like the main motivation I see for a lot of Headless projects is shiny it's like I want to learn a Node.js framework my team wants to learn a Node.js framework and this is a way to have your cake and eat it too I can still build Drupal and I can introduce Node.js like that should be the furthest from your mind and from your team's mind in terms of why you're building a Headless project you need to have a real business driver a real strong need in your organization for why this thing needs to be lopped off because all those risks you just introduced are gonna cause pain down the road Dries wrote a much more measured approach I think he's a little bit more excited about Headless projects than I am so if you want sort of a more balanced perspective like his blog post goes into a lot of detail and he has a whole series of blog posts where he was talking about his perspective on Headless I would also like anything written by Four Kitchens they have a really good team like they have Angular devs that work there and they're longtime Drupal guys as well so they have a lot of really good resources on how to do Headless right and how to avoid some of these pitfalls that you're gonna definitely run across so that's it for me thanks for coming out anybody have any questions? Oh, all right come grab me at the booth if you have any questions later Yeah and just one more thing John Alban is actually currently addressing this need kind of that you need to learn Drupal themes and the whole theme component system that we're building at the moment that will allow also kind of having a team that's not knowing the Drupal theme layer but a different theme layer to build themes without having to deal with all that stuff that's so Drupal specific so soon hopefully there will be one less reason to go Headless


A lot of questions come up about Wi-Fi performance and speed, and we know that what's on the box versus what you get can vary a lot, especially when it comes to Wi-Fi. And of course, from a marketing standpoint, we want to put the fastest potential that any device will offer, versus the reality of what that device will offer. Obviously, there can be some discrepancies. Wi-Fi is subject to a lot of discrepancies. And I wanted to cover a couple things real quick about Wi-Fi, and I'm using a unified device, but this applies to other devices as well. And that comes to the channel width scenarios. And probably you're asking, well, don't I just set it to the widest channel width possible so I get the most speed possible, and that'll make all my fast problems go away, and it's only for some legacy reason that they don't have all the channels? No. Unfortunately, it's a little bit more complicated than that. I won't read you the article, but I found this clever right up from Seven Signals, the Wi-Fi performance company. I actually hadn't heard of them before I started Googling this so I could get a more concise answer. But it's what nobody's telling you about 80 megahertz and 160 megahertz channel bonding. Now to go back a little bit of a history, these are your channels, and they have a few graphs on here to show you the different channel options. So this is your 20, your 40, and your 80, which you're actually doing because the Wi-Fi is split up into 20 megahertz slices, which equates to being a channel. You bond those channels together to create more speed. Makes sense. The problem is because of the way Wi-Fi is as a standard, it only allows for so many channels. So when you start using more of these channels, and as in bonding them together, you have less channel options. So for example, if there's Wi-Fi interference in one of those channels, you would simply move to another channel. When you bond the channels together, that becomes more difficult because there's less room to maneuver if there's some type of interference in between. Now this may not at all apply to your house. So if you're in a small area, single Wi-Fi deployment, there's not any real interference because it's just you. You have a clear line of sight of the device. So you're going to get the max performance out of there and having the full 80 should be perfectly fine for you. But if you have a neighbor on the other side of the wall with their 5 gigahertz pushing at the same channel, well, now you have that interference problem. And if you have the channels bonded, but some of the channels are being knocked out by interference, you're going to get very low performance. This is why Wi-Fi performance is so tricky. It's also tricky because, for example, I have my phone pulled up here so you can see it has good Wi-Fi performance. You can see it's connected at a Wi-Fi speed of 866. We have it at the full channel width of 80 megahertz. But if any other Wi-Fi is turned on in the office, it will still connect at that speed, but the interference will cause it to have slower overall performance. The other thing you're going to note, so the phone is actually right here. I got it just out of the camera. Just by me holding the phone, you can see it went down. And then by me moving the phone to my pocket, just that far distance. So it's just out of the camera, sitting down further, we lose that much more signal. And that is the tricky part of Wi-Fi performance. Now Unify also has a tool here to show your RF environment. So here is the 2G environment versus the 5G environment. And this is what I'm talking about with the channels. So here's all the different channel options, but when you start bonding them, here's the channel options for 40, and here's the channel options for 80. So there's just many fewer channels because you're bonding all these channels together. That's why this chart looks like this. Now I'm not going to run a scan right now. I did earlier and you can do this on a lot of the Unify, newer Unify devices so you can look through the tool and figure out what's interfering. And if you want, you can just force the channel in because you know what the channel is at an adjacent access point. Let's do a couple tests real quick here and show the speed difference between the different channel options. So right here is the radios. We have them at the 2.4, which we're not using, but I did set it to 40. And then we have here set at 80, and we're connected right now at the 5 GHz. We're going to use iPerf on my phone and iPerf on my computer. So I have iPerf set up and listening. And Magic iPerf is a free tool that you can get in the Android Store. Maybe it's for iPhone as well. I don't know. We'll go ahead and do a speed test here. And I have the phone sitting on a stand with my hands off of it so I can get the most consistent numbers possible. So about 272. We'll run this again. Now to highlight what a difference holding the phone makes, now I'm going to just hold the phone and do the same test. And you can see how much it has dropped. And all's I'm doing is holding it in my hand. I'm putting both hands on it because I don't know where the, I think the antenna is at the top on the Android. So actually I'll just hold it at the top and do one more test. Yeah, the antenna is at the top. So putting my hand over the antenna, it's slower. I put it at the bottom and it got that much faster. So these little tiny differences is why it's so hard to pinpoint Wi-Fi. So I'm going to put it back in the stand here where we know we were getting about 277 without my hands on it. And we're going to switch the width of the channel back down. So now we're not going to bond the channels anymore. Apply and we'll see it provisioning. It takes a second here. My phone will actually drop and reconnect. It provisions really fast when you change the bonding of the channels. And the phone goes in and out really quick when this happens. All right, it's reconnected. And we'll go ahead and run the test again. So we're seeing about 122 versus the 272 we were getting before. So it's like 127 now without the channels bonded. So one more test. We'll do it in my hand again and hold it like this. And you can see it coming all the way down. Not quite as much, but it is dropping down to 74, depending on where I move my hand here. So if I move it, make sure it's right over it. Hit it again. Yeah, it is moving it that little bit closer to me. And away you go, you can see how much we lost in there. So the lost is more of a percentage because you still are going to lose. So that type of interference, as in my hand in a way, doesn't really affect the channel bonding. Channel bondings only really affect it by other Wi-Fi devices in that channel range of the bonded channels. So hopefully this clears that up. This is a question people always want to know, why isn't it set that way? Or should I set it that way? Or what is the trade off for loss? So short answer is, as long as you don't have it in your appearance, and there's no other APs in there, for example, if you're at your home, you have line of sight because your Wi-Fi is really close to where your devices are, and you need that maximum power for whatever reason, then you can go ahead and use the channel bonding, put them all together, and it should work perfectly fine. But if you're bouncing off a lot of things, you're in a high density area, or you're doing a commercial deployment with a lot of Wi-Fi units, you have to think and plan about where the position of those units are, and whether or not they will interfere with each other because that can happen too. And I'll leave you a link to this article. They have a few of them on this topic so you can dive deeper into it about the 256 QAM, Wave 2, and 802 11AC channel bonding in many more engineering details here. I thought this article was pretty cool. I guess that'll leave a link below. But hopefully that clears that up about the Wi-Fi performance. We may do some head-to-head testing with some other Wi-Fi devices, but I like to do this for a while to try to get some of the consumer ones. Maybe if someone will send me one of them, we'll head-to-head with them. But we have seen really, really wonderful performance out of the unified devices. Like I said, hopefully this clears that up and I'll leave links where you can use the tools that I use to do this testing. Thanks for watching. If you liked this video, go ahead and click the thumbs up. Leave us some feedback below to let us know any details which you like and didn't like as well because we love hearing the feedback. Or if you just want to say thanks, leave a comment. If you wanted to be notified of new videos as they come out, go ahead and subscribe and the bell icon that lets YouTube know that you're interested in notifications. Hopefully they send them as we've learned with you too. Anyways, if you want to contract us for consulting services, you go ahead and hit laurancesystems.com and you can reach out to us for all the projects that we can do and help you. We work with a lot of small businesses, IT companies, even some large companies and you can farm different workout to us or just hire us as a consultant to help design your network. Also, if you want to help the channel in other ways, we have a Patreon. We have affiliate links. You'll find them in the description. You'll also find recommendations to other affiliate links and things you can sign up for on laurancesystems.com. Once again, thanks for watching and I'll see you in the next video.


What's happening guys, your local Realized Man checking in and today I want to talk about breakups heartache and how you can overcome those negative feelings with mindfulness, right? Now this video was inspired by this email I received from one of my subscribers, he said I read your post on mindfulness and loved it. Thanks, buddy I was wondering if you had any specific mindfulness techniques for heartache I've just recently broken up with my girlfriend of three years and I'm feeling devastated Okay, so our man here has broken up with his girlfriend. He's feeling devastated I'm gonna give you him and give you guys some tangible advice that you can work with that's really gonna help you kind of overcome those negative feelings you get when you break up with someone when you're feeling heartache because it's probably one of the worst things you could feel in life that Aftermath of a breakup or when you're you know when you feel like shit basically And before I hop into the method of doing this I'm gonna provide you guys with some context about what I'm saying here So we're gonna talk about pain first and how this relates with the breakup issue The other day I was in steaks, right? Because I love steaks. I was in steaks.   So this time when I was putting the salt on it, I thought to myself, you know what? I'm gonna try apply some mindfulness to this try just analyze this pain without associating myself with it so a lot of times when we feel pain we kind of make a big deal with we cry we Bring ourselves into it, right? So I was just trying to objectify the pain just feel for what it is just feel the sensation and see what New insights I can gain from that.  It's about objectively analyzing everything without putting any judgments Slowing things down so that you can analyze and better As I said before as I like to say before you can escape the trap You need to analyze the trap if you're trapped in a web or something You need to see what you can do then you get out You don't just wiggle around so you need analyze the trap of these feelings that are coming up And the way you do is you really go deep into your body It's when you start feeling you know as you said I'm devastated lonely Try see where you're feeling anybody feeling in your hands Are you feeling in your heads your head gonna be heavy is in your legs is in your heart in your chest It's in your back. Where's this feeling coming from in terms of your? Physiology is your heart rate going up. What's happening in your body slow things down incredibly like really slow it down Like you have those high-speed cameras Also observe what's going on in your thoughts. What type of mental dialogue are you having? What images are you recalling of are you remembering things you did in the relationship?  What are you thinking of certain judgments how she acted are you angry? What what are you harboring? Kind of break everything down as much as you can and the process of breaking all these things down Just analyzing what you're doing Teaches you how to disassociate with those feelings so you're kind of like seeing yourself as someone who's observing from the outside, right? And this is how you're gonna get over the break up because you're observing from the outside You don't associate the pain as much with yourself in the same way as when I observe the pain on my lip when I put the salt on it It's not as bad. It's a lot easier to Be a lot easier for it to dissipate because a lot of times We feel the eggs of breakups. We feel that eggs are loneliness because we keep going back We keep making it something to do with us. We keep associating with our ego.  There's no way you're not gonna feel the heart You're gonna feel it, but you can accelerate the recovery process using these mindfulness techniques So repressing it doesn't work in the same way as if I told you not to think of Donald Trump writing a nuke while Holding a cowboy hat Falling down on North Korea.  So don't do that just Objectively analyzing don't play any judgments everything in the world is neutral until we put a perception until we label it as good or bad See for what it is and slowly but surely you start to Detach yourself from it and those feelings would dissipate much quicker much quicker. Okay, that's one aspect of it That's kind of like the inner game of getting over the breakup again over the heartache Now I'm gonna give you some more practical things you can do in the real world to get over it You need to try see this as an opportunity for you to better yourself Recall back on the breakup or the relationship and see perhaps which areas you fell short in right? Try see them objectively. Don't put your subjective ego into a try see perhaps Maybe you are not the best communicator. Perhaps you let yourself go. You got complacent because you're in a relationship You got fat you stop going to yourself take care of yourself Maybe the things that initially made you attractive slowly started going away once you became comfortable See these things and Get better work on yourself, right? This is a perfect time to work on yourself because you got that fire and if you ask your last steam Build your body up Work on your mind see how you can be better for the next run and improve as a human being because of this Get back on your mission because the guy who told me About this relationship when you break up from these relationships the best thing you could possibly do as a man is Focus on your mission use that extra stimulus that extra energy to really drive your mission. All right The girls will come later another relationship will come if you work on yourself If you keep grinding if you do the mindfulness techniques or this stuff will be good. Hey guys, that's the video That's how you get over a breakup, but that's my way If you liked that video make sure you like comment subscribe because the engagement does up the channel They'll be seeing you guys next time. Peace


The South Sudan Football Association has announced that nine members of the national football team, bright stars, have tested positive for coronavirus. The national football government body says the players together with one member of the technical staff were in isolation. It says six other players who have been in contact with those infected have been placed under surveillance. South Sudan takes on Jordan on Monday in the Arab FIFA Cup preliminary fixture. The infection does a huge blow for a team whose performance has greatly improved in recent months.


But some things that tend to be most concerning a student may have our minimum requirement for patient care experience But perhaps it's all in a low-quality category All of it is in shadowing or all of it is in more of an administrative role in a physician's office or something like that That can be concerning because although you have the minimum you really haven't had any Real high quality higher decision-making type role and it would be difficult for someone to be successful in our program without a Little bit more high-quality experience So even though you may have that minimum if all of your experiences in a lower quality category That tends to be concerning to us early on in the process that even if you were to Erin interview spot It may may be an issue for you moving forward Other issues with the a lot of time students if I could I know this is a comes up later But it's sort of like an applicant tip Very often students do not take the time to describe their experiences in CASPA In good detail and really tell us what that role is So they'll for example use a title for a job that they assume we know everything about you know They might say oh, I wasn't a CNA a certified nursing assistant and although we are competent people We know what that role generally entails You're missing an opportunity to really showcase your experience by not describing it Even if you think it's something really obvious So sometimes that can be a little concerning if you if you look at an applicant It almost looks like they rushed through it. They didn't really give you enough information And we really want to get to know that experience because it's an important part of our review process So that would be another sort of red flag is not taking advantage of the the duty section and describing that experience in detail I actually really want to cover that really briefly Because I do kind of help some PPA students with their applications And I look at their CASPA and a lot of people try to stick all of that into their essay They think that it's a narrative of their whole life Yeah, I want to like describe all their duties and I tell them no that's not the place for it, right? Advantage of all that space CASPA gives you to describe all those Responsibilities that you had in that section. So definitely take your time describing each experience Yeah, you nailed it on the head. You know, you have this opportunity to showcase those specific roles in so many different parts of your application that your essay should be more Qualitative in nature. I should be more more personal more descriptive of you and your experience and your goals As opposed to just a listing of everything we already have on file for you And so next question just off of that is are there any common mistakes or red flags or anything during the interview process? That would make somebody less competitive as an applicant. Oh Yeah, I have to laugh a little bit because It doesn't matter if you're applying to PA school or you're applying to an MBA program or you want to be a teacher and you're applying to an education program Some of these common mistakes are just found everywhere One that I would mention is saying that the school you're interviewing with is not your first choice or that You're fine because you didn't get into your first choice or there's some some illusion there that you you're You know, we weren't the ones that you were you were hoping to apply to That can be very a quick deterrent for a faculty interviewer to say what do you mean, you know or or What we what we tend to see in clinically based programs is I was trying to get into Med school and So now I'm just kind of try this instead and it's like well, you know Everyone has a life path and there's a way to explain that life path But just to to kind of unload that and make it seem as though this isn't something you really even researched And maybe you don't really even know that much about it can be a deterrent as well So why don't you be really honest in your life path? If that's what your life was and you were intending to do that we value that we think everybody has a good You know way that they got to us, but you want to be sensitive in the way you approach that topic if that's what he's for you So just with that let's say somebody had been shooting from at school their whole life And then discovered the P the PA profession during their shadowing experience and they decided hey This is better for me. Don't hide the fact that you want it to be a doctor at some point and now you want to be a PA Yeah, I think that again as a Jesuit institution having a really holistic review process We often times throw around the term cure a person Alice right care of the whole person So we want to know that life story, you know, what what did you do? Why did you apply there? How did you start a program and now you're not in it anymore? What happened? You know, and so we're really sensitive to the fact that everyone has a different path to getting here You know, some people were were born with parents that were PAs and they knew from the second they could talk that they were gonna be a PA Other times it's not something people discover until they've been in a career and this is almost like a second career for them So it really there's so many ways to come to this place So being really transparent and honest in that but being sensitive to the fact that you know This is a very competitive program And we want to make sure that if you've made the choice to apply to it that you've done the research and you understand Truly what this what this profession is All right So number one on the list of things not to do is don't say that this is your second choice program or Second choice career don't say you actually want to do something else and you're just trying out this PA thing. Don't do that Yeah, yeah, I Sort of I sort of joke sometimes with students and say think about like you're interviewing someone to be your new best friend Would you want that person to say? Oh, well, you're great. But like I was really hoping to hang out with Cindy down the road But you were just like available It's a lot nicer if you know that person really is invested in you and they know a lot about you and they think you'd be a great Best friend, you know, so it's a silly way to think of it, but kind of put it in that perspective I think that's a good way to think of it All right, so can you give me one more thing someone shouldn't do during the interview During the interview or during the admission process like the full process or just at the interview You know what how about one of each? If you're invited to interview it's because we believe that you could be a good fit for this program And if you do your best and you you are yourself and you you do the absolute best you can do with the interview questions That's all you can worry about. That's the part that's in your control And anything else beyond that what's happening with the committee and the faculty and the analysis of all of that There's no there's nothing a student can do to have changed that So I always say if you've been invited to interview do your best to lose that imposter syndrome this feeling that you don't belong there for some reason You know, we see something in you and we want to learn more about it. So do your absolute best You know, I've heard that before like if you're invited to the interview There's no rank order system anymore. You are possibly going to get one of those spots It's all about moments at the interview from now on Yeah, a lot of times what I'll tell applicants in our information sessions is You know, once you get to the interview, it's almost like everyone's on even playing field, right? Like you've all been invited for some reason so there's no reason to then be comparing yourself to the person next to a person to the right of you or left of you because You've both been invited on your same merit for whatever reason that was so at that point it's really a matter of just being yourself and Remembering that it's a two-way interview, you know competitive programs It can feel very much like you're on the spotlight and you're you're the one being critiqued and in many ways you are But we're also you're also critiquing us You know, you're a competitive candidate, which means you have a choice of a number of programs Likely in the country to explore So the fact that you're interviewing with us is a reminder to us that you know We want to also recruit you to choose us if we should offer you an invitation. So it's a two-way interview That's a really good point and I know one common interview question is do you have any questions for us? Yeah, the worst answer to that question is no no You want to yeah, you want to put the other person not on the spot, but you want to know more about the program Like what is your favorite thing about this program? Why did you choose to teach here whoever's interviewing you? Yeah? Yeah, those are all great. I mean there's you could there's so many different ways you could go with that question But when you're asked in an interview, do you have any questions? It can be an opportunity for you to learn more about the person interviewing you It can be an opportunity more learn more about the college learn more about the program or an opportunity to really Turn the question back around, you know and say, you know, this is something in my experience that I really valued Does your program also value that? You know, does your faculty also have experience with that? So it can be an opportunity to also showcase something about yourself while getting a question answered And many career services offices all at all different colleges offer a lot of help in that So if you're an alumni or even if you're finishing up your senior year and you want to get some good interview practice very often Your undergraduate institution will have a career services office that can do a lot of really good prep with you on that